Question & Answer
Question
Message "EQQJ530E SCANNING LENGTH EXCEEDED LINE nnnn of Orig JCL" may be issued when using the OETEVNM JCL variable in a SETVAR directive such as //*%OPC SETVAR TVAR1=SUBSTR(&OETEVNM,6,32)
Cause
If the resolved length of the &OETEVNM variable is more than 37 characters, the total length of the directive will be more than 71 characters, causing the substitution to fail and the error message to be issued. The operation whose JCL includes this directive will be set to ERROR with an OSUB code.
Answer
When used in conjunction with an ETT RESOURCE EVENT, the OETEVNM variable contains the complete SPECIAL RESOURCE NAME of the triggering event. If the ETT EVENT is a DATASET TRIGGER, the OETEVNM is the fully qualified DSN of the triggering dataset.
.
TWSz JCL VARIABLES are limited to no more than 71 characters in length, while a z/OS DSN may be as much as 44 characters. in testing the SETVAR directive shown above, message EQQJ530E was issued if the resolved value of the OETEVNM variable was more than 37 characters.
.
This is a design restriction, and has been documented via DOC APAR PM01090, and request for design change MR1209097032 has been submitted to add support to TWSz for continuation of JCL DIRECTIVES across multiple lines.
.
In the case above, a few more characters can be gleaned for resolution of the OETEVNM variable by changing the name of temporary variable TVAR1 to T1. Temporary variable names must begin with T. However, variable names may be reused within a single JCL member as is documented in the TWSz MANAGING THE WORKLOAD manual.
Was this topic helpful?
Document Information
Modified date:
13 September 2019
UID
swg21418925