Data Center Management Systems
The Expert JCL Manager - JED |
The following list represents the error messages displayed from DCMS/JED regarding JCL errors, environmental problems and runtime issues. These messages may appear on the batch-invoked reports and online-invoked screens. Here is the format of each message entry:
Message ID – Unique message identifier
Message severity - (F)atal, (E)nvironmental, (W)arning ,(I)nformational
Message text
JEDxxxxxs tttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttt
REASON: Why this message was displayed
OPTIONS: What JED options are related to this error
RECOVERY: What you can do to eliminate the error
JED10001F MEMBER MISSING FROM LIBRARY
REASON: Member cannot be located on designated library.
OPTIONS: ACCESS,LIBRARY,DDNAME-LIBRARY
RECOVERY: Correct member name or library DSNAME.
JED10002F PROTECTED LIBRARY MEMBER
REASON: Panvalet member is access-protected.
OPTIONS: (none)
RECOVERY: Use 'ACC' keyword on execution parm to specify
access code.
JED10003F #nnnnn INVALID LIBRARY SPECIFICATION = ddname
REASON: The specified library ddname does not follow the required
standard format of 'xxxDDyyy', where 'xxx' is PAN, LIB, PDS
or SEQ, 'DD' is a required literal, and 'yyy' is 1-3 byte
alphanumerics. The error occurred on the 'nnnnn'th record
within the SYSIN file.
OPTIONS: (none)
RECOVERY: Correct the library name in the SYSIN file.
JED10004F #nnnnn INCLUDE/EXCLUDE TABLE FULL
REASON: The maximum number of INCLUDE and EXCLUDE statements has
been exceeded at the 'nnnnn'th record within the SYSIN file.
OPTIONS: (none)
RECOVERY: Correct the SYSIN file.
JED10005I NO ERRORS ENCOUNTERED
REASON: The member was edited/reformatted without errors.
OPTIONS: PRINT
RECOVERY: (none)
JED10006E PROCLIB=PROCxx NOT DEFINED
REASON: Either a /*JOBPARM PROCLIB=PROCxx or a TABLE-JOBCLASS=c=xx
indicated that PROCxx should be use but it was not defined.
OPTIONS: SYNTAX
RECOVERY: Correct TABLE-JOBCLASS or /*JOBPARM or define datasets for\
PROCLIB number 'xx' with TABLE-PROCLIB options.
JED10007F JOB STATEMENT MISSING - SYNTAX NOT USED
REASON: Syntax check can only be performed on JOBs or PROCs.
OPTIONS: SYNTAX
RECOVERY: Insert a JOB statement or change parm class to
'PROC'.
JED10010F CONTROL-M INTERFACE FAILED
REASON: A severe error occurred in attempting to use
CONTROL-M to extract the JCL member.
Implement-ControlM turned off.
OPTIONS: IMPLEMENT-CONTROLM
RECOVERY: Inspect the SYSPRINT output to determine the cause
of the error.
JED10011I PROCESSING BYPASSED DUE TO PROFILE=NONE
REASON: The member was not processed because the PROFILE=NONE was
specified in the execution PARM or by automatic profile
selection or (if IMPLEMENT-CCS=YES) in the EDITMBR parameter
of the associated Type Table entry or installation options.
OPTIONS: PROFILE or EDITMBR AND IMPLEMENT-CCS
RECOVERY: Insure that the CCS Installation options (GSCCTOPT) specifies
an options member name for the EDITMBR keyword. Insure that
the associated Type table (GSCCTTYP) entry specifies a valid
options member name.
JED10012F UNDEFINED/UNALLOCATED LIBRARY
REASON: The member could not be accessed on the designated
library. The message DDNAME indicates the library
in error.
OPTIONS: (none)
RECOVERY: Insure that the edit options member specifies the
correct library to be accessed for this member.
JED10014F FAILURE IN JCL xxxxxxxx
REASON: Failure detected while using the 'xxxxxxxx'
component of the syntax routine.
OPTIONS: SYNTAX
RECOVERY: Contact DCMS support.
JED10015F #nnnnn message-text
REASON: The 'nnnnn'th record within the SYSIN file contains
a syntax error. The possible values for 'message-text' are:
END MEMBER BEFORE START MEMBER - The ending member in a range
must be a higher value than the starting member.
INVALID CONTINUATION - A SYSIN record must end with a space.
INVALID DATE SPECIFICATION - The date value must be a valid date
in MMDDYY, MMDDYYYY, MM/DD/YY or MM/DD/YYYY format.
RANGE REQUIRES EQUAL COMPARE - Less than or greater than symbol
not valid prior to member range (from-to).
REQUIRED MEMBER MISSING - INCLUDE/EXCLUDE not valid without
a member value.
WILDCARD INVALID WITHIN END MEMBER - JED does not support the
use of wildcards within the end member of a range.
WILDCARD REQUIRES EQUAL COMPARE - Less than or greater than
symbol not valid prior to wildcarded member.
OPTIONS: (none)
RECOVERY: Correct SYSIN file.
JED10017W OUTPAN UPDATE FAILED FOR xxxxxxxx
REASON: A high return code was received from utility PAN#1 while
updating member 'xxxxxxxx' on the OUTPAN library.
OPTIONS: DDNAME-OUTPAN
RECOVERY: Insert JEDPRINT SYSOUT DD and re-run to determine the cause
of the error.
JED10018W OUTLIB UPDATE FAILED FOR xxxxxxxx
REASON: A high return code was received from utility LIBRPROG while
updating member 'xxxxxxxx' on the OUTLIB library.
OPTIONS: DDNAME-OUTLIB
RECOVERY: Insert JEDPRINT SYSOUT DD and re-run to determine the cause
of the error.
JED10100F JED AUTHORIZATION FAILURE
REASON: DCMS/JED is not authorized for use on the current
CPU.
OPTIONS: (none)
RECOVERY: Contact DCMS support.
JED10301F PROCLIB DD STATEMENT ERROR
REASON: An unspecified error has been detected with the use
of the PROCLIB DD statement concatenation.
OPTIONS: (none)
RECOVERY: Correct PROCLIB DD statement(s).
JED10405F INSTREAM PROC=xxxxxxxx NOT USED
REASON: Procedure 'xxxxxxxx' was defined as an instream proc
in this job but it was not subsequently referenced.
OPTIONS: VERIFY-INSTREAM
RECOVERY: Correct EXEC statement.
JED10615W UNSUPPORTED CA-7 CONTROL STATEMENT AT COLUMN nn
REASON: The CA-7 #JI/#JO/#XI/#XO statement contains criteria
that is not supported by JED. The error was
detected in column 'nn'
OPTIONS: VERIFY-CA7
RECOVERY: Contact DCMS for assistance.
JED10616F INVALID CA-7 CONTROL STATEMENT AT COLUMN nn
REASON: The CA-7 #JI/#JO/#XI/#XO statement contains a syntax
error. The error was detected in column 'nn'.
OPTIONS: VERIFY-CA7
RECOVERY: Correct the CA-7 control statement.
JED10617W CA-7 SIMULATION INCOMPLETE
REASON: More than 100 unique criteria are used in the JCL
member. Only the first 100 are used.
OPTIONS: VERIFY-CA7
RECOVERY: Contact DCMS for assistance.
JED10618F ++INCLUDE MEMBER NOT FOUND = xxxxxxxx
REASON: A ++INCLUDE statement could not be processed because
the included member 'xxxxxxxx' was not found on the
include library (xxxDDn#n).
OPTIONS: (any)
RECOVERY: Provide an include library DD statement referencing
the library where the included member resides.
JED10619F ++INCLUDE STATEMENT FORMAT ERROR
REASON: JED detected a ++INCLUDE statement containing a syntax
error. The member name must be delimited by spaces.
OPTIONS: (any)
RECOVERY: Correct the ++INCLUDE statement.
JED10620F JOB STATEMENT COLUMNS 70-71 NOT BLANK FOR CA-7
REASON: CA-7 requires that the first record of the JOB statement
contains spaces in columns 70 thru 71.
OPTIONS: VERIFY-CA7
RECOVERY: Correct the JOB statement.
JED20001W JES2 STATEMENT ENCOUNTERED
REASON: A JES2 statement was encountered in the JCL when the
installation options indicate a JES3 environment.
OPTIONS: (none)
RECOVERY: Correct or remove the JES2 statement.
JED20002E SERVER NOT ACTIVE
REASON: The JEDSERV task associated with the IMPLEMENT-JEDSERV
option is not active and cannot be used. This message
causes JED to terminate immediately with RC=16.
OPTIONS: IMPLEMENT-JEDSERV
RECOVERY: Start JEDSERV task or remove IMPLEMENT-JEDSERV option.
JED20004I UNRECOGNIZED MODULE CLASS - JOB ASSUMED
REASON: The Class parameter was set to a value other than
PROC or JOB. It was reset to JOB.
OPTIONS: (none)
RECOVERY: Correct the class value in the execution parm.
JED20008W JED OPTION UNRECOGNIZED - IGNORED
REASON: //*JED encountered in JCL, but stated option
unrecognized.
OPTIONS: (none)
RECOVERY: Correct //*JED statement within edited JCL.
JED20009W STATEMENTS ENCOUNTERED AFTER // NULL
REASON: Member contains one or more JCL and/or DATA
statements after the // (null) job terminator.
These statements are ignored by the operating
system.
OPTIONS: (none)
RECOVERY: Correct // NULL statement or remove statements after
it.
JED20016I OVERRIDE DETECTED = xxxx ...
REASON: //*JED encountered in JCL.
OPTIONS: (none)
RECOVERY: (none)
JED20101F JOB STATEMENT MISSING OR INVALID
REASON: Class=JOB was specified but the Job statement not
found before first EXEC or first DD statement.
OPTIONS: (none)
RECOVERY: Insert JOB statement or change class to 'PROC'.
JED20102F MORE THAN ONE JOB STATEMENT ENCOUNTERED
REASON: Your installation does not permit multiple JOB
statements within a single member.
OPTIONS: INHIBIT-MULTJOBS
RECOVERY: Separate jobs into multiple members.
JED20103F NON-STANDARD JOBNAME AT COL=nn
REASON: The specified JOB name does not meet naming standards
defined by your site.
OPTIONS: VERIFY-JOBSTD
RECOVERY: Correct the job name.
JED20104F INVALID MSGCLASS = X
REASON: Msgclass on JOB statement has non-standard value.
OPTIONS: VERIFY-MSGCLASS
RECOVERY: Correct Msgclass or add class to 'Verify Msgclass' list.
JED20107F INVALID JOBCLASS = X
REASON: Class on JOB statement has non-standard value.
OPTIONS: VERIFY-JOBCLASS
RECOVERY: Correct Class or add class to 'Verify Jobclass'
list.
JED20115F MSGCLASS MISSING FROM JOB STATEMENT
REASON: Msgclass must be coded on JOB statement and it has
been omitted.
OPTIONS: VERIFY-MSGCLASS
RECOVERY: Add Msgclass keyword to JOB statement.
JED20116F CLASS MISSING FROM JOB STATEMENT
REASON: Class must be coded on JOB statement and it has been
omitted.
OPTIONS: VERIFY-JOBCLASS
RECOVERY: Add Class keyword to JOB statement.
JED20117W COND KEYWORD MISSING FROM JOB STATEMENT
REASON: The JOB statement in this member is missing a COND
keyword, as required by your shop's standards.
OPTIONS: VERIFY-JOBCOND
RECOVERY: Add COND keyword to JCL.
JED20118F MEMBER NAME MUST MATCH JOBNAME
REASON: Name on JOB statement did not match member name.
OPTIONS: VERIFY-MEMBER
RECOVERY: Correct JOB statement.
JED20119F MEMBER INVALID JOBNAME SPECIFICATION
REASON: Label field on JOB statement must be upper case, beginning
with alphabetic.
OPTIONS: (none)
RECOVERY: Correct JOB statement.
JED20200I DSN=&& ASSUMED
REASON: A DSN=&value was found and the symbolic was not resolved.
JED will assume that the dataset is temporary and has
internally renamed it to DSN=&&value.
OPTIONS: (none)
RECOVERY: Correct the DSN or supply a value for the unresolved
symbolic.
JED20201E UTILITY DD REFERENCE MISSING = xxxxxx
REASON: A DD statement is missing for a VOL= reference within a
standard IBM utility. The value 'xxxxxx' is the volume
serial number required on a DD statement.
OPTIONS: VERIFY-UTILITY
RECOVERY: Correct the VOL reference within the utility control
statements or add the required DD statement.
JED20204W DD STATEMENT MISSING - ddname
REASON: The executed program apparently requires a DD statement
that is not present. The Warn option uses the CCS
PGMSCAN file and UTILITY options to determine which DD's
are used.
OPTIONS: WARN-MISSING
RECOVERY: Add DD statement to step or remove 'dead' code which
opens the file from the executed source program.
JED20209E PROGRAM VERIFICATION BYPASSED DUE TO MISSING LOADLIB
REASON: JED is unable to check for the existence of the
executed program due to a previously reported error
with a STEPLIB or JOBLIB library.
OPTIONS: VERIFY-PROGRAM
RECOVERY: Correct JOBLIB/STEPLIB dataset name or allocate this
PDS.
JED20210I XXXXXXXX LOCATED IN LINK-LISTED LIBRARY #nn
REASON: The indicated program was not found in any STEPLIB
or JOBLIB but it was found in system Link-Listed
library number 'nn'. The 'nn' value is the concatenation
number of the library in the link-list.
OPTIONS: VERIFY-PROGRAM and/or PRINT-LOCATION
RECOVERY: (none)
JED20211I XXXXXXXX LOCATED IN dsname
REASON: The indicated program was found in STEPLIB or JOBLIB
dataset 'dsname'.
OPTIONS: VERIFY-PROGRAM and PRINT-LOCATION
RECOVERY: (none)
JED20212E XXXXXXXX NOT FOUND IN LINKLIST
REASON: The indicated program was not found and no STEPLIB
or JOBLIB was specified.
OPTIONS: VERIFY-PROGRAM
RECOVERY: Correct spelling of program name or add
JOBLIB/STEPLIB to JCL.
JED20213E XXXXXXXX NOT FOUND IN JOBLIB/STEPLIB
REASON: The indicated program was not found in the specified
STEPLIB or JOBLIB libraries.
OPTIONS: VERIFY-PROGRAM
RECOVERY: Correct spelling of program name or add
JOBLIB/STEPLIB to JCL.
JED20214E XXXXXXXX NOT IN PRODUCTION
REASON: The indicated program is not currently defined to
CCS as a module type with class of 'PROGRAM'.
OPTIONS: VERIFY-CCSPGM
RECOVERY: Using CCS.4, add program as module type 'SOFTWARE'.
JED20215E XXXXXXXX NOT EXECUTABLE
REASON: The indicated program is currently marked non-executable
in the load library directory.
OPTIONS: VERIFY-PROGRAM
RECOVERY: Correct and re-link program.
JED20217F REQUIRED STEPLIB MISSING
REASON: The executed program is defined to CCS as module
type 'SOFTWARE' and a class of 'AUTH', indicating
that an APF- Authorized STEPLIB should have been
used. The STEPLIB is missing.
OPTIONS: TABLE-AUTHLIB
RECOVERY: Add required STEPLIB or remove class from associated
module record thru CCS.4.
JED20218F DUPLICATE EXEC KEYWORD ENCOUNTERED
REASON: The EXEC statement at this step duplicates one or
more keywords.
OPTIONS: (none)
RECOVERY: Remove extraneous EXEC statement keyword.
JED20219F COND KEYWORD MISSING FROM EXEC STATEMENT
REASON: The EXEC statement at this step is missing a COND
keyword, as required by your shop's standards.
OPTIONS: VERIFY-EXECCOND
RECOVERY: Add COND keyword to JCL.
JED20300F DSNAME VALUE TOO LONG
REASON: The value specified for the DSN keyword is longer
than permitted by the operating system. For a GDG
base, the maximum length is 35. For all other
dsnames, the maximum length is 44.
OPTIONS: (none)
RECOVERY: Correct the DSN value and retry.
JED20301F DATASET GENERATION NOT YET CREATED
REASON: A plus-generation dataset is being reference with
DISP=SHR or DISP=OLD. The generation was not
created with DISP=NEW in a prior jobstep.
OPTIONS: VERIFY-USAGE
RECOVERY: The generation number is probably invalid.
JED20302F SUBSYS=CCSS NOT SUPPORTED
REASON: Your site has determined that the Control Card
Sub-System is not to be used.
OPTIONS: INHIBIT-CCSS
RECOVERY: Remove SUBSYS=CCSS parameter.
JED20303F PREVIOUS GENERATION NOT YET CREATED
REASON: A plus-two (or higher) dataset is being created but
the previous relative generation was not created
with DISP=NEW in a prior jobstep.
OPTIONS: VERIFY-USAGE
RECOVERY: The generation number is probably invalid.
JED20304W DISP KEYWORD MISSING
REASON: The DISP keyword is not coded on this DD statement.
Because DSN is coded, this omission is probably an
error.
OPTIONS: (none)
RECOVERY: Add the DISP keyword.
JED20305W DUPLICATE KEYWORD ENCOUNTERED
REASON: The indicated DD statement duplicates one or more
keywords.
OPTIONS: (none)
RECOVERY: Remove extraneous DD statement keywords.
JED20306W SECURED UTILITY INPUT DATASET
REASON: The dataset containing input statements for IDCAMS
or IKJEFTxx is read-protected. JED cannot read
the file to validate the statements.
OPTIONS: VERIFY-IDCAMS, VERIFY-PROGRAM
RECOVERY: Grant JED read-access to the file.
JED20307F SYSOUT USED IN CONCATENATION
REASON: A SYSOUT= parameter was encountered within a
concatenation of datasets when only input files
are valid.
OPTIONS: (none)
RECOVERY: DDname is probably missing.
JED20308W NEW/MOD USED IN CONCATENATION
REASON: DISP=NEW or DISP=MOD was encountered within a
concatenation of datasets when only input files
are valid.
OPTIONS: (none)
RECOVERY: DDname is probably missing.
JED20309W SECONDARY BLKSIZE GREATER THAN PRIMARY
REASON: The BLKSIZE value of dataset within a
concatenation is larger than the BLKSIZE of the
first dataset in the concatenation.
OPTIONS: (none)
RECOVERY: Add larger BLKSIZE value to primary DD.
JED20310F CONCATENATION INVALID AFTER DUMMY
REASON: A DUMMY parameter was used in a previous DD of this
concatenation. Subsequent DD's in the concatenation
are invalid.
OPTIONS: (none)
RECOVERY: DDname is probably missing.
JED20311F DYNAM USED IN CONCATENATION
REASON: A DYNAM parameter was used in the primary DD for a
concatenation of datasets. This is illegal.
OPTIONS: (none)
RECOVERY: Remove DYNAM parameter.
JED20312F DCB/AMP INCOMPATIBLE
REASON: The use of DCB= and AMP= on the same DD statement is
illegal.
OPTIONS: (none)
RECOVERY: Remove either DCB or AMP parameter.
JED20313F DCB/DYNAM INCOMPATIBLE
REASON: The use of DCB= and DYNAM on the same DD statement is
illegal.
OPTIONS: (none)
RECOVERY: Remove either DCB or DYNAM parameter.
JED20314F DCB/xxxxxxxx CONFLICT
REASON: The use of DCB 'xxxxxxxx' keyword and another DD
statement parameter is not valid.
OPTIONS: (none)
RECOVERY: Remove the conflicting DCB parameter.
JED20315E UNDEFINED LIKE DSN=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
REASON: The dataset name specified in the LIKE
parameter does not exist.
OPTIONS: VERIFY-MDLDCB
RECOVERY: Correct the dataset name in the LIKE parameter
for this DD statement.
JED20316W CODED BLKSIZE LESS THAN ACTUAL
REASON: The BLKSIZE value found in the JCL is less than
the value found in the dataset's DSCB.
OPTIONS: (none)
RECOVERY: Correct the BLKSIZE value for this DD statement.
JED20317W DATASET IS NOT PARTITIONED
REASON: The DSNAME parameter includes a member name, but
the dataset is not DSORG=PO.
OPTIONS: VERIFY-PDS
RECOVERY: Correct the DSN or remove the member.
JED20318E MEMBER SPECIFIED BUT DISP=NEW OR MOD
REASON: When DISP=NEW or DISP=MOD, the PDS member must not
be specified on the DSN.
OPTIONS: VERIFY-PDS
RECOVERY: Remove the member name or change the DISP value.
JED20319W IMPROPER USE OF PARTITIONED DATASET
REASON: DSNAME member not specified but DISP=MOD will cause
the loss of the member from the directory.
OPTIONS: VERIFY-PDS
RECOVERY: Add the member name or change the DISP value.
JED20320F XXXXXXXX IS AN INVALID FORM NAME
REASON: The DD SYSOUT statement references a form name that
is not defined in the JED Form/FCB table.
OPTIONS: VERIFY-FORM
RECOVERY: Correct the Form name in the JCL or have the Form
name added to the JED Form/FCB table.
JED20321F INVALID OUTCLASS = X
REASON: The DD SYSOUT statement references a class which is
invalid.
OPTIONS: VERIFY-OUTCLASS
RECOVERY: Correct the SYSOUT class in the JCL or add the class
to the 'Verify Outclass' list.
JED20322W LIBRARY WILL BE DELETED
REASON: The specified dataset is partitioned and the normal
disposition value is DELETE. Upon normal step
termination, the dataset will be deleted.
OPTIONS: VERIFY-PDS
RECOVERY: Change the DSNAME or the DISP value.
JED20323W CODED RECFM DIFFERENT THAN ACTUAL
REASON: The dataset is coded with a RECFM parameter that is
different than the value found in the dataset's
DSCB. This is probably an error.
OPTIONS: (none)
RECOVERY: Correct or remove the RECFM parameter.
JED20324W AMP USED FOR NON-VSAM DATASET
REASON: The dataset is coded with a AMP parameter but the
dataset's DSCB shows it is not a VSAM file. AMP
can only be used with VSAM.
OPTIONS: (none)
RECOVERY: Remove the AMP parameter.
JED20325F AFF DDNAME NOT PRESENT
REASON: The dataset is coded with a AFF parameter but the
DDNAME it references is not present in the step JCL.
OPTIONS: (none)
RECOVERY: Correct the AFF parameter.
JED20326F AFF USED FOR NEW DISK FILE
REASON: The dataset is coded with DISP=NEW and an AFF
parameter but the DDNAME it references is on
disk. This is illegal.
OPTIONS: (none)
RECOVERY: Correct or remove the AFF parameter.
JED20327F AFF USED FOR INSTREAM FILE
REASON: The dataset is coded with an AFF parameter and
either 'DD *' or 'DD DATA' This is illegal.
OPTIONS: (none)
RECOVERY: Correct or remove the AFF parameter.
JED20328W SPECIFIED VOLUME(S) NOT CATALOGED VOLUME(S)
REASON: The dataset's coded SER= volume name(s) is/are not the same
as the volume(s) to which the dataset is currently
cataloged. This is or will cause a duplicate file.
OPTIONS: (none)
RECOVERY: Correct or remove the SER parameter.
JED20329W EXTRANEOUS LABEL FOR CATALOGED DATASET
REASON: The dataset specifies LABEL>1 but has no SER= or REF=
parameter. When accessing the dataset thru the catalog
the LABEL parameter should not be used.
OPTIONS: (none)
RECOVERY: Correct or remove the LABEL parameter.
JED20330F INVALID UNIT NAME = XXXXXXXX
REASON: The Unit name specified on this DD statement does
not exist in a list of valid unit names.
OPTIONS: VERIFY-UNIT
RECOVERY: Correct the Unit name in the JCL or add the
name to the Unit Table.
JED20331F INVALID UNIT NAME = XXXXXXXX
REASON: The Unit name specified on this DD statement is not
defined to the system device table.
OPTIONS: VERIFY-SYSUNIT
RECOVERY: Correct the Unit name in the JCL.
JED20332W TEMPORARY PDS OR UNRESOLVED SYMBOLIC
REASON: The DD statement uses DSN=&, which is either a
temporary partitioned dataset or a symbolic that has
not been resolved. If this is a temporary PDS, this
is not a problem An unresolved symbolic will cause
the JOB to fail with a 'Dataset Not Found' error.
OPTIONS: VERIFY-PDS
RECOVERY: Insure dataset does not use an unresolved symbolic.
JED20333W DIRECTORY SPACE FOR SEQUENTIAL FILE
REASON: The DD statement specifies directory blocks in the
SPACE parameter but has DSORG=PS. A sequential file
cannot have directory space.
OPTIONS: (none)
RECOVERY: Correct the DSORG or the SPACE parameter.
JED20334W DISP FIELD INCOMPATIBLE WITH DSNAME
REASON: The DD statement specifies DISP=(,CATLG) but the DSN
is invalid or missing.
OPTIONS: (none)
RECOVERY: Correct the DSN or DISP parameter.
JED20335F DDNAME KEYWORD COUNT EXCEEDS MAXIMUM
REASON: A jobstep may have no more than 5 DDNAME= keywords.
OPTIONS: (none)
RECOVERY: Remove the DDNAME keyword.
JED20336W UNIT MISSING FOR NEW/MOD DATASET
REASON: The Unit name is missing on this DD statement. A
Disp=New dataset always requires a Unit. A Disp=Mod
dataset will require a Unit if the dataset doesn't
exist at execution time. Your site standards
requires that the Unit be present
OPTIONS: IMPLEMENT-CATLG
RECOVERY: Add a Unit keyword to the JCL.
JED20337E UNALLOCATED PDS DSN=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
REASON: The Partitioned Dataset (PDS) referenced by this DD
statement does not exist.
OPTIONS: VERIFY-PDS
RECOVERY: Correct the PDS dataset name or create the PDS.
JED20338F NON-STANDARD PDS DSN=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
REASON: The Partitioned Dataset (PDS) referenced by this DD
statement cannot be used in production JCL at your
site because the dataset is not exist is a list of
valid PDS's.
OPTIONS: VERIFY-PDSLIST
RECOVERY: Correct the PDS dataset name or add the PDS to the
JED options member.
JED20339W MEMBER VERIFICATION BYPASSED
REASON: SUBSYS=LAM is not supported during interactive
invocation of JED. Library member(s) may not be
present.
OPTIONS: VERIFY-PDS
RECOVERY: Manually verify library member existance.
JED20340F NON-STANDARD AT QUAL#x-CHAR#y DSN=XXXXXXXXXXXXXXXXXXXXXXXX
REASON: The Dataset referenced by this DD statement does not
meet dataset naming standards as defined by your
shop. The error was detected at DSNAME qualifier
number 'x', character 'y'.
OPTIONS: VERIFY-DSNAME
RECOVERY: Correct the dataset name or correct the JED DSNSTD
table.
JED20341E DEFINE MISSING DSN=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
REASON: Naming standards indicates that the Dataset
referenced by this DD statement is a VSAM file but
the Define member for this dataset is not known to
CCS.
OPTIONS: VERIFY-DEFINE AND CCS PRESENT
RECOVERY: Correct the dataset name or add a Define member to
CCS containing the IDCAMS Defines statement that
creates this file.
JED20342E GDG BASE UNDEFINED DSN=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
REASON: The Dataset referenced by this DD statement is a
Generation Data Group (GDG) but the GDG base for the
dataset has not yet been defined.
OPTIONS: VERIFY-GDG
RECOVERY: Correct the dataset name or use an IDCAMS 'Define
GDG' command to create the GDG base.
JED20343F MODEL DCB REQUIRED FOR NEW GENERATION
REASON: The Dataset referenced by this DD statement is a
Generation Data Group (GDG) and a new generation is
being created. MVS requires that new GDG
generations be created with a model DC dataset name
and this information is not present.
OPTIONS: VERIFY-MDLDCB
RECOVERY: Add a model dataset name to the DCB parameters for
this DD statement.
JED20344E UNDEFINED MODEL DCB DSN=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
REASON: The Dataset referenced by this DD statement is a
Generation Data Group (GDG) and a new generation is
being created. The model dataset name specified in
the DCB parameters does not exist.
OPTIONS: VERIFY-MDLDCB
RECOVERY: Correct the model dataset name in the DCB parameters
for this DD statement.
JED20345F EXPDT=99000 REQUIRED FOR NEW TAPE GENERATION
REASON: The Dataset referenced by this DD statement is a
Generation Data Group (GDG) and a new generation is
being created. Your site requires that a RETPD
keyword or a EXPDT=99000 be present under these
conditions.
OPTIONS: ENFORCE-EXPDT
RECOVERY: Add or correct the EXPDT keyword to the DD
statement.
JED20346I UNUSED DD STATEMENT = ddname
REASON: The executed program does not apparently use the
specified DD statement. The Warn option uses the CCS
PGMSCAN file and UTILITY options to determine which DD's
are used.
OPTIONS: WARN-UNUSED
RECOVERY: Determine if the DD statement is in use and delete
it if is not.
JED20347F EXPDT=99365 INVALID FOR CATALOGED TAPE
REASON: Your site prohibits the use of EXPDT=99365 to create
permanently cataloged tapes.
OPTIONS: ENFORCE-EXPDT
RECOVERY: Remove or correct the EXPDT keyword on the DD
statement.
JED20348E XXXXXXXX MISSING FROM XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
REASON: The indicated member was not found on the specified
PDS.
OPTIONS: VERIFY-PDS
RECOVERY: Correct the spelling of the member name or the PDS
Dsname.
JED20349E JOBLIB DATASET NOT LOCATED DSN=xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
REASON: The Dataset referenced by this JOBLIB DD statement
is not cataloged.
OPTIONS: VERIFY-PROGRAM
RECOVERY: Correct JOBLIB DSN.
JED20350I DATASET NOT AVAILABLE FOR UTILITY VERIFICATION
REASON: The indicated dataset could not be accessed. The dataset
must be mounted, LRECL=80, DSORG=PS and accessible by JED.
OPTIONS: VERIFY-IDCAMS, VERIFY-PROGRAM
RECOVERY: (none)
JED20351I MEMBER NOT AVAILABLE FOR UTILITY VERIFICATION
REASON: The indicated PDS member could not be accessed. The
PDS must be mounted, LRECL=80, DSORG=PO and
accessible by JED.
OPTIONS: VERIFY-IDCAMS, VERIFY-UTILITY
RECOVERY: (none)
JED20352E STEPLIB DATASET NOT LOCATED DSN=xxx
REASON: The specified STEPLIB dataset is not cataloged. JED
is unable to determine if the executed program exists.
OPTIONS: VERIFY-PROGRAM
RECOVERY: Correct STEPLIB dsname.
JED20353F TEMPORARY GDG OR UNRESOLVED SYMBOLIC
REASON: The DD statement uses DSN=&, which is either a
generation data group or a symbolic that has not
been resolved. Temporary GDG's are not permitted,
An unresolved symbolic will cause the JOB to fail
with a 'Dataset Not Found' error.
OPTIONS: VERIFY-PDS
RECOVERY: Insure dataset does not use an unresolved symbolic.
JED20354W SPACE MISSING FOR NEW/MOD DISK DATASET
REASON: The Space keyword is missing on this DD statement.
A Disp=New disk dataset always requires Space. A
Disp=Mod dataset requires Space if the dataset
doesn't exist at execution time. Your site
standards requires that Space be present.
OPTIONS: IMPLEMENT-CATLG
RECOVERY: Add a Space keyword to the JCL.
JED20355W DUPLICATE DD ENCOUNTERED = ddname
REASON: More than one DD statement with this DDNAME has been
found in the current step. Only the first occurance
is used --- any secondary duplicate DD's are ignored
by MVS.
OPTIONS: WARN-DUPDDS
RECOVERY: Delete the invalid DD statement.
JED20356F BLKSIZE NOT SPECIFIED
REASON: Your site requires a BLKSIZE parameter be included
when new files are created. It is missing on this
DD statement.
OPTIONS: ENFORCE-BLKSIZE
RECOVERY: Add the Blksize keyword to the DD statement.
JED20357W SECURED CONTROL INPUT DATASET
REASON: The dataset containing CONTROL statements is
read-protected. JED cannot read the file to validate the
statements.
OPTIONS: PRINT-CONTROL
RECOVERY: Grant JED read-access to the file.
JED20358F REFERENCED DDNAME=dddddddd MISSING
REASON: The job step contained a DDNAME=dddddddd, but a DD statement
for ddname 'dddddddd' was not encountered in the step.
OPTIONS: (none)
RECOVERY: Correct DDNAME= parameter or add DD statement.
JED20359F DUPLICATED DDNAME=dddddddd
REASON: The job step contained a DDNAME=dddddddd, but the specified
ddname 'dddddddd' was already used on a DDNAME= during the
current step.
OPTIONS: (none)
RECOVERY: Correct DDNAME= parameter.
JED20360W ERROR ACCESSING CONTROL INPUT DATASET
REASON: JED detected an error in attempting to read the
CONTROL input file for the current step.
OPTIONS: PRINT-CONTROL
RECOVERY: Contact DCMS.
JED20361F INVALID SMS DATACLASS
REASON: The DATACLAS value specified in the JCL is not defined to SMS.
OPTIONS: VERIFY-SMS
RECOVERY: Correct DATACLAS value.
JED20362F INVALID SMS MGMTCLASS
REASON: The MGMTCLAS value specified in the JCL is not defined to SMS.
OPTIONS: VERIFY-SMS
RECOVERY: Correct MGMTCLAS value.
JED20363F INVALID SMS STORCLASS
REASON: The STORCLAS value specified in the JCL is not defined to SMS.
OPTIONS: VERIFY-SMS
RECOVERY: Correct STORCLAS value.
JED20364F INVALID DMPCLASS = X
REASON: The DD SYSOUT statement references a class that is
invalid for DDNAME SYSUDUMP or SYSABEND.
OPTIONS: VERIFY-DMPCLASS
RECOVERY: Correct the SYSOUT class in the JCL or add the class
to the 'Verify Dmpclass' list.
JED20365F UNDEFINED DATASET ALIAS=xxx
REASON: The high-level qualifier of the dataset name is not
defined as an alias in the master catalog. The
JOB's attempt to catalog the file requires update
authority to the system master catalog.
OPTIONS: INHIBIT-MASTERCAT
RECOVERY: Correct the dataset name or define the alias to the
master catalog.
JED20367F NEW DATASET STILL EXISTS
REASON: The DD statement attempts to create a dataset that has
not been deleted since it's previous jcl reference.
OPTIONS: VERIFY-USAGE
RECOVERY: Correct the previous use of the dataset in the JCL to
delete the dataset.
JED20368F TEMPORARY DATASET DOES NOT EXIST
REASON: The DD statement attempts to access a temporary
dataset that was never created or was been deleted
in a prior step.
OPTIONS: VERIFY-USAGE
RECOVERY: Correct the previous use of the dataset in the JCL
to PASS the dataset.
JED20369F DATASET PREVIOUSLY DELETED
REASON: The DD statement attempts to access a dataset that
was deleted in a prior step.
OPTIONS: VERIFY-USAGE
RECOVERY: Correct the previous use of the dataset in the JCL
to KEEP the dataset.
JED20370W INPUT FILE REFERS TO OUTPUT DD
REASON: The program indicates this is an input file but the
JCL DD statement uses DISP=NEW, DISP=MOD or SYSOUT.
The program information is obtained from a UTILITY
option or from the CCS PGMSCAN file.
OPTIONS: VERIFY-USAGE
RECOVERY: Insure proper use of dataset.
JED20371W OUTPUT FILE REFERS TO INPUT DD
REASON: The program indicates this is an output file but the
JCL DD statement uses instream data. The program
information is obtained from a UTILITY option or
from the CCS PGMSCAN file.
OPTIONS: VERIFY-USAGE
RECOVERY: Insure proper use of dataset.
JED20372W WORK FILE REFERS TO QUEUE DD
REASON: The program indicates this is an I-O file but the
JCL DD statement uses instream data or SYSOUT. The
program information is obtained from a UTILITY
option or from the CCS PGMSCAN file.
OPTIONS: VERIFY-USAGE
RECOVERY: Insure proper use of dataset.
JED20373E oooooooo CANNOT ALTER CAT=XXXXXXXXXXXXX
REASON: The indicated catalog cannot be updated by the job. The
security system was queried for ALTER access to the
dataset alias for owner 'oooooooo'.
OPTIONS: VERIFY-ALIAS
RECOVERY: Modify security system to grant ALTER-access for the
dataset to the job
JED20374E INSUFFICIENT SPACE ON VOLUME
REASON: The specified volume does not contain an extent large
enough for the primary SPACE amount.
OPTIONS: VERIFY-SPACE
RECOVERY: Change VOL=SER value or move/delete data from volume.
JED20375W OUTPUT FILE REFERS TO GDG BASE
REASON: The program indicates this is an output file but the
JCL DD statement specifies an unqualified GDG base.
The program information is obtained from a UTILITY
option or from the CCS PGMSCAN file.
OPTIONS: VERIFY-USAGE
RECOVERY: Insure proper use of dataset.
JED20376W PGM=*.DDNAME REFERBACK IS NOT A PDS
REASON: The EXEC statement uses a program referback. The
referenced ddname was found but is not a PDS.
OPTIONS: (none)
RECOVERY: Correct the PGM= parameter.
JED20378F BLKSIZE NOT MULTIPLE OF LRECL
REASON: When RECFM=FB, BLKSIZE must be multiple of LRECL.
The indicated DD statement BLKSIZE is incorrected
specified.
OPTIONS: VERIFY-BLKSIZE
RECOVERY: Correct BLKSIZE value.
JED20379I NOT CATALOGED DSN=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
REASON: The indicated dataset does not currently exist in
system catalog. The JOB requires the dataset to
exist prior to execution.
OPTIONS: VERIFY-CATLG
RECOVERY: Create the dataset.
JED20380I ALREADY CATALOGED DSN=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
REASON: The indicated dataset already exists in system
catalog and the JOB creates the dataset. Executing
the JOB creates a duplicate dataset.
OPTIONS: VERIFY-CATLG
RECOVERY: Scratch the dataset.
JED20381W DUPLICATE DD ENCOUNTERED IN PROC = ddname
REASON: More than one DD statement with this DDNAME has been
found in the current PROC step. Only the first
occurance is used --- any secondary duplicate DD's
are ignored by MVS.
OPTIONS: WARN-DUPDDS REMOVE-DUPDDS
RECOVERY: Delete the invalid DD statement.
JED20382E VOLUME NOT MOUNTED= XXXXXX
REASON: The UNIT parameter indicates a DISK unit but the
specified volume is not currently mounted.
OPTIONS: VERIFY-UNIT
RECOVERY: Correct the Unit name or the SER value in the JCL.
JED20383E UNDEFINED VOL=REF DSN=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
REASON: The Dataset referenced in the VOL=REF parameter of
this DD statement could not be found in the system
catalog. The dataset name may be misspelled.
OPTIONS: VERIFY-STACKING
RECOVERY: Correct the dataset name in the VOL=REF parameter
for this DD statement.
JED20384F CREATING +0 GENERATION
REASON: This DD statement is creating a '+0' generation of a
GDG.
OPTIONS: VERIFY-GDG
RECOVERY: Correct the generation number.
JED20385W ERROR ACCESSING UTILITY INPUT DATASET
REASON: JED detected an error in attempting to read the
input file for the current utility program.
OPTIONS: VERIFY-IDCAMS, VERIFY-PROGRAM
RECOVERY: Contact DCMS.
JED20386E DATASET NOT ON SPECIFIED VOLUME
REASON: The indicated dataset was not found on the specified
disk volume.
OPTIONS: VERIFY-VOLUME
RECOVERY: Correct DD SER parameter.
JED20387E DATASET EXISTS ON SPECIFIED VOLUME
REASON: The indicated new dataset already exists on the
specified disk volume.
OPTIONS: VERIFY-VOLUME
RECOVERY: Correct DD SER parameter.
JED20388F VOLUME REFERBACK NOT FOUND
REASON: The DD statement REF= parameter cannot be resolved.
OPTIONS: VERIFY-STACKING
RECOVERY: Correct DD REF parameter.
JED20389F LABEL SEQUENCE INVALID
REASON: The DD statement LABEL parameter does not specify the correct
dataset sequence number. For multi-file volumes, the LABEL
value must be one greater than that specified on the previoud
output file.
OPTIONS: VERIFY-STACKING
RECOVERY: Correct DD LABEL parameter.
JED20390I RETAIN MISSING FOR VOLUME
REASON: The volume indicated by this DD statement is
appended with a subsequent DD but RETAIN is not
coded to prevent premature unloading during
execution.
OPTIONS: VERIFY-STACKING
RECOVERY: Add RETAIN to VOL parameter.
JED20391W UNIT=AFF MISSING
REASON: The volume indicated by this DD statement is
appended to a previous DD in this step but
UNIT=AFF=ddname is not coded to insure single output
device is used.
OPTIONS: VERIFY-STACKING
RECOVERY: Add UNIT=AFF parameter.
JED20392W UNIT=AFF INVALID
REASON: The volume indicated by this DD statement is
appended to a previous DD in this step but
UNIT=AFF=ddname coded does reference to correct
ddname.
OPTIONS: VERIFY-STACKING
RECOVERY: Correct UNIT=AFF parameter.
JED20393E SECURED PDS DSN=XXXXXXXXXXXXX
REASON: The indicated dataset is read-protected by your
security system. JED cannot inspect the library to
determine if the member/program exists.
OPTIONS: VERIFY-PDS, VERIFY-PGM
RECOVERY: Modify security system to grant read-access to the
JED job or user.
JED20394E oooooooo CANNOT aaaaaaa DSN=XXXXXXXXXXXXX
REASON: The indicated dataset cannot be accessed by the job
in the manner intended. The security system was
queried for 'aaaaaaa' access to the dataset for
owner 'oooooooo'.
OPTIONS: VERIFY-ACCESS
RECOVERY: Modify security system to grant 'aaaaaaaa'-access for
the dataset to the job
JED20395F INVALID DD DESTID
REASON: The indicated DD statement specifies a DEST value
that is not defined in the DEST table.
OPTIONS: VERIFY-DEST
RECOVERY: Correct DEST parameter on DD statement or add
destination to DEST table.
JED20396W VOL=REF DOES NOT REFERENCE PREVIOUS DATASET
REASON: The DD statement REF parameter does not refer to the
previoud dataset on the multi-file volume. If the
previous dataset spans to a new volume, the job will
fail.
OPTIONS: VERIFY-STACKING
RECOVERY: Correct DD REF= parameter.
JED20397F IMPROPER UNIT=name FOR xxxx USAGE
REASON: The Unit name specified on this DD statement is used
improperly. The DD statement requires a 'xxxx'
(TEMP/WORK) unit name.
OPTIONS: VERIFY-UNIT
RECOVERY: Correct the Unit name in the JCL.
JED20398F RECFM=VB BLKSIZE MUST BE 4 BYTES > LRECL
REASON: When RECFM=VB, BLKSIZE must be at least 4 bytes
greater than the LRECL value.
OPTIONS: VERIFY-BLKSIZE
RECOVERY: Correct BLKSIZE value.
JED20399F XXXXXXXX IS AN INVALID FCB NAME
REASON: The DD SYSOUT statement references an FCB name that
is not defined in the JED Form/FCB table.
OPTIONS: VERIFY-FCB
RECOVERY: Correct the FCB name in the JCL or have the FCB name
added to the JED Form/FCB table.
JED20401F PROC STATEMENT MISSING OR INVALID
REASON: Class=PROC was specified but the Proc statement not
found before first EXEC or first DD statement.
OPTIONS: (none)
RECOVERY: Insert PROC statement or change class to 'JOB'.
JED20402W DUPLICATE SYMBOLIC = xxxxxxxx
REASON: Procedure symbolic 'xxxxxxxx' was duplicated in the
PROC or EXEC statement.
OPTIONS: (none)
RECOVERY: Correct PROC or EXEC statement.
JED20403F IN-STREAM PROCEDURES NOT PERMITTED
REASON: An in-stream procedure was encountered. These are
not permitted in production JCL at your site.
OPTIONS: INHIBIT-PROCS
RECOVERY: Remove the in-stream procedure from the Job and add
it to a PROC library.
JED20404F MEMBER NAME MUST MATCH PROCNAME
REASON: Name on PROC statement did not match member name.
OPTIONS: VERIFY-MEMBER
RECOVERY: Correct PROC statement.
JED20405E SECURED TAPE DSN=XXXXXXXXXXXXX
REASON: The indicated tape dataset is read-protected by your
security system. JED cannot inspect the TMS to
determine if the tape volser exists.
OPTIONS: VERIFY-TAPE
RECOVERY: Modify security system to grant read-access to the
JED job or user.
JED20406W FETCH-PROTECTED PDS DSN=XXXXXXXXXXXXX
REASON: The indicated dataset is fetch-protected by your security
system. The job is able to read the library but JED cannot
inspect it to determine if the member/program exists.
OPTIONS: VERIFY-PDS, VERIFY-PGM
RECOVERY: Modify security system to grant read-access to the
JED job.
JED20505F INVALID OUTPUT DESTID
REASON: The indicated OUTPUT statement specifies a DEST
value that is not defined in the DEST table.
OPTIONS: VERIFY-DEST
RECOVERY: Correct DEST parameter on OUTPUT statement or add
destination to DEST table.
JED20506E DATASET IS MIGRATED
REASON: The indicated dataset is currently in a 'migrated' status,
which will cause a job delay while recalling file.
OPTIONS: ONLINE-FUNCTION=SUBMIT
RECOVERY: Recall dataset manually before submitting JCL.
JED20507E VOLUME NOT MOUNTED = vvvvvv
REASON: The indicated dataset is cataloged to or referencing
a volume that is not currently mounted.
OPTIONS: ONLINE-FUNCTION=SUBMIT
RECOVERY: Correct DSNAME or VOLSER or mount volume.
JED20508F DATASET NOT ON VOLUME = vvvvvv
REASON: The format-1 DSCB is not found for the indicated dataset
on the specified or cataloged volume.
OPTIONS: VERIFY-VOLUME
RECOVERY: Correct DSNAME or VOLSER or uncatalog dataset.
JED20601F IN-STREAM IDCAMS DEFINE NOT PERMITTED
REASON: An IDCAMS Define command was encountered as
in-stream SYSIN data. This is not permitted in
production JCL at your site.
OPTIONS: INHIBIT-DEFINES
RECOVERY: Remove the in-stream Define command to a separate
member and add to CCS as a Define member. Change
the JCL to reference the Define command as a PDS
member.
JED20602F IN-STREAM DATA INVALID WITHIN PROC
REASON: In-stream data was encountered within a JCL
Procedure. MVS does not permit this.
OPTIONS: (none)
RECOVERY: Move the in-stream data to a 'Parmlib' PDS member.
Change the JCL to reference the data as a PDS
member.
JED20603F CA-7 CONTROL PLACEMENT ERROR
REASON: JED does not permit the use of CA-7 control
statements (such as #JI or #JO) when these
statements interrupt or are present between
continued JCL records. For example:
//SYSUT1 DD DISP=OLD,
#JI,SCHED=01
// DSN=FILE01.GDG(0)
#JI,SCHED=02
// DSN=FILE01.GDG
#JEND
OPTIONS: (none)
RECOVERY: Code the CA-7 control statement around complete JCL
statements. For example:
#JI,SCHED=01
//SYSUT1 DD DISP=OLD,
// DSN=FILE01.GDG(0)
#JI,SCHED=02
//SYSUT1 DD DISP=OLD,
// DSN=FILE01.GDG
#JEND
JED20604F IDCAMS DD STATEMENT MISSING
REASON: The SYSIN data for IDCAMS references a DD statement
that is not present in the jobstep JCL.
OPTIONS: VERIFY-IDCAMS
RECOVERY: Correct the IDCAMS command or add the DD statement
to the jobstep.
JED20605W IDCAMS INFILE(DDNAME) REFERS TO OUTPUT DD
REASON: The SYSIN data for IDCAMS references a DD statement
in a manner that is inconsistent with the coded JCL.
For example, INFILE(XXXXXXXX) is coded but the DD
for XXXXXXXX specifies DISP=NEW.
OPTIONS: VERIFY-IDCAMS
RECOVERY: Correct the IDCAMS command or correct the JCL DD
statement.
JED20606W IDCAMS OUTFILE(DDNAME) REFERS TO INPUT DD
REASON: The SYSIN data for IDCAMS references a DD statement
in a manner that is inconsistent with the coded JCL.
For example, OUTFILE(XXXXXXXX) is coded but the DD
for XXXXXXXX specifies DISP=OLD.
OPTIONS: VERIFY-IDCAMS
RECOVERY: Correct the IDCAMS command or correct the JCL DD
statement.
JED20608I IDCAMS DD STATEMENT NOT USED
REASON: The SYSIN data for IDCAMS does not reference this DD
statement --- possible user error.
OPTIONS: VERIFY-IDCAMS
RECOVERY: Correct the IDCAMS command or delete the JCL DD
statement.
JED20609F MULTIPLE DEFINES NOT PERMITTED IN IDCAMS STEP
REASON: The SYSIN data for IDCAMS contains more than one
DEFINE statement. This violates JCL standards at
your site.
OPTIONS: INHIBIT-MULTDEFS
RECOVERY: Separate the DEFINE statements into multiple steps.
JED20610W IMPROPER PLACEMENT OF INSTREAM DATA
REASON: One or more non-JCL statements were detected in the
current step, but these were not preceded by a DD *
or DD DATA statement.
OPTIONS: INHIBIT-INSERTS
RECOVERY: Add DD statement or remove extraneous non-JCL
statements.
JED20611W IDCAMS WORK FILE REFERS TO QUEUE DD
REASON: An IDCAMS work file references a DD statement using
SYSOUT on instream data.
OPTIONS: VERIFY-IDCAMS
RECOVERY: Correct the IDCAMS command or correct the JCL DD
statement.
JED20612W IDCAMS OUTFILE(DDNAME) REFERS TO GDG BASE
REASON: The SYSIN data for IDCAMS references a DD statement
in a manner that is inconsistent with the coded JCL.
For example, OUTFILE(XXXXXXXX) is coded but the DD
for XXXXXXXX specifies an unqualified GDG base.
OPTIONS: VERIFY-IDCAMS
RECOVERY: Correct the IDCAMS command or correct the JCL DD
statement.
JED20613W SYSTSIN DATA SYNTAX ERROR DETECTED
REASON: The SYSTSIN data for IKJEFT01 was found to be in
error. The detected error is presented on REPORT04.
OPTIONS: VERIFY-PROGRAM
RECOVERY: Correct the IKJEFT01 input file.
JED20614W SYSTSIN DATA INDICATES NON-DB2 USAGE
REASON: The SYSTSIN data for IKJEFT01 is normally used for
the batch invocation of a DB2 program. JED has not
found the command sequence for this type of
operation.
OPTIONS: VERIFY-PROGRAM
RECOVERY: Verify the IKJEFT01 input file. If input correct,
use instream '//*JED MSG=JED20614X' to suppress
message or contact DCMS for assistance.
JED20615W VOLUME NOT DEFINED TO TAPE-MGMT - EXPDT=98000 REQD
REASON: The dataset volser is not defined to the tape management
system. LABEL=EXPDT=98000 is required to reference an
outside tape.
OPTIONS: VERIFY-TAPE
RECOVERY: Correct tape volser or add LABEL=EXPDT=98000 to DD statement.
JED20616W DSNAME/VOLUME DOES NOT MATCH TAPE-MGMT
REASON: The tape management system indicates that the dataset
volume does not contain the specified dataset.
OPTIONS: VERIFY-TAPE
RECOVERY: Resolve out-of-synch issues with TMS.
JED20617W TAPE VOLUME IS OFFSITE
REASON: The tape management system indicates that the dataset
volume is not on the premises. Volume may be vaulted.
OPTIONS: VERIFY-TAPE
RECOVERY: Recall volume from tape vault location.
JED20618W LABEL TYPE DOES NOT MATCH TAPE-MGMT
REASON: The tape management system indicates that the dataset's
label type (SL, NL, etc.) does not match JCL value.
OPTIONS: VERIFY-TAPE
RECOVERY: Correct or omit JCL LABEL parameter.
JED20619W VOLUME SEQUENCE MISMATCH
REASON: The tape management system indicates that the dataset's
position on the tape does not match JCL value.
OPTIONS: VERIFY-TAPE
RECOVERY: Correct or omit JCL LABEL parameter.
JED20800F INVALID xxxxxxxx DESTID
REASON: The indicated JES2/JES3 statement specifies a DEST value
that is not defined in the DEST table.
OPTIONS: VERIFY-DEST
RECOVERY: Correct DEST parameter on JES2/JES3 statement or add
destination to DEST table.
JED20801F NON-NUMERIC VALUE FOR XXXXXXXX
REASON: Where a numeric value was expected for JCL keyword
'xxxxxxxx a non-numeric value was found.
OPTIONS: (none)
RECOVERY: Correct JCL value.
JED30103I JOBNAME WILL BE CHANGED TO MEMBER NAME
REASON: Name on JOB statement did not match member name.
OPTIONS: VERIFY-JOBNAME
RECOVERY: (none)
JED30105I MSGCLASS WILL BE CHANGED TO DEFAULT
REASON: Msgclass on JOB statement was non-standard and changed.
OPTIONS: DEFAULT-MSGCLASS
RECOVERY: (none)
JED30106I MSGCLASS KEYWORD WILL BE ADDED TO JOB STATEMENT
REASON: Msgclass keyword missing from JOB statement, was
added.
OPTIONS: DEFAULT-MSGCLASS
RECOVERY: (none)
JED30108I JOB CLASS WILL BE CHANGED TO DEFAULT
REASON: Class on JOB statement was non-standard and changed.
OPTIONS: DEFAULT-JOBCLASS
RECOVERY: (none)
JED30109I CLASS KEYWORD WILL BE ADDED TO JOB STATEMENT
REASON: Class keyword missing from JOB statement, was added.
OPTIONS: DEFAULT-JOBCLASS
RECOVERY: (none)
JED30110I ACCOUNT WILL BE SHIFTED TO PGMRNAME
REASON: JOB Account field exists when should be blank,
Pgmrname blank so Account field is now Pgmrname
field.
OPTIONS: REMOVE-JOBACCOUNT
RECOVERY: (none)
JED30111I XXXXXXXXXXXX KEYWORD WILL BE REMOVED FROM JOB STATEMENT
REASON: Listed field coded on JOB statement is not permitted
at your site so it was removed.
OPTIONS: REMOVE-JOBXXXXXXXX
RECOVERY: (none)
JED30112I JOB ACCOUNTING WILL BE CHANGED
REASON: Account field changed on JOB statement to standard
value.
OPTIONS: VERIFY-ACCOUNT
RECOVERY: (none)
JED30113I JOB ACCOUNTING WILL BE ADDED
REASON: Account field added on JOB statement to standard
value.
OPTIONS: VERIFY-ACCOUNT
RECOVERY: (none)
JED30114I JOB PGMRNAME WILL BE EXPANDED TO MAXIMUM LENGTH
REASON: Pgmrname field on JOB statement expanded to 20
characters.
OPTIONS: OPTIMIZE-PGMRNAME
RECOVERY: (none)
JED30201F STEPNAME NOT UNIQUE
REASON: Renumber option requires unique stepname.
OPTIONS: RENUMBER
RECOVERY: Find and correct duplicate stepname within JOB.
JED30202F MAXIMUM STEPS EXCEEDED
REASON: The maximum number of steps has been exceeded using
the defined renumbering options.
OPTIONS: RENUMBER
RECOVERY: Split member into multiple jobs or change the
Renumber options.
JED30203I STEPS WILL BE RENUMBERED
REASON: An out-of-sequence condition occurred on the current
step number and step renumbering has begun.
OPTIONS: RENUMBER
RECOVERY: (none)
JED30205I DCMS/RDS CANNOT BE REMOVED
REASON: The EXEC Parm field cannot be parsed to remove the
call to DCMS/RDS program GSRD0010.
OPTIONS: REMOVE-RDS
RECOVERY: Remove use of GSRD0010 manually.
JED30206I DCMS/RDS GSRD0010 WILL BE REMOVED - OBSOLETE
REASON: The EXEC statement has been modified to remove the
call to DCMS/RDS program GSRD0010, which is now
obsolete.
OPTIONS: REMOVE-RDS
RECOVERY: (none)
JED30207I IDCAMS WILL BE CHANGED TO GSIDCAMS
REASON: The step executed program IDCAMS. This was change
to GSIDCAMS --- a DCMS utility which calls IDCAMS
then abends when a higher-than-expected return code
is received.
OPTIONS: IMPLEMENT-GSIDCAMS
RECOVERY: (none)
JED30208I CA-11/ARTS WILL BE IMPLEMENTED AS 1ST STEP
REASON: The first step of the Job was not using UCC11RMS.
JCL changed to use it.
OPTIONS: IMPLEMENT-ARTS
RECOVERY: (none)
JED30216I REGION KEYWORD WILL BE REMOVED FROM EXEC STATEMENT
REASON: A Region keyword is specified on a Job EXEC
statement with a value than is smaller than the
default region size. The keyword has been removed.
OPTIONS: REMOVE-EXECREGION
RECOVERY: (none)
JED30220I PROC KEYWORD WILL BE ADDED TO EXEC STATEMENT FOR CLARITY
REASON: This step executes a procedure, but the optional
PROC= keyword was missing. It was added to promote
readability.
OPTIONS: OPTIMIZE-PROC
RECOVERY: (none)
JED30221I TMSX050 STEP WILL BE CONVERTED TO USE CICSCEMT
REASON: This step executes the TMSX050 PROC to open or close
CICS files. The step was converted to use McKinney
CICSCEMT.
OPTIONS: IMPLEMENT-CICSCEMT
RECOVERY: (none)
JED30222I SMART-RESTART WILL BE IMPLEMENTED
REASON: The program and parm values were updated in this
step to use Smart-Restart.
OPTIONS: IMPLEMENT-SMART
RECOVERY: (none)
JED30223I SMART-RESTART COULD NOT BE IMPLEMENTED
REASON: The JCL could not be modified to implement
Smart-Restart.
OPTIONS: IMPLEMENT-SMART
RECOVERY: (none)
JED30300I EXPDT KEYWORD WILL BE REMOVED
REASON: The EXPDT keyword has been removed from this DD
statement due to standards enforcement. If EXPDT is
the only sub-keyword of DCB, the DCB keyword has
been removed as well.
OPTIONS: REMOVE-EXPDT
RECOVERY: (none)
JED30302I KEYWORD DSNAME WILL BE CHANGED TO DSN
REASON: The indicated DD statement used 'DSNAME' keyword.
This was changed to 'DSN' for consistancy.
OPTIONS: (none)
RECOVERY: (none)
JED30303I KEYWORD VOLUME WILL BE CHANGED TO VOL
REASON: The indicated DD statement used 'VOLUME' keyword.
This was changed to 'VOL' for consistancy.
OPTIONS: (none)
RECOVERY: (none)
JED30304I KEYWORD SHARE WILL BE CHANGED TO SHR
REASON: The indicated DD statement used 'SHARE' keyword.
This was changed to 'SHR' for consistancy.
OPTIONS: (none)
RECOVERY: (none)
JED30306I TEMPORARY DATASET WILL BE CATALOGED
REASON: The indicated dataset is considered temporary --- it
is created and deleted within this Job. The
disposition was changed to catalog this dataset.
The dataset will be delete at the Job's last step.
OPTIONS: CATLG-TEMPS
RECOVERY: (none)
JED30307I DSN= AND DISP= KEYWORDS WILL BE REMOVED FOR WORK DATASET
REASON: The indicated dataset is considered a work file ---
it is created and deleted within this step. For
clarity, the DSN and DISP keywords have been removed
to permit system defaults.
OPTIONS: CATLG-TEMPS
RECOVERY: (none)
JED30308I TEMPORARY DATASET WILL BE KEPT
REASON: The indicated dataset is considered temporary --- it
is created and deleted within this Job. The
disposition was changed to retain this dataset until
the job's last step.
OPTIONS: CATLG-TEMPS
RECOVERY: (none)
JED30309I TEMPORARY DATASET WILL BE KEPT UPON ABEND
REASON: The indicated dataset is considered temporary --- it
is created and deleted within this Job. The
disposition was changed to retain this dataset until
the Job's last step --- even if the step abends.
OPTIONS: CATLG-TEMPS
RECOVERY: (none)
JED30310I VIOPLUS WILL BE IMPLEMENTED
REASON: One or more VSAM datasets were encountered in this
step. Since VIOCTL statements were not encountered,
a VIOCTL ACTIVATE DD statement has been added to
implement the use of VIOPLUS.
OPTIONS: IMPLEMENT-VIOPLUS
RECOVERY: (none)
JED30311I JOBCAT STATEMENT WILL BE DELETED
REASON: A JOBCAT DD statement has been found and removed
from the JCL. These are not permitted in production
JCL at your site
OPTIONS: REMOVE-JOBCAT
RECOVERY: (none)
JED30312I STEPCAT STATEMENT WILL BE DELETED
REASON: A STEPCAT DD statement has been found and removed
from the JCL. These are not permitted in production
JCL at your site
OPTIONS: REMOVE-STEPCAT
RECOVERY: (none)
JED30313I PROCLIB STATEMENT(S) WILL BE DELETED
REASON: A PROCLIB DD statement has been found and removed
from the JCL. These are not permitted in production
JCL at your site
OPTIONS: REMOVE-PROCLIB
RECOVERY: (none)
JED30314I DUPLICATE DD WILL BE DELETED
REASON: A DD statement with a duplicate DDname has been
encountered. The entire secondary DD statement has
been removed from the JCL.
OPTIONS: REMOVE-DUPDDS
RECOVERY: Insure that the duplicated DD in not required.
JED30315I JOBLIB(S) WILL BE CHANGED
REASON: The JOBLIB DD statement concatenation has be
modified to meet standards for production JCL at
your site.
OPTIONS: ENFORCE-JOBLIB
RECOVERY: (none)
JED30316I STEPLIB STATEMENT(S) WILL BE DELETED
REASON: The indicated STEPLIB DD statement has been deleted
to meet standards for production JCL at your site.
OPTIONS: ENFORCE-JOBLIB
RECOVERY: (none)
JED30317I VIOCTL STATEMENT WILL BE DELETED - NOT USED
REASON: VSAM files are not in use in this step. The VIOCTL
statement has been deleted because it is not needed.
OPTIONS: IMPLEMENT-VIOPLUS
RECOVERY: (none)
JED30318I DISP=SHR WILL BE FIXED
REASON: Disp=(Shr) or Disp=(Shr,Keep) or Disp=(Shr,Pass) was
coded on this DD statement. It has been changed to
Disp=Shr for clarity and conformity.
OPTIONS: OPTIMIZE-DISP
RECOVERY: (none)
JED30319I DISP PARAMETERS WILL BE EXPANDED TO SHOW DEFAULTS
REASON: The Disp values on this DD statement have been
expanded to show all system defaults for clarity and
conformity.
OPTIONS: OPTIMIZE-DISP
RECOVERY: (none)
JED30322I OUTPUT CLASS WILL BE CHANGED TO DEFAULT
REASON: The DD SYSOUT statement references a class that is
invalid. It has been changed to the default class.
OPTIONS: DEFAULT-OUTCLASS
RECOVERY: Correct the SYSOUT class in the JCL or add the class
to the 'Verify Outclass' list.
JED30323I DEFAULT FORM NAME WILL BE ADDED
REASON: The DD SYSOUT statement did not specify a form name.
The default form name has been added to the SYSOUT
DD statement.
OPTIONS: DEFAULT-FORM
RECOVERY: (none)
JED30324I DEFAULT FCB WILL BE ADDED
REASON: The DD SYSOUT statement did not specify an FCB name.
The default FCB name has been added to the SYSOUT DD
statement.
OPTIONS: DEFAULT-FCB
RECOVERY: (none)
JED30325I VOL=SER KEYWORD WILL BE REMOVED
REASON: The DD specifies a SER keyword. This keyword has
been removed to enforce the use of the OS catalog.
OPTIONS: IMPLEMENT-CATALOG
RECOVERY: (none)
JED30326I UNIT NAME WILL BE REMOVED
REASON: The DD specifies a UNIT keyword when referencing an
existing dataset. This keyword has been removed to
enforce the use on the OS catalog.
OPTIONS: IMPLEMENT-CATALOG
RECOVERY: (none)
JED30327I UNIT KEYWORD WILL BE REMOVED
REASON: The DD specifies a UNIT name with a UNIT keyword
when referencing an existing dataset. This UNIT
name has been removed to enforce the use of the OS
catalog.
OPTIONS: IMPLEMENT-CATALOG
RECOVERY: (none)
JED30328I NEW DATASET WILL BE CATALOGED
REASON: The DD specifies Disp=(New,Keep) for a new dataset.
The Disp keyword has been changed to catalog the
dataset to enforce the use of the OS catalog.
OPTIONS: IMPLEMENT-CATALOG
RECOVERY: (none)
JED30329I CONTIG SPACE OPTION WILL BE REMOVED
REASON: The Contig option has been removed from the Space
parameters for this DD statement due to standards at
your site.
OPTIONS: OPTIMIZE-CONTIG
RECOVERY: (none)
JED30331W UNIT NAME WILL BE CHANGED TO DEFAULT
REASON: The Unit name specified on this DD statement does
not exist in a list of valid unit names. It has
been changed to the default for your site.
OPTIONS: DEFAULT-UNIT
RECOVERY: Verify that the unit name is correct.
JED30333I SECONDARY SPACE WILL BE ADDED
REASON: The new dataset specified on this DD statement does
not allocate secondary space. A secondary Space
allocation of 10% of the primary has been added.
OPTIONS: OPTIMIZE-SPACE
RECOVERY: (none)
JED30334I SPACE OPTION RLSE WILL BE ADDED
REASON: The new dataset specified on this DD statement does
not utilize the Release option in the Space
parameters. The RLSE option has been added.
OPTIONS: OPTIMIZE-RLSE
RECOVERY: (none)
JED30335W SPACE OPTION RLSE MISSING
REASON: The new dataset specified on this DD statement does
not utilize the Release option in the Space
parameters.
OPTIONS: VERIFY-RLSE
RECOVERY: Add a Rlse option if possible.
JED30339F NOT TEMPORARY DSN=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
REASON: The Dataset referenced by this DD statement is NOT a
temporary dataset and must not use the naming
standard for such because it is not both created and
deleted in this Job.
OPTIONS: CATLG-TEMPS
RECOVERY: Correct the dataset name or delete the dataset using
a Disp=(Old,Delete) in the JCL.
JED30347I QUOTES ENCLOSING DSNAME WILL BE REMOVED
REASON: The Dataset name referenced by this DD statement is
enclosed in quotation marks needlessly. The
enclosing quotations are removed for clarity.
OPTIONS: (none)
RECOVERY: (none)
JED30349I JOBLIB(S) WILL BE INSERTED
REASON: No JOBLIB DD statement concatenation was
encountered. These were inserted to meet standards
for production JCL at your site.
OPTIONS: ENFORCE-JOBLIB
RECOVERY: (none)
JED30352I UNUSED DD STATEMENT WILL BE DELETED
REASON: This DD statement is not used by the executed
program and has been deleted from the JCL.
OPTIONS: REMOVE-UNUSED
RECOVERY: (none)
JED30357I OUTPUT KEYWORD VALUE WILL BE CORRECTED
REASON: An OUTPUT keyword value on this DD statement has
been corrected to remove a duplicate OUTPUT
statement.
OPTIONS: IMPLEMENT-RAS
RECOVERY: (none)
JED30358I DCMS/RAS WILL BE IMPLEMENTED
REASON: The OUTPUT keyword was added to this DD statement in
order to produce one copy of the report for DCMS
Report Archival System. The original copies and
destination are produced via backward reference to
an OUTPUT statement.
OPTIONS: IMPLEMENT-RAS
RECOVERY: (none)
JED30359I MODEL DCB WILL BE ADDED FOR NEW GENERATION
REASON: The Dataset referenced by this DD statement is a
Generation Data Group (GDG) and a new generation is
being created. MVS requires that new GDG
generations be created with a model DCB dataset name
and this information is not present. Your site's
default value has been added.
OPTIONS: DEFAULT-MDLDCB
RECOVERY: (none)
JED30360I UNIT COUNT WILL BE ADDED
REASON: The unit-count parameter has been added to the UNIT
keyword on this DD statement. This has been done to
permit the dataset to be extended onto multiple
volumes.
OPTIONS: TABLE-UNIT-COUNT
RECOVERY: (none)
JED30361I UNIT COUNT WILL BE CHANGED
REASON: The unit-count parameter for the UNIT keyword has
been changed to the installation-supplied value on
this DD statement.
OPTIONS: TABLE-UNIT-COUNT
RECOVERY: (none)
JED30362I DCB KEYWORD WILL BE REMOVED
REASON: The DCB keyword is not required on this DD
statement. It has been removed for the sake of
clarity.
OPTIONS: REMOVE-DCB
RECOVERY: (none)
JED30363I BLKSIZE WILL BE OPTIMIZED
REASON: The BLKSIZE keyword has be changed to an optimum
value.
OPTIONS: OPTIMIZE-BLKSIZE
RECOVERY: (none)
JED30365I OUTPUT CLASS SAME AS MSGCLASS, WILL BE CHANGED TO *
REASON: The DD SYSOUT statement specifies the same class as
the current MSGCLASS. Changed to '*' for clarity.
OPTIONS: VERIFY-OUTCLASS
RECOVERY: None.
JED30366I DUMP CLASS WILL BE CHANGED TO DEFAULT
REASON: The DD SYSOUT statement references a class that is
invalid for DDNAME SYSUDUMP, SYSABEND or SYSDBOUT.
It has been changed to the default class.
OPTIONS: DEFAULT-DMPCLASS
RECOVERY: Correct the SYSOUT class in the JCL or add the class
to the 'Verify Dmpclass' list.
JED30373I SECONDARY SPACE WILL BE INCREASED TO 10% PRIMARY
REASON: The dataset specified on this DD statement specifies
a secondary space amount which is less than 10% of
the primary The secondary Space allocation has been
increased to 10% of the primary.
OPTIONS: OPTIMIZE-SPACE
RECOVERY: (none)
JED30374I AMP WILL BE REMOVED - VIOPLUS ACTIVE
REASON: The AMP parameter on this DD statement has been
removed because VIOPLUS is used in this step. The
AMP parameter conflict with the function of VIOPLUS.
OPTIONS: IMPLEMENT-VIOPLUS
RECOVERY: (none)
JED30376I TEMPORARY DATASET DSN WILL BE CORRECTED
REASON: The indicated dataset is considered temporary --- it
is created and deleted within this Job. The dataset
name was modified to production standards.
OPTIONS: CATLG-TEMPS
RECOVERY: (none)
JED30377I SPACE BLKSIZE WILL BE CHANGED TO MATCH DCB BLKSIZE
REASON: The SPACE has been changed to match the DCB BLKSIZE
value. The primary and secondary amounts have been
adjusted to yield the same allocation.
OPTIONS: OPTIMIZE-BLKSIZE
RECOVERY: (none)
JED30402I PROCEDURE NAME WILL BE CHANGED TO MEMBER NAME
REASON: Name on PROC statement did not match member name.
OPTIONS: (none)
RECOVERY: (none)
JED30501I OUTPUT JCL STATEMENT WILL BE REMOVED - NOT USED
REASON: The indicated OUTPUT statement is not referenced in the job
and was removed.
OPTIONS: IMPLEMENT-RAS
RECOVERY: (none)
JED30502I OUTPUT JCL STATEMENT WILL BE REMOVED - DUPLICATE
REASON: The indicated OUTPUT statement was identical to a
previous OUTPUT statement. All references to this
OUTPUT are changed to use the previous one. This
OUTPUT statement has been deleted because it is no
longer in use.
OPTIONS: IMPLEMENT-RAS
RECOVERY: (none)
JED30503I OUTPUT JCL STATEMENT WILL BE INSERTED FOR DCMS/RAS
REASON: The indicated OUTPUT statement was inserted prior to
the first EXEC in order that DCMS/RAS can be
implemented in one or more jobsteps.
OPTIONS: IMPLEMENT-RAS
RECOVERY: (none)
JED30504I JOBPARM PROCLIB KEYWORD WILL BE REMOVED
REASON: A JOBPARM statement was encountered utilizing a
Proclib keyword. The Proclib keyword was removed.
If Proclib was the only keyword on the JOBPARM
statement, the JOBPARM statement was deleted from
the JCL. These are not permitted in production JCL
at your site.
OPTIONS: REMOVE-PROCLIB
RECOVERY: (none)
JED40001F PROCLIB TABLE ERROR
REASON: An error occurred while attempting to dynamically
allocate the contents of the PROCLIB table. This is
normally accompanied by a console message from GSJE0016.
OPTIONS: SYNTAX
RECOVERY: Correct PROCLIB table and retry.
JED40002F RC=xx RETURNED FROM JES2INFO ROUTINE
REASON: An error occurred while attempting to dynamically determine
the JES2 PROCLIB/JOBCLASS data. IMPLEMENT- DYNPROC is
disabled.
OPTIONS: IMPLEMENT-DYNPROC
RECOVERY: Contact DCMS Technical Support.
JED40003F TABLE-PROCLIB/PROCLIB-DD MISSING
REASON: There are no TABLE-PROCLIB entries and the PROCLIB DD
statement is missing. The SYNTAX option requires at least
one procedure library.
OPTIONS: SYNTAX
RECOVERY: Add PROCLIB DD or correct PROCLIB table and retry.
JED40601W INVALID KEYWORD = xxxxxxxxxx
REASON: An unrecognized option keyword was entered.
OPTIONS: (any)
RECOVERY: Correct OPTION file and retry.
JED40602W FORMAT xxxx yyyy=vvvv OUT OF RANGE
REASON: The value 'vvvv' specified for formatting option 'yyyy',
statement type 'xxxx' is not within a valid numeric range.
OPTIONS: (any)
RECOVERY: Correct OPTION file FORMAT option and retry.
JED40603W FORMAT xxxx yyyy=vvvv INVALID
REASON: The value 'vvvv' specified for formatting option
'yyyy', statement type 'xxxx' is not valid.
OPTIONS: (any)
RECOVERY: Correct OPTION file FORMAT option and retry.
JED40604W DEFAULT YES ASSUMED
REASON:
OPTIONS: (any)
RECOVERY: Correct OPTION file and retry.
JED40605W INVALID YES/NO VALUE RESET TO NO
REASON: An option requiring a yes or no value was specified incorrectly
The option value has been set to 'NO'.
OPTIONS: (any)
RECOVERY: Correct OPTION file and retry.
JED40606W INVALID xxxx OPTION=yyyy
REASON: The value 'yyyy' specified for 'xxxx' is not valid
OPTIONS: (any)
RECOVERY: Correct OPTION file and retry.
JED40607E SERVLU=xxxxxxxx NOT DEFINED IN INSTALL OPTIONS
REASON: The specified JEDSERV logical unit is not defined within
the installation options (GSJETOPT).
OPTIONS: IMPLEMENT-JEDSERV
RECOVERY: Correct the installation options or remove JEDSERV option.
JED40631W DD=xxxxxxxx DYNAMIC DE-ALLOCATION FAILED
REASON: During shutdown a dynamically allocated dataset
could not be freed. This is probably an internal
error.
OPTIONS: (any)
RECOVERY: Contact DCMS.
JED40632F PROFILE DATASET MISSING
REASON: The defined profile dataset is no longer cataloged.
The profile dataset is defined to the JED001 entry
in the JED dataset name table (GSJE0DSN) load
module.
OPTIONS: (any)
RECOVERY: Restore the profile dataset and retry.
JED40633W WORK SPACE NOT ALLOCATED
REASON: Dynamic allocation failed obtaining a work file to
be used by the Control-M interface. JED will
continue with IMPLEMENT-CONTROLM=NO.
OPTIONS: IMPLEMENT-CONTROLM
RECOVERY: Correct JEDUNIT options and retry.
JED40634W DD=xxxxxxxx NOT FOUND IN DSN TABLE
REASON: JED was unable to dynamically allocate a CCS-owned
file because the file is not defined in GSCC0DSN.
JED will continue without the use of the file.
OPTIONS: IMPLEMENT-CCS
RECOVERY: Validate JED options and CCS dataset name table.
JED40635W DD=xxxxxxxx DYNAMIC ALLOCATION FAILED
REASON: JED was unable to dynamically allocate a CCS-owned
file. The file could be exclusively use by another
task or it is no longer cataloged.
OPTIONS: IMPLEMENT-CCS
RECOVERY: Validate CCS dataset name table.
JED40636W DD=xxxxxxxx MISSING - AFFECTING OPTION=xxx...
REASON: JED was unable to find file 'xxxxxxxx' in the
execution JCL. JED will continue without the
option.
OPTIONS: SPECIFIED IN MESSAGE.
RECOVERY: Correct execution JCL.
JED40637W DD=xxxxxxxx ALREADY SPECIFIED, DUPLICATE
REASON: One or more DDNAME option has the same value. Each
DDNAME value must be unique.
OPTIONS: DDNAME
RECOVERY: Correct DDNAME option.
JED40638W DD=xxxxxxxx FOUND - AFFECTING OPTION=xxx...
REASON: JED found 'xxxxxxxx' already present in the execution
JCL. JED will continue without the option.
OPTIONS: SPECIFIED IN MESSAGE.
RECOVERY: Correct execution JCL.
JED40639W DD=xxxxxxxx DYNAMIC ALLOCATION FAILED
REASON: JED was unable to dynamically allocate a CONTROL-M
dataset defined to JED.
OPTIONS: IMPLEMENT-CONTROLM
RECOVERY: Validate JED dataset name table.
JED40641W INVALID TABLE OPTION = xxxx
REASON: The value 'xxxx' specified a table not valid
OPTIONS: (any)
RECOVERY: Correct OPTION file and retry.
JED40700W xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
REASON: The JED Options Processsor detected an error in the
current Options file, Option Profile, Execution
Parm or //*JED statement.
OPTIONS: (any)
RECOVERY: Correct the JED option.
JED40701F PROFILE MEMBER xxxxxxxx IS OLD FORMAT, RELOAD
REASON: The requested profile was created by a different release
of JED.
OPTIONS: (any)
RECOVERY: Use ADMIN option 6 to reload to new format.
JED40702F PROFILE MEMBER NOT FOUND = xxxxxxxx
REASON: The requested profile is not stored on the profile dataset.
OPTIONS: (any)
RECOVERY: Correct the profile name in the execution PARM.
JED51000I UNSUPPORTED JCL KEYWORD=xxxxxxxx
REASON: JCL keyword 'xxxxxxxx' is not recognized by JED. It
may or may not be invalid.
OPTIONS: SYNTAX
RECOVERY: Correct JCL error or contact DCMS for support.
JED52nnnW INVALID VALUE=xxxxxxxx FOR KEYWORD=yyyyyyyy (POSITION #z)
REASON: Value 'xxxxxxxx' is not acceptable for JCL keyword
'yyyyyyyy', sub-parameter number 'z'. The 'nnn' in
the message ID is the unique rule identifier.
The POSITION value is not included when the sub-parameter
number is one.
OPTIONS: SYNTAX
RECOVERY: Correct JCL error.
JED53nnnF REQUIRED VALUE MISSING FOR KEYWORD=yyyyyyyy (POSITION #z)
REASON: A value is required for JCL keyword 'yyyyyyyy',
sub-parameter 'z' where it is now omitted. The 'nnn' in
the message ID is the unique rule identifier. The
POSITION value is not included when the sub-parameter
number is one.
OPTIONS: SYNTAX
RECOVERY: Correct JCL error.
JED54nnnF INVALID REFERBACK
REASON: A reference in the JCL to a prior DD statement that
does not exist. The 'nnn' in the message ID is the
unique rule identifier.
OPTIONS: SYNTAX
RECOVERY: Correct JCL error.
JED55000F xxxxxxxx yyyy POSITIONAL PARAMETER #z
REASON: The positional JCL parameter number 'z' on the type 'yyyy'
statement is in error. When 'xxxxxxxx' is INVALID, the value
does not follow the rules for the parameter. Either the value
is too long, it contains invalid characters or utilizes the
wrong word. When 'xxxxxxxx' is EXCESS, the positional value
is not recognized for this JCL statement.
OPTIONS: SYNTAX
RECOVERY: Correct JCL error.
JED56000I UNSUPPORTED JCL STATEMENT
REASON: A JCL statement was encounter that is not recognized by
the system.
OPTIONS: SYNTAX
RECOVERY: Correct JCL error or contact DCMS for support.
JED60001F IF STMT SYNTAX ERROR REASON=r
REASON: An IF statement is improperly formatted. A required parameter
is either missing or misspelled. The reason code indicates
the parameter in error:
1 - Operand #1
2 - Comparator
3 - Operand #2
4 - Connector (AND/OR)
5 - THEN missing
OPTIONS: SYNTAX
RECOVERY: Correct JCL error.
JED60002F IF STMT SYNTAX VALUE REASON=r
REASON: An IF statement contains an invalid value. The reason code
indicates the parameter in error:
1 - Operand #1
2 - Comparator
3 - Operand #2
4 - Connector (AND/OR)
OPTIONS: SYNTAX
RECOVERY: Correct JCL error.
JED60003F TABLE-RC STEP DOES NOT EXECUTE PGM
REASON: The stepname on a TABLE-RC entry specifies a step that
executes a procedure, in violation of TABLE-RC rules.
OPTIONS: TABLE-RC
RECOVERY: Correct the erroneous TABLE-RC entry.
JED60004F IF STEPNAME DOES NOT EXECUTE PGM
REASON: The stepname on an IF statement specifies a step that
executes a procedure, in violation of IF statement rules.
OPTIONS: SYNTAX
RECOVERY: Correct JCL error.
JED60005I STATEMENT WITHIN IF/ENDIF IGNORED
REASON: A JCL statement was encountered within an IF/ENDIF construct
that will still be processed by the operating system. The
statement type is not affected by an IF statement.
OPTIONS: SYNTAX
RECOVERY: Correct possible JCL error.
JED60006I EXEC BYPASSED DUE TO IF STATEMENT
REASON: Based on specified or default return codes, the specified
EXEC statement is bypassed for this simulated run due to
a FALSE IF/ELSE/ENDIF test.
OPTIONS: SYNTAX
RECOVERY: (none)
JED60007F NO EXEC WITHIN IF/ENDIF
REASON: Between the IF and ENDIF statements that just terminated,
no EXEC statements were encountered, in violation of IF
statement coding rules.
OPTIONS: SYNTAX
RECOVERY: Correct JCL error.
JED60008I EXEC BYPASSED DUE TO JOB COND
REASON: Based on specified or default return codes, the specified
EXEC statement is bypassed for this simulated run due to
the COND parameter of the JOB statement.
OPTIONS: SYNTAX
RECOVERY: (none)
JED60009I EXEC BYPASSED DUE TO EXEC COND
REASON: Based on specified or default return codes, the specified
EXEC statement is bypassed for this simulated run due to
the COND parameter of the most recent EXEC statement.
OPTIONS: SYNTAX
RECOVERY: (none)
JED60010I EXEC BYPASSED DUE TO PRIOR ABEND
REASON: Based on the specified TABLE-RC abend code, the specified
EXEC statement is bypassed for this simulated run.
OPTIONS: SYNTAX
RECOVERY: (none)
JED60011I EXEC BYPASSED DUE TO RESTART STEP
REASON: Based on the specified VERIFY-JOBSTEP value, the specified
EXEC statement is bypassed for this simulated run.
OPTIONS: SYNTAX
RECOVERY: (none)
JED90291F MESSAGE TABLE FULL
REASON: The message table in GSJE0029 has exceeded the
maximum number of 300 entries for a specific JCL member.
OPTIONS: (none)
RECOVERY: Correct JCL member to reduce errors.
