IBM Support

Message EQQI011F and RC=12 when executing WAPL after PTFs for PI57310 are applied ( COMPID 5697WSZ01 )

Flashes (Alerts)


Abstract

EQQI011F TWS version 930 not supported by WAPL 9.3 message with PI57310 in effect.
New MOD= parameter added to EQQYXJCL which is part of the PARM used also.

Content

The PTFs for APAR PI57310 - UI41128 UI41134 and a LANGUAGE specific PTF :

UI41129 Korean
UI41130 English
UI41131 German
UI41132 Kanji
UI41133 Spanish

require that some changes are made to the EQQYXJCL procedure however the ACTION HOLD
which is part of UI41134 is incorrect.

The ACTION HOLD section for WAPL states:

WAPL actions
=======================================
You need to:
- run EQQWPLCO sample
- update EQQYXJCL sample by:
- running EQQJOBS
or
- changing manually your already customized EQQYXJCL sample
by adding the new line:
// MOD='',
after the existing line:
// LANG=&LANG

replacing the old line:
// PARM=&&@'&&CMD &&SUBSYS-&&VER &&ARGS'&&#
with the new line:
// PARM=&&@'&&CMD &&SUBSYS-&&VER&&MOD &&ARGS'&&#

This ACTION HOLD is correct as written EXCEPT for the part about replacing
the PARM value without running EQQJOBS. When you run EQQJOBS,
it changes the && to & (2 AMPERSANDS to 1 AMPERSAND)

So if you are dealing with an ALREADY customized EQQYXJCL sample it should say:

replacing the old line:
// PARM=&@'&CMD &SUBSYS-&VER &ARGS'&#
with the new line:
// PARM=&@'&CMD &SUBSYS-&VER&MOD &ARGS'&#

or even more simply, in the PARM value change &VER to &VER&MOD.

Note also that if you choose to run EQQJOBS, only part 4 of EQQJOBS needs to
be run:
4 - Generate WAPL samples

After making the changes either via EQQJOBS or a manual edit, and then copying the
EQQYXJCL proc to the desired PROCLIB if needed, the completed EQQYXJCL should
look something like this: (removing all the comments to save space)

//EQQYXJCL PROC @=,
// ARGS='',
// CMD=EQQYXTOP,
// FILESPEC=FILENONE,
// LANG=EN,
// MOD='',
// OPTFILE='TWSZ.V9R3M0.SEQQWAPL',
// OPTS=OPTDEFLT,
// REF=REFERNCE,
// REG=4M,
// SUBSYS=T93C,
// VER=930,
// #=
//EQQYXTOP EXEC PGM=IKJEFT01,
// REGION=&REG,
// PARM=&@'&CMD &SUBSYS-&VER&MOD &ARGS'&#
//STEPLIB DD DISP=SHR,DSN=TWSZ.V9R3M0.SEQQLMD0
//SYSPROC DD DISP=SHR,DSN=TWSZ.V9R3M0.SEQQMISC
//EQQMLIB DD DISP=SHR,DSN=TWSZ.V9R3M0.SEQQMSG0
//EQQMLOG DD SYSOUT=*
//EQQDUMP DD SYSOUT=*
//EQQLANG DD DISP=SHR,DSN=TWSZ.V9R3M0.SEQQWAPL(LANG&LANG.)
//EQQREF DD DISP=SHR,DSN=TWSZ.V9R3M0.SEQQWAPL(&REF.)
//EQQOPTS DD DISP=SHR,DSN=&OPTFILE.(&OPTS.)
//EQQFILE DD DISP=SHR,DSN=TWSZ.V9R3M0.SEQQWAPL(&FILESPEC.)
//EQQSMTP DD SYSOUT=(,)
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD DUMMY

However if you run with this you will STILL get the RC=12 and error message.
You also need to OVERRIDE the MOD= value in your WAPL JCL or change
the EQQYXJCL proc to contain:

MOD='+001'

The reason for this is explained in the WAPL User's Guide.

The EQQYXJCL generated by EQQJOBS is the generic one, that is the JCL that a customer can use to adapt to different level of functionality.
The only reason why EQQJOBS needs to be run after PI57310 is because the EQQYXJCL has been changed by this apar in its structure because of the addition of a new parameter, the MOD level parameter.

MOD must be +001 to handle NOP information (the new function in PI57310). Future enhancements to
WAPL may require a new MOD value (for instance MOD='+002')

So there are really two changes in PI57310- one just to ADD the MOD parameter, which is documented,
and one to change the value of the MOD parameter to '+001' - this part is missing.

Note: If you leave the EQQYXJCL PROC with MOD='' (as it is after running EQQJOBS)
then you will need to add the correct MOD parameter when you invoke EQQYXJCL, for example:

//EQQYXJCL EXEC EQQYXJCL,
// SUBSYS=T93C,MOD='+001'

Here are some samples of WAPL execution before and after PI57310 is applied:

PRIOR to PI57310:

//EQQYXTOP EXEC PGM=IKJEFT01,
// REGION=&REG,
// PARM=&@'&CMD &SUBSYS-&VER &ARGS'&#

EQQI001I T93CCMD1,JOB32089 Starting WAPL v9.3 build 0843
EQQI002I Loading data definitions for TWS 9.3

RC=04

After PI57310 but missing correct actions

//EQQYXTOP EXEC PGM=IKJEFT01,
// REGION=&REG,
// PARM=&@'&CMD &SUBSYS-&VER &ARGS'&#


EQQI001I T93CCMD1,JOB32123 Starting WAPL v9.3 build 0886
EQQI002I Loading data definitions for TWS 9.3 +
EQQI011F TWS version 930 not supported by WAPL 9.3

RC=12

(Note the BUILD value changes from 0843 to 0886)

With ACTION HOLDS suggested by the PTF UI41134

//EQQYXTOP EXEC PGM=IKJEFT01,
// REGION=&REG,
// PARM=&@'&CMD &SUBSYS-&VER&MOD &ARGS'&#

EQQI001I T93CCMD1,JOB32128 Starting WAPL v9.3 build 0886
EQQI002I Loading data definitions for TWS 9.3 +
EQQI011F TWS version 930 not supported by WAPL 9.3

RC=12

With CORRECT MOD value +001:

//EQQYXTOP EXEC PGM=IKJEFT01,
// REGION=&REG,
// PARM=&@'&CMD &SUBSYS-&VER&MOD &ARGS'&#


EQQI001I T93CCMD1,JOB32186 Starting WAPL v9.3 build 0886
EQQI002I Loading data definitions for TWS 9.3 +001

RC=04

(Note The EQQI002I message now has TWS 9.3 +001 instead of just TWS 9.3 +)

[{"Product":{"code":"SSRULV","label":"IBM Workload Scheduler for z\/OS"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"--","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"9.3.0","Edition":"Edition Independent","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
25 September 2022

UID

swg21995215