Download
1 / 58
580 likes | 751 Vues
Tips and Techniques for Problem Diagnosis/Resolution. What can I do before calling the Customer Service Center (CSC)?. Session Overview/Description.
E N D
Tips and Techniques for Problem Diagnosis/Resolution What can I do before calling the Customer Service Center (CSC)?
Session Overview/Description • This session will show you how to locate and use some on-line resources on the Datatel web site: AnswerNet, Tech Doc Online and the Data Structure Diagrams (DSDs). These can be used to troubleshoot and do research beyond the information provided in the documentation and help. • We will review several problems and the methods that can aid in their resolution. • Other helpful tips for the Systems Administrator
Helpful Links AnswerNet – http://support.datatel.com Datatel Documentation General and TechDoc – http://www.datatel.com/documentation DSDs - http://www.datatel.com/documentation Discussion Groups -http://discuss.datatel.com Cedarville –ftp://ftp.cedarville.edu/unidata/
On-Line Resources Tech Doc Online AnswerNet Data Structure Diagrams Discussion Groups (new) Cedarville
Cedarville - cont • What will I find here? • In the cedarville folder on the prior screen, you will find the CEDARVILLE DOWNLOAD program, utilities to view records or files • In the quinnipiac is a program to convert area codes • In the mott folder you will find a program to do uploads to Colleague files
Sample Error Diagnosis Analysis And Resolution
Research done • Go to the INSTALL account and into UT. Bring up ELII and enter the following to do a search ;I S.GET.SAFARI.SECURITY • Select any one of these. I would select # 4, since it is a subroutine and view the results. You will see which update that was on and you may re-set this update using ELRS.
GL Size Incorrect • User calls you and says I got an error message "GL number size is incorrect". You know that GL is in the CF application. You can search the CF.ERROR file to for the message to figure out which error message number it is so you search the program. FIND CF.ERROR incorrect 2 records retrieved to list 0. LIST CF.ERROR ERRORMSG.USED.BY ERRORMSG.MESSAGE From the list I do not see what I am looking for. FIND CF.SOURCE incorrect 9 records retrieved to list 0. >FIND CF.SOURCE number 5 records retrieved to list 0. >FIND CF.SOURCE size 1 records retrieved to list 0. >AE CF.SOURCE < 1 > Top of "GLB001" in "CF.SOURCE", 1,833 lines, 59,691 characters. *---: /incorrect 0950: XL.MSG<-1> = 'LINE ':X.LINE.NO:': The GL number size is incorrect' At line 1833 (bottom). Found 1 line.
GL Size Incorrect - continued • 0932: ***************** • 0933: VALIDATE.RECORD: • 0934: ***************** • 0935: • 0936: * Perform several validations against the data. If anything is • 0937: * invalid set XL.MSG. • 0938: • 0939: * Even if the previous validation of the source code gives an error, • 0940: * continue to validate record, so that all errors are displayed • 0941: • 0942: * Make sure a GL no, debit, credit, descriptions and ref no exist. • 0943: * Make sure a offset account and bank account exist when necessary. • 0944: • 0945: X.VALID.GL = '' • 0946: IF NOT(LEN(X.GL.NO)) THEN • 0947: XL.MSG<-1> = 'LINE ':X.LINE.NO:': No GL number specified' • 0948: END ELSE • 0949: IF LEN(X.GL.NO) NE X.SIZE.TGL THEN • 0950: XL.MSG<-1> = 'LINE ':X.LINE.NO:': The GL number size is incorrect' • 0951: END ELSE • 0952: V.GL.ACCTS.ID = X.GL.NO • Top. • *---: /X.GL.NO • 0751: X.GL.NO = TRIM(R.INTERFACE[V.GLID.GL.NO.START,V.GLID.GL.NO.LENGTH]) • 0752: IF LEN(X.GL.NO) THEN • 0758: CALL @MOD.SUBR(X.GL.NO) • 0760: X.GL.NO = TRIM(X.GL.NO)
GL Size Incorrect - continued • From the message X.GL.NO = TRIM(R.INTERFACE[V.GLID.GL.NO.START,V.GLID.GL.NO.LENGTH]) I knew that the reference is to the GL.INTERFACES file or the GLID – GL Import Definition process I had the user check the size of their GL number in the GL Account No Def. Sure enough it was set to 22 and their GL number size was 25.
Fixing Damaged UniData Files • Get ALL users off of the system. • Set /etc/.nologin to keep users out • Or use MAX.USERS to block UniData login • Make a Unix copy of the damaged file(s). • Run guide on the file(s). • Run the fixfile utility • A UniData ECL COPY may fix some damage that fixfile doesn’t
File corruption detection / recovery • Corruption during udt run-time is recorded in logs • $UDTBIN/udt.errlog - non RFS files • fixfile creates ascii files with records it dumps • Can be used to reload. First field is the key. Delete it. • fixgroup filename group.no (with no –ifile) • Can be used to zero a bad group • memresize filename restore • Will skip corrupted groups – if fixfile can’t read the group
How to change the default sort for CKSE – cont.Line 7 below is PROCESS.TO.EXECUTE
How do I stop the phantom screen from appearing when running processes.
In this example, I am running the GBER report. This is the phantom process screen that will appear. This is typically the third screen you would see. To update this individual report, you want to go into CF and then JDEF – Procedure Specification. When prompted for Procedure Mnemonic Lookup, enter GBER. In the following example, you will want to update the field: Executable as a Phantom. Currently, it is a Y. Change the field to N and the user will not be prompted to execute the screen in background.
Now if the process is re-delivered the setting will be overwritten. I would suggest creating a VOC paragraph to set the appropriate screens the way you would like. If you generate a savedlist of the processes you want to remove the phantom prompt for you can use a modify command to change the flag to N. To change the setting using a modify command, you could do the following: SELECT CF.PRCS.GEN “GBER” MODIFY CF.PRCS.GEN JS.PHANTOM.ALLOWED = ‘N’
