EQAUT: JCL analyzer messages
All messages that are shown in this section are in mixed case English. The uppercase English message text is the same, but is in uppercase letters.
Each message has a number of the form EQAUTnnnnx, where EQAUT indicates that the message is an
Test Accelerator for
Z JCL analyzer message, nnnn is
the number of the message, and x indicates the severity level of each message. The value of x is I,
W, E, S, or U, as described below:
- I
- An informational message calls attention to some aspect of a command response that might assist the programmer.
- W
- A warning message calls attention to a situation that might not be what is expected or to a situation that Test Accelerator for Z attempted to fix.
- E
- An error message describes an error that Test Accelerator for Z detected or cannot fix.
- S
- A severe error message describes an error that indicates a command referring to bad data, control blocks, program structure, or something similar.
- U
- An unrecoverable error message describes an error that prevents Test Accelerator for Z from continuing.
EQAUT3001I
Explanation
This message provides white space when a series of messages are generated, allowing the messages to be more easily read.System action
The system is functioning normally.User response
None.EQAUT3002I program_name (compile_date compile_time)
Explanation
This message is the first in a series of seven that report a copyright notice.System action
The system is functioning normally.User response
None.EQAUT3003I Licensed materials - Property of IBM
Explanation
This message is the second in a series of seven that report a copyright notice.System action
The system is functioning normally.User response
None.EQAUT3004I Copyright IBM Corp. year All Rights Reserved
Explanation
This message is the fourth in a series of seven that report a copyright notice. The message text variable year indicates the copyright year(s).System action
The system is functioning normally.User response
None.EQAUT3005I US Government Users Restricted Rights - Use, duplication
Explanation
This message is the fifth in a series of seven that report a copyright notice.System action
The system is functioning normally.User response
None.EQAUT3006I or disclosure restricted by GSA ADP Schedule Contract
Explanation
This message is the sixth in a series of seven that report a copyright notice.System action
The system is functioning normally.User response
None.EQAUT3007I with IBM Corporation
Explanation
This message is the seventh in a series of seven that report a copyright notice.System action
The system is functioning normally.User response
None.EQAUT3009I *** Opened File List
Explanation
This message is an informational banner.System action
The system is functioning normally.User response
None.EQAUT3010I parameter
Explanation
This message is an informational echo of parameter(s), user data, return code, and so on. This message provides additional information for interpreting other error messages.System action
The system is functioning normally.User response
None.EQAUT3011I *** End Opened File List
Explanation
This message is an informational banner.System action
The system is functioning normally.User response
None.EQAUT3012I *** Job Search List
Explanation
This message is an informational banner.System action
The system is functioning normally.User response
None.EQAUT3013I *** End Job Search List
Explanation
This message is an informational banner.System action
The system is functioning normally.User response
None.EQAUT3014I *** Default Search List
Explanation
This message is an informational banner.System action
The system is functioning normally.User response
None.EQAUT3015I *** End Default Search List
Explanation
This message is an informational banner.System action
The system is functioning normally.User response
None.EQAUT3016I *** Referenced List
Explanation
This message is an informational banner.System action
The system is functioning normally.User response
None.EQAUT3017I status_data1 status_data2 status_data3
Explanation
This message is an informational status data.System action
The system is functioning normally.User response
None.EQAUT3018I *** End Referenced List
Explanation
This message is an informational banner.System action
The system is functioning normally.User response
None.EQAUT3019E Container name exceeds maximum
Explanation
JCL analyzer supports the following container name maximum lengths: z/OS® = 44, workstation = 254.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the length of the container name, then retry the operation.EQAUT3020E File name exceeds maximum
Explanation
JCL analyzer supports the following file name length maximums: z/OS® = 10, workstation = 254.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the length of the file name, then retry the operation.EQAUT3021E Open failure on DD:JCLLIB, specifies default concatenation list
Explanation
No JCLLIB statement was specified in the JCL, or the data set specified for JCL INCLUDEs or procedures could not be opened. JCL analyzer will use its own default JCLLIB concatenation list (for example, DD DUMMY).System action
Processing continues.User response
No action is required if there are no INCLUDEs or procedures named in EXEC statements to be found. Otherwise, identify a valid concatenation set and retry the operation. Concatenation sets are in &hlq.USER.INCL2, where &hlq represents the high-level qualifier for JCL analyzer user data sets specified at the time of installation. Contact IBM Software Support.EQAUT3022E Number of containers exceeds default concatenation limit
Explanation
For the JCL scanner, the JCL analyzer container concatenation maximum is 32. The number of containers specified for JCLLIB DD * exceeds this limit.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the number of containers, then retry the operation.EQAUT3023E Container name read from file too long
Explanation
The JCL analyzer supports the following container name maximum lengths: z/OS® = 44, workstation = 254.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the length of the container name, then retry the operation.EQAUT3024E Number of containers on JCLLIB exceeds limit
Explanation
The JCL analyzer container concatenation maximum is 32. The number of containers specified in the JCLLIB ORDER= statement cannot exceed this limit.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the number of containers listed in the JCLLIB ORDER= statement, then retry the operation.EQAUT3025E Attempt to nest source too deeply
Explanation
The JCL analyzer container concatenation maximum is 32. The number of containers specified in the JCLLIB ORDER= statement cannot exceed this limit.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the number of containers listed in the JCLLIB ORDER= statement, then retry the operation.EQAUT3026E Number of source files used exceeds limit
Explanation
The JCL analyzer include and procedure source file maximum is 200. The number of unique referenced source files cannot exceed this limit.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the number of unique referenced source files, then retry the operation.EQAUT3027E File name for INCLUDE or external PROC name is too long
Explanation
The JCL analyzer supports the following file name length maximums: z/OS® = 10, workstation = 254.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the length of the file name, then retry the operation.EQAUT3028E INCLUDE file or cataloged PROC not found: name
Explanation
The JCL analyzer detected a reference to an INCLUDE or PROC named name, and it was not found by searching the JCLLIB concatenation set of containers, if specified, or the user concatenation set of containers, if specified.System action
The scanner continues processing.User response
Verify the location of the named INCLUDE or PROC and ensure its container is represented in a concatenation set known to JCL analyzer. This representation can be accomplished either by using a JCLLIB concatenation set of containers in the JCL or by identifying a user concatenation set of containers assigned to the container or file being processed.EQAUT3030E Container Name parameter is not valid
Explanation
The container name was not found in the input parameters, or it is an invalid container name.System action
The scanner skips the current file, and processing continues.User response
Contact IBM Software Support.EQAUT3031E File Name parameter is not valid
Explanation
The file name was not found in the input parameters, or it is an invalid file name.System action
The scanner skips the current file, and processing continues.User response
Contact IBM Software Support.EQAUT3032E Open failure on DD:INFILE, specifies JCL file
Explanation
The container and member specified for the INFILE DD could not be opened. Possible causes are:- The container or file does not exist.
- The user does not have proper authority to access the container.
System action
The scanner skips the current file, and processing continues.User response
Verify and correct the cause, then retry the operation.EQAUT3033E Comment continuation flag was not followed by valid card
Explanation
An expected comment continuation was not found. The JCL being analyzed included a comment continuation flag in column 72, but the next statement was not a valid comment.System action
Scanning terminates for the current file, and processing continues.User response
Verify the JCL comment statement is continued correctly. To continue a comment:- Interrupt the comment at a convenient place before column 72, up to and including column 71.
- Code a non-blank character in column 72.
- Code // in columns 1 and 2.
- Code a blank character in column 3.
- Continue the comments field beginning in any column after column 3.
Verify and correct the syntax, then retry the operation.
EQAUT3034E End of file after comment continuation flag
Explanation
An expected continuation of comment was not found. The last statement in the JCL contained a comment continuation flag.System action
Scanning terminates for the current file, and processing continues.User response
Verify the JCL comment statement should be continued. To continue a comment:- Interrupt the comment at a convenient place before column 72, up to and including column 71.
- Code a non-blank character in column 72.
- Code // in columns 1 and 2.
- Code a blank character in column 3.
- Continue the comments field beginning in any column after column 3.
Verify and correct the syntax, then retry the operation.
EQAUT3038E DLM= delimiter not two characters
Explanation
The DLM=delimiter did not specify the required two characters to indicate the end of this data set in the input stream.System action
Scanning terminates for the current file, and processing continues.User response
Verify the DLM=delimiter subparameter specifies two characters. Enclose special characters—any character that is neither alphanumeric nor national—in apostrophes. If the delimiter contains an ampersand or an apostrophe, code each ampersand or apostrophe as two consecutive ampersands or apostrophes. Each pair counts as one character. Verify and correct the syntax, then retry the operation.EQAUT3039E DLM= parameter on DD statement < 2 chars
Explanation
The DLM=delimiter did not specify the required two characters to indicate the end of this data set in the input stream.System action
Scanning terminates for the current file, and processing continues.User response
Verify the DLM=delimiter subparameter specifies two characters. Enclose special characters—any character that is neither alphanumeric nor national—in apostrophes. If the delimiter contains an ampersand or an apostrophe, code each ampersand or apostrophe as two consecutive ampersands or apostrophes. Each pair counts as one character. Verify and correct the syntax, then retry the operation.EQAUT3040W DLM= contains & not followed by &
Explanation
The DLM=delimiter did not specify the required two ampersands.System action
Scanning terminates for the current file, and processing continues.User response
Verify the DLM=delimiter subparameter contains a pair of ampersands for each intended single occurrence. Each pair of ampersands counts as one character. Verify and correct the syntax, then retry the operation.EQAUT3043E Illegal statement found in PROC definition
Explanation
The scanner encountered unexpected syntax while processing a procedure definition. The PROC statement marks the beginning of a procedure. Syntax of the PROC statement is as follows:- For a cataloged procedure:
//[name] PROC [parameter [comments]] //[name] PROC - For an in-stream procedure:
//name PROC [parameter [comments]] //name PROC
System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the syntax of the procedure, then retry the operation.EQAUT3046E Illegal statement within include group
Explanation
The scanner encountered unexpected syntax while processing an include group. Include groups cannot contain the following JCL statements:- JOB statements
- PROC and PEND statements
- JCLLIB statements
- JES2 and JES3 statements and commands
- DD * and DD DATA statements
System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the syntax of the include group, then retry the operation.EQAUT3048E PEND without matching procedure invocation
Explanation
A PEND statement was identified and no corresponding procedure invocation was found.System action
Scanning terminates for the current file, and processing continues.User response
Locate any missing files, then retry the operation. Otherwise, verify and correct the syntax, then retry the operation.EQAUT3050E Memory allocation failure
Explanation
This is an internal error of the application.System action
Processing stops.User response
Contact IBM Software Support.EQAUT3054E Includes nested too deeply
Explanation
The JCL analyzer include nesting maximum is 15. The nesting of INCLUDEs exceeds this limit.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the include nesting, then retry the operation.EQAUT3058E Symbolic name too long
Explanation
The JCL analyzer JCL name length maximum is 8. The symbolic name fields must not exceed this limit.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the length of the symbolic name, then retry the operation.EQAUT3059E Multiple JOB cards
Explanation
More than one JOB card was detected. JCL analyzer does not support multiple JOB cards; only a single job per file is allowed.System action
Scanning terminates for the current file, and processing continues.User response
Split multiple (nested) JOBs into single files, then retry the operation.EQAUT3062E Too many parms
Explanation
The JCL analyzer parameter maximum is 400. The number of JCL parameters passed to a step exceeded this limit.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the number of parameters, then retry the operation.EQAUT3063E Parenthesis and apostrophe nesting exceeded
Explanation
The JCL analyzer nesting maximum is 20. You can nest the delimiters up to the maximum.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the delimiter nesting level, then retry the operation.EQAUT3065E If nesting exceeds limit
Explanation
The JCL analyzer IF nesting level maximum is 16. The nesting of IF statements exceed this limit. You can nest IF/THEN/ELSE/ENDIF statement constructs up to the maximum. The steps that execute in a THEN clause and an ELSE clause can be another IF/THEN/ELSE/ENDIF statement construct.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the IF nesting level, then retry the operation.EQAUT3066E ENDIF without IF
Explanation
An ENDIF statement was identified and no corresponding IF statement was located. The IF statement is always followed by a relational expression and a THEN clause. Optionally, an ELSE clause can follow the THEN clause. An ENDIF statement always follows the ELSE clause, if present, or the THEN clause. The ENDIF statement indicates the end of the IF/THEN/ELSE/ENDIF statement construct and must be coded for each construct.System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the IF/THEN/ELSE/ENDIF syntax, then retry the operation.EQAUT3067E Keyword parameter or SET statement missing =
Explanation
The scanner detected that a symbol value pair was found without a SET statement, or a symbol value pair was missing an equal sign. SET defines and assigns initial values to symbolic parameters used when processing JCL statements. Syntax of the SET statement is as follows:System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the syntax of the SET statement parameter(s), then retry the operation.EQAUT3068E JCLLIB missing ORDER=
Explanation
The scanner detected a JCLLIB statement, but no ORDER= keyword parameter was found. The JCLLIB statement identifies and orders the libraries that the system uses for the job when searching for procedures and INCLUDEs. Syntax of the JCLLIB statement is as follows:System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the syntax of the JCLLIB statement, then retry the operation.EQAUT3070E EXEC card has null first parameter
Explanation
The scanner detected an EXEC statement, but no positional parameter (for example, PGM, PROC or procedure name) was found. The EXEC statement identifies the program or cataloged or in-stream procedure that this job step is to execute. Syntax of the EXEC statement is as follows:System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the syntax of the EXEC statement, then retry the operation.EQAUT3071E EXEC card PGM= has null value
Explanation
The scanner detected an EXEC statement with a positional parameter PGM=, but no program name was found. The PGM parameter names the program that the system is to execute. The syntax of the PGM parameter is as follows:- PGM=
- {program_name}
- {*.stepname.ddname}
- {*.stepname.procstepname.ddname}
- {JCLTEST}
- {JSTTEST}
System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the syntax of the PGM= parameter, then retry the operation.EQAUT3072E DD concatenation without DD statement
Explanation
The scanner was processing a DD concatenation and found no corresponding job step, JOBLIB or JOBCAT.System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the syntax, then retry the operation.EQAUT3073E Missing JOB card
Explanation
The JOB statement is expected to be the first statement to mark the beginning of a job. The JOB statement was not found, or an incomplete JOB card was detected (for example, a JOB statement was identified but an expected continuation of the JOB card was not found)System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the JCL to include a JOB card, then retry the operation.EQAUT3074E DD after JOB not JOBLIB or JOBCAT or PROCLIB
Explanation
The scanner encountered an unexpected DD statement. The scanner expects to find JOBLIB, JOBCAT, or PROCLIB statements following the JOB card. There should be no intervening EXEC or other DD statements.System action
Scanning terminates for the current file and processing continues.User response
Verify and correct the syntax. Try the operation again.EQAUT3075E Multiple JOBCAT statements
Explanation
The scanner supports one JOBCAT per job, appearing after the JOB statement, following the JOBLIB, if coded, and before the first EXEC.System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the JCL to use a single JOBCAT, then retry the operation.EQAUT3076E Multiple JOBLIB statements
Explanation
The scanner supports one JOBLIB per job, appearing after the JOB statement, before the JOBCAT, if coded, and before the first EXEC.System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the JCL to utilize a single JOBLIB, then retry the operation.EQAUT3078E Illegal statement in procedure
Explanation
JCL analyzer encountered an unknown statement while processing the syntax of the procedure. Syntax of the PROC statement is as follows:- For a cataloged procedure:
//[name] PROC [parameter [comments]] //[name] PROC - For an in-stream procedure:
//name PROC [parameter [comments]] //name PROC
System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the syntax of the procedure, then retry the operation.EQAUT3079E PROC nesting exceeded limit
Explanation
The JCL analyzer PROC nesting maximum is 15. In a procedure, an EXEC statement can invoke another procedure, which can contain an EXEC statement to invoke another procedure, and so on. Cataloged and in-stream procedures can invoke other procedures up to 15 levels of nesting.System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the syntax, then retry the operation.EQAUT3080E Query empty context stack
Explanation
This is an internal error of the application.System action
Scanning terminates for the current file, and processing continues.User response
Contact IBM Software Support.EQAUT3081E PROC stack underflow
Explanation
This is an internal error of the application.System action
Scanning terminates for the current file, and processing continues.User response
Contact IBM Software Support.EQAUT3082I Statement: level1-level2 label operation parameter
Explanation
This message provides the status of a JCL statement being processed.System action
The system is functioning normally.User response
None.EQAUT3083I Substitution: level1-level2 label operation parameter
Explanation
This message provides the status of a JCL statement being substituted.System action
The system is functioning normally.User response
NoneEQAUT3084E Too many steps in job
Explanation
The JCL analyzer JOB step maximum is 255. You enter a program into the operating system as a job step. A job step consists of the job control statements that request the resources needed to run the program and is identified by an EXEC statement. A job can be simple or complex; it can consist of one step or of many steps, up to 255.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the number of steps in the job, then retry the operation.EQAUT3086E StepName.DDName too long
Explanation
The JCL analyzer detected a step name syntax that exceeded allowed length.System action
The analysis scan is terminated.User response
Correct the invalid JCL and reanalyze.EQAUT3087E Could not find step named on override DD
Explanation
An override statement explicitly named a step that was not found in the expanded procedure.System action
Scanning terminates for the current file, and processing continues.User response
Locate any missing files, then retry the operation. Otherwise, verify and correct the syntax, then retry the operation.EQAUT3088E Could not add DD; no PGM= steps found
Explanation
The DD override was not added to inventory. The scanner attempted to default to override the first step, which was not found, possibly due to all expanded steps invoking nested procedures.System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the syntax, then retry the operation.EQAUT3089I Added to Proc: level1-level2 label operation parameter
Explanation
This message provides the status of a JCL statement; a DD statement was added.System action
The system is functioning normally.User response
None.EQAUT3090I Override Proc: level1-level2 label operation parameter
Explanation
This message provides the status of a JCL statement; a DD statement was overridden.System action
The system is functioning normally.User response
None.EQAUT3091E Fatal Error: level1-level2 label operation parameter
Explanation
This message reports a fatal error while processing a JCL statement.System action
Scanning terminates for the current file, and processing continues.User response
Contact IBM Software Support.EQAUT3092E Statement label is too long
Explanation
The JCL analyzer JCL statement label length maximum is 18 (for example, StepName.DDNameXX).System action
Scanning terminates for the current file, and processing continues.User response
Reduce the length of the statement label, then retry the operation.EQAUT3093E Statement parameter text is too long
Explanation
The JCL analyzer JCL statement parameter length maximum is 8192. The parameter text length exceeds this limit.System action
Scanning terminates for the current file, and processing continues.User response
Reduce the length of the statement parameter text string, then retry the operation.EQAUT3095E Instream PROC has no name
Explanation
An in-stream procedure definition has no name in its PROC statement.System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the syntax, then retry the operation.EQAUT3096E Instream PROC PEND not found before end of file
Explanation
An end of file was reached, and no corresponding PEND statement was located for the in-stream procedure being processed. In-stream procedures must end with a PEND statement.System action
Scanning terminates for the current file, and processing continues.User response
Verify and correct the syntax, then retry the operation.EQAUT3097I Input parameters:
Explanation
This message reports the status of input parameters being processed.System action
The system is functioning normally.User response
None.EQAUT3098E Internal error
Explanation
This is an internal error of the application.System action
Scanning terminates for the current file, and processing continues.User response
Contact IBM Software Support.EQAUT3100W Could not substitute DB2 run unit for SYSTSIN *
Explanation
The scanner recognizes batch invocation of TSO (IKJEFT1A) and will look for SYSTSIN DD on the job step to identify the actual DB2® run unit name. If SYSTSIN DD is not coded, does not specify RUN PROG(name), or the data cannot be read, no run unit name substitution is available.System action
Processing continues.User response
None.EQAUT3101W Could not open filename
Explanation
The scanner could not open the filename specified for SYSTSIN DD. The scanner attempts to open this file to identify the DB2® system specified on the DSN SYSTEM(sysname) parameter and the run unit name specified on the RUN PROG(progname) parameter. This message can be paired with DMH1443W.System action
Processing continues.User response
Verify the status and location of the file specified for the SYSTSIN DD; make corrections, if any, and try the operation again if the file is available.EQAUT3102W Could not find OUTPUT spec named name
Explanation
The JCL analyzer detected output parameters associated with a SYSOUT DD statement (for example, OUTPUT=(*.name)), but could not find the associated //name output statement in the JCL to capture the parameters.System action
The JCL analyzer ignores the OUTPUT= parameter specification associated with the SYSOUT DD statement and continues processing.User response
Correct the JCL, then retry the operation.EQAUT3103W Could not read DD DDITV02 for DB2/IMS
Explanation
The scanner recognizes batch invocation of IMS (DFSRRC00) and will examine the PARM= data to identify the run unit and PSB name. When run unit DSNMVT01 is detected in the parameter data, the scanner will also look for DDITV02 DD to identify the actual DB2® run unit name. The scanner did not find DDITV02 DD on the job step.System action
Processing continues.User response
None.EQAUT3104W Could not read DD DDITV02
Explanation
The scanner recognizes batch invocation of IMS (DFSRRC00) and will examine the PARM= data to identify the run unit. When DSNMVT01 is detected in the parameter data, the scanner will also look for DDITV02 DD on the job step to identify the actual DB2® run unit name. DDITV02 DD was found but the read failed.System action
Processing continues.User response
None.EQAUT3105W Could not substitute DB2 run unit for DSNMVT01
Explanation
The scanner recognizes batch invocation of IMS (DFSRRC00) and will examine the PARM= data to identify the run unit. When DSNMVT01 is detected in the parameter data, the scanner will also look for DDITV02 DD on the job step to identify the actual DB2® run unit name. If DDITV02 DD is not found, does not specify a DSN= parameter, or the DSN specified is a temporary file, no run unit name substitution is available. This message can be paired with DMH1447W or DMH1448W.System action
Processing continues.User response
None.EQAUT3108W Could not find IMS program name
Explanation
The scanner recognizes batch invocation of IMS (DFSRRC00) and will examine the PARM= data to identify the run unit. No PARM= statement was found. DFSRRC00 is the run unit assigned to the job step.System action
Processing continues.User response
None.EQAUT3109W Could not find IMS PSB name name
Explanation
The scanner recognizes batch invocation of IMS (DFSRRC00) and will examine the PARM= data to identify the run unit and PSB name. The scanner did not find a PSB name coded.System action
Processing continues.User response
None.EQAUT3110E Internal error
Explanation
This is an internal error of the application.System action
Scanning terminates for the current file, and processing continues.User response
Contact IBM Software Support.EQAUT3111E Override not proceeded by named DD stmt
Explanation
A JCL override statement was found which referred to a non-existent DD name.System action
The analysis scan is terminated.User response
Correct invalid JCL and reanalyze.EQAUT3112E Open failure on DD:ATTRBOUT, specifies MA flat file
Explanation
The file cannot be opened. The DD statement for ATTRBOUT is a temporary data set established to hold JCL analyzer import records. Possible causes are:- The user does not have proper authority to allocate the file.
- There is a system storage problem.
System action
Processing is stopped.User response
Verify and correct the cause, then retry the operation.EQAUT3113I Open failure on DD:RDPRINT, specifies logfile
Explanation
The file cannot be opened. The DD statement for RDPRINT is a temporary data set established to hold JCL analyzer import records. Possible causes are:- The user does not have proper authority to allocate the file.
- There is a system storage problem.