Error feedback tracing

The following procedure allows gathering of information needed to diagnosis error feedback problems with remote build procedures. This tracing will cause performance degradation and should only be done under the direction of the IBM® support center. All references to hlq in this section refer to the high-level qualifier used during installation of z/OS® Explorer Extensions. The installation default is FEL, but this might not apply to your site.
  1. Make a backup copy of your active ELAXFCOC compile procedure. This procedure is default shipped in data set hlq.SFELSAMP, but could have been copied to a different location, such as SYS1.PROCLIB, as described in "ELAXF* remote build procedures" in the Host Configuration Guide.
  2. Change the active ELAXFCOC procedure to include the 'MAXTRACE' string on the EXIT(ADEXIT(ELAXMGUX)) compile option. 
    //COBOL    EXEC PGM=IGYCRCTL,COND=(4,LT),REGION=0M,
//*           PARM=('EXIT(ADEXIT(ELAXMGUX))',
//            PARM=('EXIT(ADEXIT(''MAXTRACE'',ELAXMGUX))',
//            'ADATA',
//*           'LIB',                     not supported in COBOL V5 & up
//*           'TEST(NONE,SYM,SEP)',      not supported in COBOL V5 & up
//            'TEST',
//            'LIST',
//            'FLAG(I,I)'&CICS&DB2&COMP)
    Note: You have to double the apostrophes around MAXTRACE. The option is now: EXIT(ADEXIT(''MAXTRACE'',ELAXMGUX)).
  3. Perform a Remote Syntax Check on the COBOL program for which you want detailed tracing.
  4. The SYSOUT part of the JES output will start by listing the names of the data sets for SIDEFILE1, SIDEFILE2, SIDEFILE3 and SIDEFILE4. 
    ABOUT TO OPEN SIDEFILE1 - NAME = 'uid.DT021207.TT110823.M0000045.C0000000'
SUCCESSFUL OPEN SIDEFILE1 - NAME = 'uid.DT021207.TT110823.M0000045.C0000000'
ABOUT TOO OPEN SIDEFILE2 - NAME = 'uid.DT021207.TT110823.M0000111.C0000001'
SUCCESSFUL OPEN SIDEFILE2 - NAME = 'uid.DT021207.TT110823.M0000111.C0000001'
ABOUT TOO OPEN SIDEFILE3 - NAME = 'uid.DT021207.TT110823.M0000174.C0000002'
SUCCESSFUL OPEN SIDEFILE3 - NAME = 'uid.DT021207.TT110823.M0000174.C0000002'
ABOUT TOO OPEN SIDEFILE4 - NAME = 'uid.DT021207.TT110823.M0000236.C0000003'
SUCCESSFUL OPEN SIDEFILE4 - NAME = 'uid.DT021207.TT110823.M0000236.C0000003'
    Note: Depending on your settings, SIDEFILE1 and SIDEFILE2 may be pointing to a DD statement (SUCCESSFUL OPEN SIDEFILE1 - NAME = DD:WSEDSF1). Refer to the JESJCL part of the output (which is located before the SYSOUT part) to get the actual data set name.
           22 //COBOL.WSEDSF1 DD DISP=MOD,
          // DSN=uid.ERRCOB.member.SF.Z682746.XML
       23 //COBOL.WSEDSF2 DD DISP=MOD,
          // DSN=uid.ERRCOB.member.SF.Z682747.XML
  5. Copy these four data sets to your PC, for example, by creating a local COBOL project in z/OS Explorer Extensions and adding the SIDEFILE1->4 data sets.
  6. Copy the complete JES job log to your PC, for example, by opening the job output in z/OS Explorer Extensions and saving it to the local project by selecting File > Save As.
  7. Restore procedure ELAXFCOC to the original state, either by undoing the change (remove the ''MAXTRACE'', string in the compile options) or restoring the backup.
  8. Send the collected files (SIDEFILE1->4 and job log) to the IBM support center.