Troubleshooting
Problem
Errors with Electronic Service Agent can be received if the QASX* and/or QAEDCDB* files in library QUSRSYS are backlevel. This document describes when and how to check for backlevel files and how to restore those files from base operating system media.
Resolving The Problem
NOTE:
Though OS versions V6R1 and V7R1 are no longer supported, this information is provided to allow hardware problem reporting to function as long as the system has a hardware maintenance agreement. Software support on these releases are limited to getting hardware problem reporting functioning.
Backlevel QASX* files in QUSRSYS library can cause problems with problem send and SNDPTFORD functions of Electronic Service Agent. The same is true for the contact information file, QAEDCDB*. Some error messages you could see when backlevel files are present are as follows:
CPF3CF2 - Error occurred during running of QsxRetrieveProblemLogEntry API.
CPFEF32 - Error creating a test problem. when attempting to create a test problem.
C2M3003 - Data was truncated on an input, output or update operation.
In WRKLNK '/qibm/userdata/os400/universalconnection/eccerr.stdout', you may see:
Failing class[ProblemLog] Failing method[retrieveProblemLogEntry] Failure descrip Entry] Failure description[Error when trying to run a procedure in AS400
Though OS versions V6R1 and V7R1 are no longer supported, this information is provided to allow hardware problem reporting to function as long as the system has a hardware maintenance agreement. Software support on these releases are limited to getting hardware problem reporting functioning.
Backlevel QASX* files in QUSRSYS library can cause problems with problem send and SNDPTFORD functions of Electronic Service Agent. The same is true for the contact information file, QAEDCDB*. Some error messages you could see when backlevel files are present are as follows:
CPF3CF2 - Error occurred during running of QsxRetrieveProblemLogEntry API.
CPFEF32 - Error creating a test problem. when attempting to create a test problem.
C2M3003 - Data was truncated on an input, output or update operation.
In WRKLNK '/qibm/userdata/os400/universalconnection/eccerr.stdout', you may see:
Failing class[ProblemLog] Failing method[retrieveProblemLogEntry] Failure descrip Entry] Failure description[Error when trying to run a procedure in AS400
You can check for backlevel QASX* and contact information files by doing the following:
DSPOBJD OBJ(QUSRSYS/QASXPROB) OBJTYPE(*FILE) DETAIL(*SERVICE) and check that the System Level is the same as the OS
DSPOBJD OBJ(QUSRSYS/QASXPTF) OBJTYPE(*FILE) DETAIL(*SERVICE) and check that the System Level is the same as the OS
DSPOBJD OBJ(QUSRSYS/QAEDCDBPF) OBJTYPE(*FILE) DETAIL(*SERVICE) and check that the System Level is the same as the OS
If the System Level for all files match the version of the OS, ensure that the Total number of fields and Total record length of each file are correct:
DSPFD FILE(QUSRSYS/QASXPROB)
Specify B in the Control field and press <ENTER> to go to the bottom of the file
Locate the Total number of fields and Total record length values, which should be:
R720 and higher:
Total number of fields . . . . . . . . . . . : 124
Total record length . . . . . . . . . . . . : 2539
R710 and R610:
Total number of fields . . . . . . . . . . . : 121
Total record length . . . . . . . . . . . . : 2539
DSPFD FILE(QUSRSYS/QASXPTF)
All releases:
Total number of fields . . . . . . . . . . . : 11
Total record length . . . . . . . . . . . . : 60
DSPFD FILE(QUSRSYS/QAEDCDBPF)
All releases:
Total number of fields . . . . . . . . . . . : 71
Total record length . . . . . . . . . . . . : 4537
If you find the files are not the same System Level as the OS or have the incorrect number of fields or record length, you will need to get the correct version of the files installed on the system. This can be done by installing the files directly from the OS install media:
| 1. | Locate the base OS install media or image catalog. The objects are on the following CD/DVD labeled: o V6R1 - B2924_01 o V7R1, V7R2, V7R3 and V7R4 - B_GROUPx_01 |
| 2. | Rename (or delete) the existing QASX* physical files and logical files in QUSRSYS library: a. WRKOBJ QUSRSYS/QASX* b. Select Option 7 to rename them all (or Option 4 to delete them all) NOTE: Rename or delete the QASXPROB2 logical file first c. WRKOBJ QUSRSYS/QAEDCDB* d. Select Option 7 to rename (or Option 4 to delete) QAEDCDBLF first, followed by QAECDCDBPF. |
| 3. | Execute this command to get all of the QASX* files restored to QUSRSYS from the install media: RSTOBJ OBJ(QASX*) SAVLIB(QUSRSYS) DEV(OPT01) OPTFILE('/QUSRLIBS/Qvrm0024/QUSRSYS') Where vrm is the Version/Release/Modification Level of your OS (for example, 610, 710, 720, 730 or 740). (Note: You may not see all of the files listed, depending on your operating system version): QASXCALL QASXDTA QASXEVT QASXFRU QASXNOTE QASXPROB QASXPROB2 QASXPTF QASXSYMP QASXURI |
| 4. | Execute this command to get all the QAEDCDB* files restored to QUSRSYS from the install media: RSTOBJ OBJ(QAEDCDB*) SAVLIB(QUSRSYS) DEV(OPT01) OPTFILE('/QUSRLIBS/Qvrm0024/QUSRSYS') For each of the QASX* and QAEDCDB* files, enter the following command: CHGOBJOWN OBJ(QUSRSYS/xxxxx) OBJTYPE(*FILE) NEWOWN(QSYS) CUROWNAUT(*REVOKE) **Where xxxxx is one of the QASX* and QAEDCDB* files listed above. |
| 5. | Check the authority for each object: a. WRKOBJ QUSRSYS/QASX* b. Take an Option 2 on each object. c. The Owner (in the upper right hand corner) should say QSYS. d. The authorities should look like this: Object User Group Authority *PUBLIC *CHANGE QSYS *ALL |
| 6. | If the contact information files were restored, the contact information must be updated using the CHGCNTINF command. |
| 7. | Test that the new files resolved the issue by sending a test problem (GO SERVICE, Option 15, and accept the defaults) or by using SNDPTFORD. |
[{"Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CGRAA2","label":"Electronic Service Agent"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0;7.2.0;7.3.0;7.4.0"}]
Historical Number
606402052
Was this topic helpful?
Document Information
Modified date:
21 August 2020
UID
nas8N1011422