ASG-PRO/JCL Messages and Codes Guide

ASG-PRO/JCL Messages and Codes GuideVersion: 3.5.0

Publication Date: August 2021

©2021 ASG Technologies Group, Inc. All rights reserved.

The information contained herein is the confidential and proprietary information of ASG Technologies Group, Inc. Unauthorized use of thisinformation and disclosure to third parties is expressly prohibited. This technical publication may not be reproduced in whole or in part, by anymeans, without the express written consent of ASG Technologies Group, Inc.

All names and products contained herein are the trademarks or registered trademarks of their respective holders.

ASG Technologies Worldwide Headquarters Naples Florida USA | asg.com | [email protected]

708 Goodlette Road North, Naples, Florida 34102 USA Tel: 239.435.2200 Fax: 239.263.3692 Toll Free: 800.932.5536 (USA only)

ContentsPreface ii

About this Publication ii

Worldwide Customer Support ii

ASG Customer Care Expert Solution Services Portal (ACCESS) ii

Product Support Policy iii

ASG Documentation/Product Enhancements iii

Messages and Codes 1

System Messages 2

Return Codes 153

Advanced Product Manager Messages 154

Product Identifier Codes 157

i

PrefaceThis documentation describes how to use our main ASG product ASG-PRO/JCL.

About this PublicationThis documentation describes how to use the different modules that form the ASG product ASG-PRO/JCL.

Worldwide Customer SupportASG provides support throughout the world to resolve questions or problems regarding installation, operation, or use ofour products. ASG provides all levels of support during normal business hours and emergency support during non-business hours.

You can access support information from ASG’s Support page.

ASG Third-party Support. ASG provides software products that run in a number of third-party vendor environments.Support for all non-ASG products is the responsibility of the respective vendor. In the event a vendor discontinuessupport for a hardware and/or software product, ASG cannot be held responsible for problems arising from the use ofthat unsupported version.

ASG Customer Care Expert Solution Services Portal (ACCESS)The ACCESS Portal provides online support. Log on to the portal with the following information:

Email ID = NNNNNNNNN

Site Password = XXXXXXXXXX

where:

NNNNNNNNN is your email ID supplied by ASG Product Distribution.

XXXXXXXXXX is your unique site password supplied by ASG Product Distribution.

If you do not have your logon information, contact your local support center. This table outlines the support responsetimes you can expect:

Severity MeaningExpected Support ResponseTime

1 Production down, critical situation Within 30minutes

2 Major component of product disabled Within 2 hours

3 Problem with the product, but customer has work-aroundsolution

Within 4 hours

4 “How-to” questions and enhancement requests Within 4 hours

ii

ASG-PRO/JCLMessages and Codes Guide

Product Support PolicyASG fully supports the current release and one previous release of each of its products. ASGwill temporarily support anolder release, for up to six months, to provide time for you to upgrade.

After programming support for a product release is withdrawn, ASGwill no longer supply new fixes for problems noraccept enhancement requests for that release. When a vendor announces the end of support for system software or ahardware configuration on which ASG products rely, ASGwill make a similar announcement regarding the support plansfor its products. ASG’s support for problems affected by system software release levels will terminate when the vendorno longer supports their hardware or software.

Announcements regarding support plans for various products can be found on ASG’s Web site.

ASG Documentation/Product EnhancementsUse ASG’s contact form to submit your product and documentation suggestions. Ensure that you include the name ofthe ASG product you are using.

iii

Product Support Policy

https://www.asg.com/en/Contact-Us.aspx

Messages and CodesThis documentation provides information about themessages and return codes generated by ASG-PRO/JCL (hereincalled PRO/JCL). PRO/JCL is a JCL asset management tool that reduces syntactic and production errors. It does this bysimulating theMVS run-time environment to validate the syntax of JCL and many other control statement types

This documentation consist of the following topics:

Topic Description

System Messages Explains the PRO/JCL message formats and lists the PRO/JCL messages inalphabetical order by message ID.

Return Codes Lists and explains the PRO/JCL return codes.

Advanced Product ManagerMessages

Lists themessages that you may encounter while attempting to authorize oractivate ASG-PRO/JCL.

Product Identifier Codes Lists the Product Identifier codes.

1

Messages and Codes

System MessagesThis topic explains message formats and all PRO/JCL messages in order by message ID. For explanations of PRO/JCLreturn codes, see Return Codes.

Message Format

This topic contains a complete listing of all PRO/JCL product error messages in order by message number.

Two types of error messages are listed:

l Product execution messages.

l JCL verification messages generated by PRO/JCL as your JCL is scanned.

PRO/JCL messages have this general format:

Number Meaning

DSS Standard prefix for all PRO/JCL messages.

10000 <

PRO/JCL execution messages. Thesemessages describe possible reasons for why the product didnot run. These types ofmessages can appear in the started task (SYSPRINT DD), JPSEL, or SJL.

Messages numbered less than 10000 cannot be viewed and the severity level of thesemessages cannot bemodified.

10000 >

Simulation errors. These are coding errors identified by PRO/JCL and listed in the SJL output.

Messages numbered greater than 10000 can be viewed and the severity of thesemessages can bemodified. For information on Managing Messages in the SJL, see thetopic -Managing Messages in the SJL in the System Administrator documentation .

90000 > User messages. These are special user-defined JCLManipulation Program (JMP)messages. SeeJMP Message Format for more information.

JMP Message FormatPRO/JCL's JCL Manipulation Program (JMP) allows for special user messages to be defined to your site.

Themessage number, severity, and message text can be specified as follows:

Option Description

Msg # Themessage number. This must be in the range 90,000 to 99,999.

Sev A positive number up to 99 indicating the level of severity assigned to the error:

2


Option Description

l 0 - advisory. An A is appended to the error message in the SJL.

l 1 through 4 -Warning. AW is appended to the error message in the SJL.

l 5 through 99 - Error. An E is appended to the error message in the SJL.

TextThis is the first 62 characters of the short text.

To view the entire short text and long text, enter S in the Sel field to select themessage.

These options are available from the Create and Modify User Messages panel. See the ASG-PRO/JCL ReferenceManual for information about creating, editing, and deleting special user messages.

PRO/JCL Messages

PRO/JCL issues two types ofmessage formats:

l Parameterized

l Non-parameterized

Non-parameterized messages contain no replaceable parameters. Parameterized messages contain up to fourreplaceable parameters (&1, &2, &3, and &4). Since these parameters can vary, depending on system or user input, theyhave been left unresolved in the text of the error messages listed.

If you receive an error message that is not listed, contact ASG Customer Support.

l Error Messages from DSS00001 to DSS01000























DSS00002 "Internal error: '&1' detected '&2': RC = '&3'. Please call ASG Technologies Customer Support."

Explanation: This error resulted from inconsistent information internal to the product. It should not bedependent upon external data.

3

System Messages

Action: Call ASG Technologies Customer Support.

DSS00003 "VSAMERROR: &1 &2 &3 &4."

Explanation: VSAM ERROR: &1&2&3&4.

DSS00007 "Internal error: '&1' processor cannot be run. Please call ASG Technologies Customer Support."

Explanation: Internal error: unable to run '&1' processor because the input or output file cannot be opened.


DSS00009 "User processor '&1' returned &2. Processing stopped."

Explanation: The user-defined processor called '&1' issued a return code of &2, which stopped all processing.

DSS00010 "Attempted overwrite of '&1' was blocked. This can occur if you specify the same TODSN for twoFROMDSNs, and the two FROMDSNs contain the samemember name."

Explanation: BIORequest::IOSOpenOutput() detected that the file '&1' is already open for output whenanother request was made to open it for output. This can occur if you specify the same TODSNfor two FROMDSNs, and the two FROMDSNs contain the samemember name.

DSS00011 "Unable to open VSAM file - &1 &2. Please call ASG Technologies Customer Support."

Explanation: Neither the short text nor the long text for this message should ever be issued.

Action: Call ASG Technologies Customer Support for resolution.

DSS00012 "Unable to close VSAM file '&1': RC =&2. Please call ASG Technologies Customer Support."

Explanation: The attempt to close the VSAM file '&1' failed with a return code of &2.

Action: This represents an internal or installation error which should be reported to ASG TechnologiesCustomer Support for resolution.

DSS00013 "Read failure on '&1'. Please call ASG Technologies Customer Support."

Explanation: An attempt to read a record from the file '&1' failed.

Action: This internal error should be reported to ASG Technologies Customer Support for resolution.

DSS00014 "Write failure on '&1' - &2. Please call ASG Technologies Customer Support."

Explanation: An attempt to write a record to the file '&1' failed with themessage '&2'.


DSS00015 "VSAM update failure on '&1'. Please call ASG Technologies Customer Support."

Explanation: An attempt to update the VSAM file '&1' failed.


DSS00016 "VSAM internal error. Incorrect LOCATE option - '&1'. Please call ASG Technologies CustomerSupport."

Explanation: The 'LOCATE' macro was issued with an incorrect option '&1'.


4


DSS00017 "VSAM FLOCATE (&1) failure on &2. Please call ASG Technologies Customer Support."

Explanation: VSAM FLOCATE (&1) failure on &2.


DSS00019 "Access to '&1' denied by security system."

Explanation: Access to '&1' denied by security system.

DSS00020 "ReadFirst record failure &1 - &2. Please call ASG Technologies Customer Support."

Explanation: ReadFirst record failure &1 - &2.


DSS00021 "DJ0YSLVL returned RC=&1. Please call ASG Technologies Customer Support."

Explanation: DJ0YSLVL returned RC=&1.


DSS00022 "VSAM FLOCATE failure on &1. Please call ASG Technologies Customer Support."

Explanation: VSAM FLOCATE failure on &1.

Action: Please call ASG Technologies Customer Support.

DSS00024 "Unable to lock VSAM file '&1'. Please call ASG Technologies Customer Support."

Explanation: Unable to lock VSAM file '&1'.


DSS00025 "Unable to unlock VSAM file '&1'. Please call ASG Technologies Customer Support."

Explanation: Unable to unlock VSAM file '&1'.


DSS00026 "Internal error - VSAM file '&1' not locked prior to write. Please call ASG Technologies CustomerSupport."

Explanation: Internal error - VSAM file '&1' not locked prior to write.


DSS00027 "Unable to replace record; VSAM error - &1. Please call ASG Technologies Customer Support."

Explanation: Unable to replace record; VSAM error - &1.


DSS00028 "Unable to add record; VSAM error - &1. Please call ASG Technologies Customer Support."

Explanation: Unable to add record; VSAM error - &1.


DSS00029 "ctree-tree error - &1. Please call ASG Technologies Customer Support."

Explanation: ctree-tree error - &1.

5

System Messages


DSS00032 "Processing terminated prematurely due to return code &1. Please call ASG Technologies CustomerSupport."

Explanation: Processing terminated prematurely due to return code &1.


DSS00033 "Corrupt record found in PCFILE. Processing will continue; some usage recordsmay be lost. Corruptrecord is '&1'. Expected record #&2; received #&3."

Explanation: Corrupt record found in PCFILE. Processing will continue; some usage records may be lost.Corrupt record is '&1'. Expected record #&2; received #&3.

DSS00034 "Record type &1 is not available from this server."

Explanation: Record type &1 is not available from this server. This is probably due to a mismatch betweenthe client and server or it is an internal error.

DSS00035 "Unable to start process '&2' via '&1': &3, errno=&4."

Explanation: Unable to start process '&2' via '&1': &3, errno=&4.

DSS00036 "Unable to start child process: &1, errno=&2."

Explanation: Unable to start child process: &1, errno=&2.

DSS00037 "Unable to get PCFILE directory. Records do not exist in the file."

Explanation: Unable to get PCFILE directory. Records do not exist in the file.

DSS00038 "XMS CreateTable received bad return code &1 from putTable, probable out of memory condition."

Explanation: XMS CreateTable received bad return code &1 from putTable, probable out ofmemorycondition.

DSS00039 "TableResponse unable to putTable, record doesn't fit into a block even after new allocation."

Explanation: TableResponse unable to putTable, record doesn't fit into a block even after new allocation.

DSS00042 "Dataset(&1)Owner(&2) System(&3) ASID(&4) TCB(&5)"

Explanation: An attempt to open the PCFILE has failed because it is already open by another address spacewithin the Sysplex. This message identifies the address space that owns the PCFILE.

&1 PCFILE data set name.

&2 Job name of the data set owner.

&3 System identifier of the data set owner.

&4 Address Space Identifier of the data set owner.

6


&5 Task Control Block address of the data set owner.

DSS01000 "Attempted to open an already-open DCB: DDNAME '&1'. Please call ASG Technologies CustomerSupport."

Explanation: Attempted to open an already-open DCB: DDNAME '&1'.

Action: Please call ASG Technologies Customer Support.

DSS01001 "File '&1 &2' cannot be closed."

Explanation: File '&1&2' cannot be closed.

DSS01002 "Unable to open '&1' for &2. &3."

Explanation: Unable to open '&1' for &2. &3.

DSS01003 "Error in writing '&1'."

Explanation: Error in writing '&1'.

DSS01004 "Input DCB does not exist."

Explanation: Input DCB (SIVIN) does not exist, so the SYSIN LRECL cannot be determined.

DSS01005 "DDInVio constructor error: VIOFile pointer is specified with an incorrect DISP1. Please call ASGTechnologies Customer Support."

Explanation: DDInVio constructor error: VIOFile pointer is specified with an incorrect DISP1.


DSS01006 "Unidentified MPL File."

Explanation: Unidentified MPL File.

DSS01007 "Syntax error in '&1' MPL file. Please call ASG Technologies Customer Support."

Explanation: Syntax error in '&1' MPL file.


DSS01008 "Error reading file '&1'."

Explanation: Error reading file '&1'.

DSS01009 "This report has not been initialized."

Explanation: This report has not been initialized.

DSS01011 "Record length &1 exceeds specified LRECL (&2). Data truncated. &3."

Explanation: Record length &1 exceeds specified LRECL (&2). Data truncated. &3.

DSS01012 "ISPLINK command '&1 &2' failed with return code &3."

Explanation: ISPLINK command '&1&2' failed with return code &3.

7

System Messages

DSS01013 "Current Edit Work file is empty; no records to process."

Explanation: The file being edited is null, or all records in the file have been deleted.

DSS01014 "'get' was called, but DD&1 dataset &2 is not open for input. Please call ASG Technologies CustomerSupport."

Explanation: Access object 'get' was called, but state shows the DD &1 dataset &2 is not open for input.


DSS01016 "Load of &1 MPL succeeded but no meta object was created. Processing terminated."

Explanation: Load of &1MPL succeeded but no meta object was created. Processing terminated.

DSS01018 "Master catalog could not be found. Please call ASG Technologies Customer Support."

Explanation: The 'master' catalog could not be located. This is a severe error which should never occur.


DSS01019 "Unallocated file '&1' cannot be opened. Please call ASG Technologies Customer Support."

Explanation: Unallocated file '&1' cannot be opened.


DSS01020 "DDNAME '&1' cannot be allocated prior to simulating JES processing."

Explanation: DDNAME '&1' cannot be allocated prior to simulating JES processing.

DSS01021 "Input for '&1' processor cannot be read. Please call ASG Technologies Customer Support."

Explanation: Input for '&1' processor cannot be read.


DSS01022 "DD '&1' cannot be closed: It was not open."

Explanation: DD '&1' cannot be closed: It was not open.

DSS01023 "First PROCLIB '&1' cannot be opened."

Explanation: First PROCLIB '&1' cannot be opened.

DSS01024 "Unable to load module '&1' because it was not found in STEPLIB (BLDL failed)."

Explanation: Unable to load module '&1' because it was not found in STEPLIB (BLDL failed).

DSS01025 "Stow failed for DSN '&1' member '&2' because of a prior failure."

Explanation: Stow failed for DSN '&1' member '&2' because of a prior failure.

DSS01026 "Unable to delete module '&1'."

Explanation: Unable to deletemodule '&1'.

DSS01027 "Unable to read MetaParmmember '&1'. Incomplete product control file."

Explanation: Unable to read MetaParm member '&1'. Incomplete product control file.

8


DSS01028 "Module '&1' has AMODE=24, but one of its parameters is above the 16-meg line."

Explanation: Module '&1' has AMODE=24, but one of its parameters is above the 16-meg line.

DSS01029 "Unable to write a record to sequential file '&1'. &2."

Explanation: Unable to write a record to sequential file '&1'. &2.

DSS01031 "Unable to read from '&1'. &2."

Explanation: Unable to read from '&1'. &2.

DSS01032 "Unable to close '&1'. &2."

Explanation: Unable to close '&1'. &2.

DSS01033 "An attempt wasmade to write to '&1', but the file was not opened."

Explanation: An attempt was made to write to '&1', but the file was not opened. This is an internal error.


DSS01034 "VSAM&1 file is not supported for this use."

Explanation: An attempt was made to open &1 a VSAM file, when a file type of PO, PS,LIBRARIAN, orPANVALET was expected.

DSS01035 "Dataset &1 has a DSORGof &2. Expected PO, PS, PANVALET, or LIBRARIAN."

Explanation: Dataset &1 has a DSORG of &2. Expected PO, PS, PANVALET, or LIBRARIAN.

DSS01036 "Directory services are not available for &1. It is a sequential dataset."

Explanation: Directory services are not available for &1. It is a sequential dataset.

DSS01037 "Dataset &1 has a DSORGof &2. Expect a physical sequential (PS) dataset."

Explanation: Dataset &1 has a DSORG of &2. Expect a physical sequential (PS) dataset.

DSS01038 "Unable to start trace &1. File &2 cannot be opened."

Explanation: A request to start a trace could not be completed because the specified file could not beopened.

DSS01039 "Unable to perform write action to file '&1'. '&2'."

Explanation: Unable to perform write action to file '&1'. '&2'.

DSS01040 "Dataset &1 has a DSORGof &2. Expected &3."

Explanation: Dataset &1 has a DSORG of &2. Expected &3.

DSS01041 "Dataset &1 has a RECFM of &2. Expected &3."

Explanation: Dataset &1 has a RECFM of &2. Expected &3.

DSS01042 "IOSFindDSCB on dataset &1 got a return code &2."

Explanation: IOSFindDSCB on dataset &1 got a return code &2.

9

System Messages

DSS01043 "Unable to find MetaParmmember '&1' in the local PCFILE. Incomplete product control file."

Explanation: Unable to find MetaParm member '&1' in the local PCFILE. Incomplete product control file.

DSS01100 "OPEN failed for DD='&1' DSN='&2'. Return code='&3'; reason code='&4'."

Explanation: OPEN failed for DD='&1' DSN='&2'. Return code='&3'; reason code='&4'.

DSS01101 "WRITE failed for DD='&1' DSN='&2'. ABENDS&3, out of space error."

Explanation: WRITE failed for DD='&1' DSN='&2'. ABEND S&3, out of space error.

Action: Look in JESYSMSG for more information.

DSS01102 "CLOSE failed for DD='&1' DSN='&2'. Return code='&3'."

Explanation: CLOSE failed for DD='&1' DSN='&2'. Return code='&3'.

DSS01103 "WRITE failed for DD='&1' DSN='&2'. Return code='&3'."

Explanation: WRITE failed for DD='&1' DSN='&2'. Return code='&3'. '&4'.

DSS01104 "FIND failed for DD='&1' DSN='&2'. Return code='&3'."

Explanation: FIND failed for DD='&1' DSN='&2'. Return code='&3'. '&4'.

DSS01105 "FINDNEXT failed for DD='&1' DSN='&2'. Return code='&3'."

Explanation: FIND NEXT failed for DD='&1' DSN='&2'. Return code='&3'. '&4'.

DSS01106 "READ failed for DD='&1' DSN='&2'. Return code='&3'."

Explanation: READ failed for DD='&1' DSN='&2'. Return code='&3'. '&4'.

DSS01107 "WRITE failed for DSN='&2'. Record size exceeded LRECL."

Explanation: WRITE failed for DD='&1' DSN='&2'. Record size exceeded LRECL. Return code='&3'. '&4'.

DSS01108 "STOW failed for DD='&1' DSN='&2' MEMBER='&3'. Return code='&4'."

Explanation: STOW failed for DD='&1' DSN='&2' MEMBER='&3'. Return code='&4'. '&5'.

DSS01109 "I/O failed for DD='&1', DSN='&2'. Return code='&3'. '&4'."

Explanation: I/O failed for DD='&1', DSN='&2'. Return code='&3'. '&4'.

DSS01110 "Unable to open '&1' allocated to DD '&2'. Return code =S-013; reason code '&3'."

Explanation: Unable to open '&1' allocated to DD '&2'. Return code =S-013; reason code '&3'.

DSS01111 "Unable to open '&1' allocated to DD '&2'. Return code =S-213; reason code '&3'."

Explanation: Unable to open '&1' allocated to DD '&2'. Return code = S-213; reason code '&3'.

DSS01112 "Not authorized to open '&1' allocated to DD '&2'."

Explanation: Unable to open '&1' allocated to DD '&2'. Return code = S-913; reason code '&3'. See IBMmessage IEC150I.

DSS01113 "Unable to open '&1' allocated to DD '&2'. Unsupported RECFM."

10


Explanation: Unable to open '&1' allocated to DD '&2'. Unsupported RECFM.

DSS01114 "Could not open '&1'. Unable to load DJ0YLIB (LIBRARIAN interface)."

Explanation: Could not open '&1'. Unable to load DJ0YLIB (LIBRARIAN interface).

DSS01115 "Could not open '&1'. FAIR routines not linked with DJ0YLIB."

Explanation: Could not open '&1'. FAIR routines not linked with DJ0YLIB (LIBRARIAN interface).

DSS01116 "Could not open '&1'. Unable to load 'DJ0YHOOK'."

Explanation: Could not open '&1'. Unable to load 'DJ0YHOOK'.

DSS01117 "Could not open '&1': unable to access LIBRARIANmaster file. Return code =&2, reason code =&3."

Explanation: Could not open '&1': unable to access LIBRARIANmaster file. Return code = &2, reason code =&3.

DSS01118 "No libraries assigned for PROCLIB DD '&1'. Check RTS settings for PROCLIB DD's."

Explanation: No libraries assigned for PROCLIB DD '&1'. Check RTS settings for PROCLIB DD's.

DSS01119 "Operand '&1' is not valid."

Explanation: Operand '&1' is not valid.

DSS01120 "Unexpected return code from DFSMS: &1 Reason: &2."

Explanation: Unexpected return code from DFSMS: &1 Reason: &2.

DSS01121 "Bad parameter list passed to DJ0YCAS. Probable mismatch between 'dj0rcas.hpp' and 'dj0rcas.mac'."

Explanation: Bad parameter list passed to DJ0YCAS. Probablemismatch between 'dj0rcas.hpp' and'dj0rcas.mac'.

DSS01122 "'&1' is not a valid DJ0YCAS request."

Explanation: '&1' is not a valid DJ0YCAS request.

DSS01123 "Unexpected return code from DJ0YCAS: &1."

Explanation: Unexpected return code from DJ0YCAS: &1.

DSS01124 "Bad parameter list passed to DJ0YACS. Probable mismatch between 'dj0racs.hpp' and 'dj0racs.mac'."

Explanation: Bad parameter list passed to DJ0YACS. Probablemismatch between 'dj0racs.hpp' and'dj0racs.mac'.

DSS01125 "Unexpected return code from DJ0YACS: &1."

Explanation: Unexpected return code from DJ0YACS: &1.

DSS01126 "'&1' returned by DSSIAPI function '&2'."

Explanation: The following database error was returned by DSSIAPI function '&2': '&1'.

DSS01127 "'&1' received return code &2, reason code &3."

11

System Messages

Explanation: '&1' received return code &2, reason code &3.

DSS01128 "Received selected row not found. SQLCODE=100."

Explanation: Received selected row not found. SQLCODE=100.

DSS01129 "Unable to connect to DB2 subsystem '&1'; return code &2, reason code &3, plan '&4'."

Explanation: Unable to connect to DB2 subsystem '&1'; return code &2, reason code &3, plan '&4'.

DSS01130 "Unable to disconnect from DB2; return code &1."

Explanation: Unable to disconnect from DB2; return code &1.

DSS01131 "Options did not load."

Explanation: Options did not load.

DSS01132 "DJ0YSUTS - RACROUTE ENVIR=CREATE returned RC=&1."

Explanation: DJ0YSUTS - RACROUTE ENVIR=CREATE failed, possibly due to an invalid RUTOKEN.

DSS01133 "R15 value =&1 reason =&2 RBA =&3 Last op =&4."

Explanation: R15 value = &1 reason = &2 RBA = &3 Last op = &4.

DSS01134 "IOS_TERMINATE called before all modules loaded using BIO_pds_handle::loadMember() weredeleted."

Explanation: IOS_TERMINATE called before all modules loaded using BIO_pds_handle::loadMember() weredeleted.

DSS01135 "Error trying to read '&1' from '&2'."

Explanation: Unable to read '&1' from dataset '&2' even though both the dataset and themember exist.

DSS01136 "Unable to delete module '&1'. It was not loaded."

Explanation: BIO_pds_handle::deleteMember() was called to deletemodule '&1', but that module had notbeen loaded using BIO_pds_handle::loadMember().

DSS01137 "Firstproclib dataset '&1' is not a partitioned dataset."

Explanation: Firstproclib dataset '&1' is not a partitioned dataset.

DSS01138 "Member '&1' does not exist in dataset '&2'."

Explanation: Member '&1' does not exist in dataset '&2'.

DSS01139 "Cannot open DD:&1, DSN=&2; specified DSORG '&3' is not valid."

Explanation: Cannot open DD:&1, DSN=&2; specified DSORG '&3' does not match the actual DSORG of thedataset.

DSS01140 "Job '&1' in the member '&2' and any unreferenced entities have been deleted from the INFO/XRepository."

12


Explanation: Job '&1' in themember '&2' and any unreferenced PROCs, programs, datasets, includes, etc,have been deleted from the INFO/X Repository.

DSS01141 "'&1' is not a valid load module name."

Explanation: '&1' is not a valid load module name. It must begin with an alphabetic character.

DSS01142 "'&1' is not a valid load library name."

Explanation: '&1' is not a valid load library name. It must begin with an alphabetic character.

DSS01143 "DJ0YBINDwas not passed an input parameter list. Please call ASG Technologies Customer Support."

Explanation: DJ0YBIND was not passed an input parameter list.


DSS01144 "While processing member '&1' from library '&2', the BINDER returned an error, rc=&3 reason=&4."

Explanation: While processing member '&1' from library '&2', the BINDER returned an error, rc=&3reason=&4.

Action: See the JES job log for other messages.

DSS01145 "The specified nodename '&1' was not found in the INFO/X Repository."

Explanation: The specified nodename '&1' was not found in the INFO/X Repository.

Action: Specify a valid nodename and try again.

DSS01146 "Unsupported BIO file type of '&1' encountered. Please call ASG Technologies Customer Support."

Explanation: Currently, the BIO file type of '&1' is not fully supported and should not be used at this time.

Action: Call ASG Technologies Customer Support for assistance in determining how this BIO file typewas generated.

DSS01147 "Unable to open '&1' allocated to DD '&2'. Return code =S-113;"

Explanation: Unable to open '&1' allocated to DD '&2'. Return code = S-113.

DSS01148 "'&1' DD statement is missing."

Explanation: '&1' DD statement is required for product operation.

DSS01149 "Database &1 for USERID&2 is not initialized properly. Missing IXTINFO row."

Explanation: Database &1 for USERID &2 is not initialized properly. Missing IXTINFO row.

DSS01150 "DB2 database name not specified; cannot perform SQL connect."

Explanation: DB2 database name not specified in Run Time Settings; cannot perform SQL connect.

DSS01151 "DB2 plan name not specified; cannot perform SQL connect."

Explanation: DB2 plan name not specified in Run Time Settings; cannot perform SQL connect.

DSS01152 "'PLATFORM' is now obsolete. Please change to 'NODENAME'."

Explanation: Platforms are now referred to as NODENAME.

13

System Messages

Action: Change PLATFORM = XXXXXXXX to NODENAME = XXXXXXX on your input statement. Supportfor the 'PLATFORM' parameter will be dropped in a future release.

DSS01153 "More than one rowwas found in table &1 for dataset '&2'. Please use the '&3' utility to correct theproblem then rescan the JCL. Contact ASG Technologies Customer Support if the problem still exists."

Explanation: More than one rowwas found in table &1 for dataset &2. This SQL error was returned by thedatabase: &4.

Action: Use the '&3' utility to correct the problem then rescan the JCL. Contact ASG TechnologiesCustomer Support if the problem still exists.

DSS01154 "Windows product password update failed with this SQL error: &1."

Explanation: The attempt to updateWindows product password information failed with this SQL error: &1.

Action: Contact ASG Technologies Customer Support if the problem exists.

DSS01155 "BIOObject is no longer valid for reading."

Explanation: BIO Objects are only valid for reading one time.

Action: Delete the object and create a new one to read the file.

DSS01156 "Sequential files are not valid with SYSeFileSaveAs."

Explanation: SEQ was specified as the first operand of SYSeFileSaveAs, SYSeFileSaveAs is for libraries only.

DSS01157 "Attempt made to write to non-existent file handle."

Explanation: An attempt was made to write to a non-existent file handle. Most likely an API call was madeout of sequence.

DSS01158 "An error occurred creating the directory '&1' for storing the remote database data file. Error code: &2.Error description: &3."

Explanation: An error occurred while attempting to create the directory '&1' for storing the remote databasedata file. This directory must exist in order to support remote database processing. Error code:&2. Error description: &3.

DSS01159 "An error occurred while checking the existence of &4 '&1'. Error code: &2. Error description: &3."

Explanation: An error occurred while checking the existence of &4 '&1'. Error code: &2. Error description: &3.

DSS01160 "'&1' is a regular file and not a directory."

Explanation: '&1' has been created as a regular file when it should exist as a directory.

Action: Consult product administrator at once.

DSS01161 "An error occurred while processing directory '&1'. Error code: &2. Error description: &3."

Explanation: During the processing of directory '&1' an error occurred in the call to function 'telldir'. Errorcode: &2. Error description: &3.

Action: Contact ASG Technologies Customer support if the problem persists.

DSS01162 "An attempt wasmade to read from file '&1', but the file was not opened."

14


Explanation: An attempt was made to read from file '&1', but the file was not opened.

Action: This is an internal error. Call ASG Technologies Customer Support.

DSS01163 "Record number '&4' of the CICS CSD file '&1' has an LRECL of '&2' which is not equal to the expectedLRECL of '&3'."

Explanation: All of the records in the CICS CSD file have an LRECL of '&3' for database processing to beperformed.

Action: Make change the '&1' CICS CSD file to make sure all records have an LRECL of '&3'.

DSS01164 "The ENTITY Highwater Mark is 0 which is incorrect."

Explanation: The ENTITY Highwater Mark is 0 which is incorrect.

DSS01165 "An error occurred while moving file '&1' from directory '&2' to directory '&3'. Error code: &4. Errordescription: &5."

Explanation: An attempt was made to move the file '&1' from directory '&2' to directory '&3'. This operationfailed with an error code '&4' and error description: '&5'.


DSS01166 "An error occurred while attempting to delete the file '&1' from directory '&2'. Error code: &3. Errordescription: &4."

Explanation: An attempt was made to delete the file '&1' from directory '&2'. This operation failed with anerror code '&3' and error description: '&4'.


DSS01167 "During a stat() on '&1', error '&2' occurred. The error message is: &3."

Explanation: While trying to call stat() for file '&1', error number '&2' occurred. The error message is: &3.

DSS01168 "During an fopen() of '&1', error '&2' occurred. The error message is: &3."

Explanation: While trying to call fopen() for file '&1', error number '&2' occurred. The error message is: &3.

DSS01169 "During a chmod() of '&1', error '&2' occurred. The error message is: &3."

Explanation: While trying to change permissions for file '&1', error number '&2' occurred. The error messageis: &3.

DSS01170 "During a chown() of '&1', error '&2' occurred. The error message is: &3."

Explanation: While trying to change the owner for file '&1', error number '&2' occurred. The error message is:&3.

DSS01171 "During a fwrite() to '&1', error '&2' occurred. The error message is: &3."

Explanation: While trying to write to file '&1', error number '&2' occurred. The error message is: &3.

DSS01172 "During a fclose() of '&1', error '&2' occurred. The error message is: &3."

Explanation: While trying to close file '&1', error number '&2' occurred. The error message is: &3.

15

System Messages

DSS01173 "Unable to create directory: &1."

Explanation: Unable to create directory: &1.

DSS01174 "Unable to create member '&1' in dsname '&2'. No directory space available."

Explanation: Unable to createmember '&1' in dsname '&2'. No directory space available. Return code 12from STOW.

DSS01175 "Cannot release DD:&1 DSN:&2 because it is still allocated."

Explanation: Cannot release DD:&1 DSN:&2 because it is still allocated.

DSS01176 "INFO/X AIU parameter '&1' has been deprecated from the INPUT statement. Specify this parameter onthe '&2' statement instead."

Explanation: The INFO/X AIU parameter '&1' has been deprecated from the INPUT statement.

Action: The '&2' statement should be used to specify the desired INFO/X AIU processing options.

DSS01177 "The '&1' statement is currently not supported and is reserved for future use."

Explanation: The '&1' statement is currently reserved for future use.

Action: Do not use the '&1' statement.

DSS01178 "Cannot copy from:'&1' to:'&2'. The error message is:&3."

Explanation: Cannot copy from:'&1' to:'&2'. The error message is:&3.

DSS01179 "LRECL in IOObject(&3) does not match LRECL in DDname &1(&2)."

Explanation: LRECL in IO Object(&3) does not match LRECL in DD name&1(&2).

DSS01180 "Environment Variable '&1' is not defined. This is used for DD emulation on non-MVS platforms."

Explanation: Environment Variable '&1' is not defined. This is used for DD emulation on non-MVS platforms.

DSS01181 "Attempt to open VSAM dataset '&1' with non-VSAMAPI call. Open failed with a S113-2C abend."

Explanation: Attempt to open VSAM dataset '&1' with non-VSAM API call. Open failed with a S113-2C abend.

DSS01182 "Attempted to read file &1 using BIOSegSegmented class. Segment &4 with &2 instead of &3."

Explanation: &3missing. File &1 read &2 instead.

DSS01183 "The Remote Database Update Header tag wasn't found in XML blob. FOLT file will not be created. Hereis the XML blob that was received: &1."

Explanation: The Remote Database Update Header is used by Remote Database processing to create theFOLT file. This tag was not found in the XML blob sent to the repository server, so the FOLT filewill not be created. Here is the XML blob that was received: &1.

DSS01184 "An error occurred while renaming file '&1' to file '&2'. Error code: &3. Error description: &4."

Explanation: An attempt was made to rename the file '&1' to file '&2'. This operation failed with an error code'&3' and error description: '&4'.


16


DSS01185 "No FOLT files matching mask '&1' were found to process. Exiting normally."

Explanation: There were no FOLT files matching mask '&1' were found to process. Exiting normally.

DSS01186 "During '&1' processing, the CRC could not be calculated for member '&2'. Reason: &3."

Explanation: While processing '&1' for member '&2, an attempt to obtain the CRC for this member wasunsuccessful . Reason: &3.

DSS01187 "Table '&1' could not be locked during '&2' processing of dataset '&3'. Error: '&4'."

Explanation: During INFO/Xe '&2' AIU processing of dataset '&3', table '&1' could not be locked due todatabase error '&4'. '&2' processing requires an exclusive lock to this table to function correctly.

Action: Terminate any other INFO/Xe applications that might be accessing this table and re-run the '&2'AIU.

DSS01188 "Member skipped during '&1' processing, due to dataset '&2' being migrated."

Explanation: While processing '&1' for dataset '&2, INFO/X determined that the dataset was migrated.

DSS01189 "DDNAME &1 was specified instead of JPINCLIB with PROCESS=LOADMODULE."

Explanation: PROCESS=LOADMODULE requires the DDNAME to be JPINCLIB instead of DDNAME&1.

DSS01190 "An error occurred opening the JPAIU file. Reason '&1'."

Explanation: An error occurred opening the JPAIU file. Reason '&1'.

DSS01191 "An error occurred writing to the JPAIU file. Reason '&1'."

Explanation: An error occurred writing to the JPAIU file. Reason '&1'.

DSS01192 "BIO :: open invoked without a prior INIT call."

Explanation: BIO :: open invoked without a prior INIT call.

DSS01193 "Rename of &1 to &2 failed because of errno=&3 errmsg=&4."

Explanation: Folt file rename failed renaming &1 to &2. ErrorType &3 and msg &4.

DSS01194 "Attempt to open with a ddname &1 and filename &2 prefixed with a 'DD:' that doesn't match."

Explanation: Attempt to open with a ddname&1 and filename&2 prefixed with a 'DD:' that doesn't match.

DSS01195 "Job '&1' in the member '&2' and any unreferenced entities have been identified for deletion from theINFO/X Repository. The repository was not updated because UPDATEDATABASE was not specified."

Explanation: Job '&1' in themember '&2' and any unreferenced PROCs, programs, datasets, includes, etc,have been identified for deletion from the INFO/X Repository. The repository was not updatedbecause UPDATEDATABASE was not specified.

DSS01196 "Nodename is required."

Explanation: A nodenamemust be specified when executing reports from the database.

Action: Specify a valid nodename and try again.

17

System Messages

DSS01197 "While processing member '&1' from library '&2', the BINDER returned a warning, rc=&3 reason=&4."

Explanation: While processing member '&1' from library '&2', the BINDER returned a warning, rc=&3reason=&4.

Action: See the JES job log for other messages.

DSS01198 "An attempt to spool FOLT data in an uninitialized remote database update configuration wasencountered."

Explanation: An attempt to spool FOLT data in an uninitialized remote database update configuration wasencountered.

Action: Specify either the 'LOCALSPOOL' option or a CONNECT statement to initialize a remotedatabase update configuration.

DSS01199 "Unable to write member '&2' to dataset '&1' because of a prior I/O error."

Explanation: Unable to write member '&2' to dataset '&1' because of a prior I/O error. DDNAME &3.

DSS01200 "Dynamic allocation failed for DD '&1', DSN '&2'; missing parm List for call."

Explanation: Dynamic allocation failed for DD '&1', DSN '&2'; missing parm List for call.

DSS01201 "Dynamic allocation failed for DD '&1', DSN '&2'; request code is not valid."

Explanation: Dynamic allocation failed for DD '&1', DSN '&2'; request code is not valid.

DSS01202 "Dynamic allocation failed for DD '&1', DSN '&2'; request code combination is not valid."

Explanation: Dynamic allocation failed for DD '&1', DSN '&2'; request code combination is not valid.

DSS01203 "Dynamic allocation failed for DD '&1', DSN '&2'; missing DDNAME on request."

Explanation: Dynamic allocation failed for DD '&1', DSN '&2'; missing DDNAME on request.

DSS01204 "Dynamic allocation failed for DD '&1', DSN '&2'; disposition not valid for request type."

Explanation: Dynamic allocation failed for DD '&1', DSN '&2'; disposition not valid for request type.

DSS01205 "Dynamic allocation failed for DD '&1', DSN '&2'; disposition2 not valid for request type."

Explanation: Dynamic allocation failed for DD '&1', DSN '&2'; disposition2 not valid for request type.

DSS01206 "Dynamic allocation failed for DD '&1', DSN '&2'; unit not specified for request."

Explanation: Dynamic allocation failed for DD '&1', DSN '&2'; unit not specified for request.

DSS01207 "Dynamic allocation failed for DD '&1', DSN '&2'; directory space not specified for request."

Explanation: Dynamic allocation failed for DD '&1', DSN '&2'; directory space not specified for request.

DSS01208 "Dynamic allocation failed for DD '&1', DSN '&2'; blocksize is missing on request."

Explanation: Dynamic allocation failed for DD '&1', DSN '&2'; blocksize is missing on request.

DSS01209 "Dynamic allocation failed for DD '&1', DSN '&2'; sysout class is missing on request."

Explanation: Dynamic allocation failed for DD '&1', DSN '&2'; sysout class is missing on request.

18


DSS01210 "Dynamic allocation failed for DD '&1', DSN '&2'; not authorized by SAF routine."

Explanation: Dynamic allocation failed for DD '&1', DSN '&2'; not authorized by SAF routine.

DSS01211 "Unrecognizable status returned by SAF exit: &1. Please call ASG Technologies Customer Support."

Explanation: Unmechanized status returned by SAF exit: &1. You may havemodified the SAF exit to returnan invalid status code.


DSS01212 "&1 is not a valid user id."

Explanation: &1 is not a valid user id. It is not defined to your security system, or its access been revoked.

DSS01213 "No ddnames available, all names are in use already."

Explanation: Unable to generate a DDNAME for SVC99 allocation. Table of names in use is full.

Action: Use the ALLOC operator command for more information.

DSS01214 "SVC26 invocation failure. SVC26 return code=&1 reason code=&2."

Explanation: Invocation of dj0ycdsl calling SVC26 in an SVC26 failure. return code=&1 , reason code=&2.

DSS01215 "DJ0YCDSL invalid parameter list. Either bad CDSL control block or DSNmask not alpha or starting with#,$,@. Mask=&1."

Explanation: DJ0YCDSL invalid parameter list. Either bad CDSL control block or DSNmask not alpha orstarting with #,$,@. Mask=&1.

DSS01220 "SYSeFileCreate failed with invalid status &1."

Explanation: SyseFileCreate failed with invalid status &1.

DSS01221 "SYSeFileCreate failed with invalid disposition &1."

Explanation: SyseFileCreate failed with invalid disposition &1.

DSS01222 "SYSeFileCreate failed with invalid allocation unit &1."

Explanation: SyseFileCreate failed with invalid allocation unit &1.

DSS01226 "Dynfree for &1 failed with error code=&2, info code=&3."

Explanation: Dynfree for &1 failed with error code=&2, info code=&3.

DSS01227 "Unable to delete dataset &1. Dataset does not exist."

Explanation: Unable to delete dataset &1. Dataset does not exist.

DSS01228 "Unable to delete dataset &1. Dynalloc failed with error code &2, info code &3."

Explanation: Unable to delete dataset &1. Dynalloc failed with error code &2, info code &3.

DSS01229 "Unable to allocate dataset &1 - received return code 970C from dynamic allocation (SVC99). SevereSMS VTOCservice error. Check your logrec dataset for more information."

19

System Messages

Explanation: Unable to allocate dataset &1 - received return code 970C from dynamic allocation (SVC99).Severe SMS VTOC service error.

Action: Check your logrec dataset for more information.

DSS01230 "Unable to allocate and catalog dataset &1. Invalid parameter specified."

Explanation: Unable to allocate and catalog dataset &1. Invalid parameter specified.

DSS01231 "Unable to allocate and catalog dataset &1. Invalid dataset name."

Explanation: Unable to allocate and catalog dataset &1. Invalid dataset name.

DSS01232 "Unable to allocate dataset &1 - received return code 9700 from dynamic allocation (SVC99). Checkyour logrec dataset for more information."

Explanation: Unable to allocate dataset &1 - received return code 9700 from dynamic allocation (SVC99).

Action: Check your logrec dataset for more information.

DSS01233 "Unable to DYNALLOCdataset &1 on system assigned unit. Possible authorization problem."

Explanation: Unable to DYNALLOC dataset &1 on system assigned unit. Possible authorization problem.

DSS01240 "doDynalloc received an invalid parameter. Status was &1 instead of OLD, NEW, MODor SHR."

Explanation: doDynalloc received an invalid parameter. Status was &1 instead of OLD, NEW, MOD or SHR.

DSS01241 "doDynalloc received an invalid parameter. normdisp was &1 instead of CATLG, UNCATLG, DELETEor KEEP."

Explanation: doDynalloc received an invalid parameter. normdisp was &1 instead of CATLG, UNCATLG,DELETE or KEEP.

DSS01242 "doDynalloc received an invalid parameter. condisp was &1 instead of CATLG, UNCATLG, DELETE orKEEP."

Explanation: doDynalloc received an invalid parameter. condisp was &1 instead of CATLG, UNCATLG, DELETEor KEEP.

DSS01243 "doDynalloc received an invalid parameter. dsorg was &1 instead of Unknown, VSAM, GS, PO, POU,DA, DAU, PS, PSU."

Explanation: doDynalloc received an invalid parameter. dsorg was &1 instead of Unknown, VSAM, GS, PO,POU, DA, DAU, PS, PSU.

DSS01244 "doDynalloc received an invalid parameter. alcunit was &1 instead of TRK or CYL."

Explanation: doDynalloc received an invalid parameter. alcunit was &1 instead of TRK or CYL.

DSS01245 "doDynalloc received an invalid parameter. recfm contained the character &1 instead of M, A, S, B, D, V,F or U."

Explanation: doDynalloc received an invalid parameter. recfm contained the character &1 instead ofM, A, S,B, D, V, F or U.

DSS01246 "doDynalloc received an invalid parameter. recfm was specified but contained no value."

20


Explanation: doDynalloc received an invalid parameter. recfm was specified but contained no value.

DSS01247 "doDynalloc received an invalid parameter. miscitems was specified but code cannot handle it yet."

Explanation: doDynalloc received an invalid parameter. miscitems was specified but code cannot handle ityet.

DSS01248 "doDynalloc received an invalid parameter. recorg was &1 instead of KS, ES, RRor LS."

Explanation: doDynalloc received an invalid parameter. recorg was &1 instead of KS, ES, RR or LS.

DSS01249 "doDynalloc received an invalid parameter. dsntype was &1 instead of HFS, LIBRARY, PDS or PIPE."

Explanation: doDynalloc received an invalid parameter. condisp was &1 instead of HFS, LIBRARY, PDS orPIPE.

DSS01250 "doDynalloc received an invalid parameter. pathopts was &1 instead of OCREAT, OAPPEND, OEXCL,ONOCTTY, OTRUNC, ONONBLOCK, ORDONLY, OWRONLY or ORDWR."

Explanation: doDynalloc received an invalid parameter. pathopts was &1 instead of OCREAT, OAPPEND,OEXCL, ONOCTTY, OTRUNC, ONONBLOCK, ORDONLY, OWRONLY or ORDWR.

DSS01251 "doDynalloc received an invalid parameter. pathmode was &1 instead of SIRUSR, SIWUSR, SIXUSR,SIRWXU, SIRGRP, SIWGRP, SIXGRP, SIRWXG, SIROTH, SIWOTH, SIXOTH, SIRWXO, SISUID or SISGID."

Explanation: doDynalloc received an invalid parameter. pathmodewas &1 instead of SIRUSR, SIWUSR,SIXUSR, SIRWXU, SIRGRP, SIWGRP, SIXGRP, SIRWXG, SIROTH, SIWOTH, SIXOTH, SIRWXO,SISUID or SISGID.

DSS01252 "doDynalloc received an invalid parameter. pathdisp was &1 instead of KEEP or DELETE."

Explanation: doDynalloc received an invalid parameter. pathdisp was &1 instead of KEEP or DELETE.

DSS01253 "doDynalloc received an invalid parameter. pathcdisp was &1 instead of KEEP or DELETE."

Explanation: doDynalloc received an invalid parameter. pathcdisp was &1 instead of KEEP or DELETE.

DSS01254 "doDynalloc received an invalid parameter. rls was &1 instead of NRI or CR."

Explanation: doDynalloc received an invalid parameter. rls was &1 instead of NRI or CR.

DSS01255 "doDynalloc received an invalid parameter. sysout was greater than one character."

Explanation: doDynalloc received an invalid parameter. sysout was greater than one character.

DSS01256 "Internal error: DD name &1 is already allocated cannot be allocated to &2."

Explanation: Internal error: DD name&1 is already allocated cannot be allocated to &2.

DSS01257 "Unable to allocate DSN&1 to DDNAME &2. That DDNAME is already in use."

Explanation: Unable to allocate DSN&1 to DDNAME&2. That DDNAME is already in use.

DSS01289 "DD '&1' was not preallocated. DDNAME not found in product JCL."

Explanation: DD '&1' was not preallocated. DDNAME not found in product JCL.

21

System Messages

DSS01290 "'&1' was specified in the RTS Dataset Preference table."

Explanation: '&1' was specified in the RTS Dataset Preference table. The previous error is pertaining to thepreferred dataset or DDNAME to use first.

DSS01291 "'&1' is in use, unable to wait for access to it due to failure of SYSDSNENQ. DJ0YENQRC=&2."

Explanation: '&1' is in use, unable to wait for access to it due to failure of SYSDSN ENQ. DJ0YENQ RC=&2.

Action: Contact ASG Technologies Customer Support.

DSS01292 "'&1' is in use, unable to wait for access to it due to lack of APF authorization."

Explanation: '&1' is in use, unable to wait for access to it due to lack of APF authorization.

DSS01293 "Allocation failed for DSN '&1'; Invalid input parameter, possible syntax error. &4."

Explanation: Dynamic allocated failed for DSN '&1'; SVC 99 return code was '&2' infocode was '&3'. &4.

DSS01294 "Allocation failed for DSN '&2'; Dataset currently in use. DARC='&3'."

Explanation: Dynamic allocation failed for DD '&1', DSN '&2'; Dataset currently in use. DARC='&3'.

DSS01295 "Dynamic allocation failed for load library '&1'; DARC '&2' INFO '&3'."

Explanation: Dynamic allocation failed for load library '&1'; DARC '&2' INFO '&3'.

DSS01296 "Unable to allocate &1. Dataset not found."

Explanation: Dynamic allocation failed for &1; entry not found.

DSS01297 "Dynamic allocation failed for DD '&1' DSN '&2'; RC 12, DARC '&3', INFO '&4'. &5."

Explanation: Dynamic allocation failed for DD '&1' DSN '&2'; RC 12, DARC '&3', INFO '&4'. &5.

DSS01298 "Dynamic allocation failed for DD '&1' DSN '&2'; RC 8, DARC '&3', INFO '&4'. &5."

Explanation: Dynamic allocation failed for DD '&1' DSN '&2'; RC 8, DARC '&3', INFO '&4' &5.

DSS01299 "Dynamic allocation failed for DD '&1' DSN '&2'; RC '&3', DARC '&4'. See JESMSGLG for details. &5."

Explanation: Dynamic allocation failed for DD '&1' DSN '&2'; RC '&3', DARC '&4'.

Action: See JESMSGLG for details. &5.

DSS01300 "Duplicate key - Unable to write new record '&1' to '&2'."

Explanation: The record '&1' was unable to be added to the file '&2', because a record with the same keyalready exists in '&2'.

DSS01400 "Received RC=&1 running REXX EXEC '&2'."

Explanation: Received RC=&1 running REXX EXEC '&2'.

DSS01401 "REXX EXECname '&1' &2 characters too long; max length is &3."

Explanation: REXX EXEC name '&1' is &2 characters too long; max length is &3.

DSS01402 "JMP Selected but no JMP program name provided."

22


Explanation: JMP Selected but no JMP program name provided.

Action: Specify a JMP program.

DSS01403 "REXX EXEC '&1' not found."

Explanation: The REXX EXEC named '&1' does not exist in the libraries that were searched.

DSS01404 "Execution of REXX EXEC '&1' received RC=&2."

Explanation: Execution of REXX EXEC '&1' received RC=&2.

DSS01405 "&1 received erroneous &2; &3 is not 9 characters long."

Explanation: &1 received erroneous &2; &3 is not 9 characters long.

DSS01406 "&1 expected &2, but received nothing."

Explanation: &1 expected &2, but received nothing.

DSS01407 "&1 expected &2, but received &3."

Explanation: &1 expected &2, but received &3.

DSS01408 "DSSIAPI call '&1' called out of sequence; RTS is not initialized."

Explanation: DSSIAPI call '&1' called out of sequence; RTS is not initialized.

DSS01409 "Create Stmt does not support language type '&1'."

Explanation: Create Stmt does not support language type '&1'.

DSS01410 "'&1' is not a valid statement for language '&2'."

Explanation: '&1' is not a valid statement for language '&2'.

DSS01411 "Unable to execute REXX EXEC '&1'. Return code 20 from IRXEXEC."

Explanation: Unable to execute REXX EXEC '&1'. Return code 20 from IRXEXEC.

DSS01412 "Syntax error '&1' in REXX EXEC '&2'."

Explanation: Syntax error '&1' in REXX EXEC '&2'.

DSS01413 "Unable to add parm '&1' to &2; not supported."

Explanation: Unable to add parm '&1' to &2; not supported.

DSS01414 "Unable to insert &1 because the preceding &2 did not come from a file."

Explanation: Unable to insert the new&1 because the preceding &2 did not come from a file. PRO/JCL willinsert new&1s only if the preceding &1was read from a file during a JCL scan.

DSS01415 "No statement available for insert at position &1."

Explanation: No statement available for insert at position &1.

DSS01416 "Unable to add new parms to &1 statement due to syntax errors."

Explanation: Unable to add new parms to &1 statement due to syntax errors.

23

System Messages

DSS01417 "Unable to create new&2 statement '&1'; not supported."

Explanation: Unable to create new&2 statement '&1'; not supported.

DSS01418 "The DSSIAPI REXX environment has not been properly initialized."

Explanation: The DSSIAPI REXX environment has not been properly initialized.

DSS01419 "The DSSIAPI SQL environment has not been properly initialized."

Explanation: The DSSIAPI SQL environment has not been properly initialized. Therefore the '&1' SQL API callhas been made out of sequence.

Action: Make sure the DSSIAPI SQL environment has been properly initialized before issuing the '&1'SQL API call.

DSS01420 "JMPGetLoadLibrary is only meaningful on EXECPGM= statements."

Explanation: JMPGetLoadLibrary is only meaningful on EXEC PGM= statements.

DSS01421 "IRXINIT failed rc=&1 reason=&2. Cannot execute the REXX EXEC&3."

Explanation: Unable to initialize REXX environment. IRXINIT failed rc=&1 reason=&2. Cannot execute theREXX EXEC &3.

DSS01422 "Unable to support client. System API is at version &1 and client is &2."

Explanation: Unable to support client. System API is at version &1 and client is &2.

DSS01423 "API Server expected an APIREQUEST tag. However not tag could be identified in &1."

Explanation: API Server expected an APIREQUEST tag. However not tag could be identified in &1.

DSS01424 "API Server expected an APIREQUEST tag. However &1 was received."

Explanation: API Server expected an APIREQUEST tag. However &1was received.

DSS01425 "Sender &1, connected but disconnected before sending data."

Explanation: Sender &1, connected but disconnected before sending data.

DSS01426 "Sender &1, disconnected but had not sent STOP command. Possible abnormal termination - shuttingdown."

Explanation: Sender &1, disconnected but had not sent STOP command. Possible abnormal termination -shutting down.

DSS01427 "Data sent to server &1, but server disconnected before returning any data."

Explanation: Data sent to server &1, but server disconnected before returning any data.

DSS01428 "Internal Error No data sent from server, &1."

Explanation: Internal Error No data sent from server, &1.

DSS01429 "Client did not receive an XML packet, but rather: &1."

Explanation: Client did not receive an XML packet, but rather: &1.

24


DSS01430 "REXX EXEC '&1' was not found. Unable to preload '&1'."

Explanation: Return code -3 loading REXX EXEC. Could not find member '&1'.

DSS01431 "Unable to terminate the REXX environment. rc = &1 from IRXTERM."

Explanation: Unable to terminate the REXX environment. rc = &1 from IRXTERM.

DSS01432 "Unable to load REXX EXEC '&1'. Return code '&2' from IRXLOAD."

Explanation: Unable to invoke REXX EXEC '&1'. Return code '&2' from IRXLOAD.

DSS01500 "Resource '&1' is not available; duplicate request. ENQ return code = 14."

Explanation: Resource '&1' is not available; duplicate request. ENQ return code = 14.

DSS01501 "Resource '&1' is not available; the limit for the concurrent resource requests has been reached. ENQreturn code = 18."

Explanation: Resource '&1' is not available; the limit for the concurrent resource requests has been reached.ENQ return code = 18.

DSS01502 "Resource '&1' is not available; unidentified return code &2 from ENQHAVE."

Explanation: Resource '&1' is not available; unidentified return code &2 from ENQ HAVE.

DSS01503 "Resource '&1' is not available; unidentified return code &2 from ENQUSE."

Explanation: Resource '&1' is not available; unidentified return code &2 from ENQ USE.

DSS01504 "Resource '&1' is not available; unidentified return code &2 from ENQTEST."

Explanation: Resource '&1' is not available; unidentified return code &2 from ENQ TEST.

DSS01505 "Resource '&1' was not released; current task has already requested a release."

Explanation: Resource '&1' was not released; current task has already requested a release.

DSS01506 "Resource '&1' was not released; current task does not hold a lock."

Explanation: Resource '&1' was not released; current task does not hold a lock.

DSS01507 "Resource '&1' is not released; unidentified return code &2 from DEQ."

Explanation: Resource '&1' is not released; unidentified return code &2 from DEQ.

DSS01508 "Member &2 in output file &1 is in use."

Explanation: Could not write to output file &1 becausemember &2 is in use by someone else.

DSS01509 "Warning: Freeing leftover ENQ:&1."

Explanation: Warning: Freeing leftover ENQ:&1.

DSS01510 "Requested DEQ for &1 was not performed. The resource is not currently enqueued."

Explanation: Resource &1 is not enqueued in this address space. The resourcemay have been enqued in aprimary started task, and the connection to the primary was lost.

25

System Messages

DSS01511 "Warning: ENQ created but ENQ List exceeded. Unable to add to ENQ list for &1 &2."

Explanation: Warning: ENQ created but ENQ List exceeded. Unable to add to ENQ list for &1&2.

DSS01512 "&1 is not a defined resource name."

Explanation: Resource &1 is not defined in syncro.hpp RNAMES.

DSS01600 "APF authorization is required to validate access to this dataset."

Explanation: APF authorization is required to validate access to this dataset.

DSS01601 "RACINIT (SVC131) return code &1 &2."

Explanation: RACINIT (SVC 131) return code &1&2.

DSS01602 "RACROUTE REQUEST=VERIFY return code: &1 &2 &3."

Explanation: RACROUTE REQUEST=VERIFY return code: &1&2&3.

DSS01700 "Nomembers selected."

Explanation: No members selected.

DSS01701 "&1 &2 selected from dataset &3."

Explanation: &1&2 selected from dataset &3.

DSS01702 "Total: &1 &2 processed."

Explanation: Total: &1&2 processed.

DSS01703 "&1 processed. Max return code &2."

Explanation: &1 processed. Max return code &2.

DSS01704 "I/O Error on dataset '&2', member '&1'. Member skipped."

Explanation: I/O Error on dataset '&2', member '&1'. Member skipped.

DSS01705 "&1 was processed. Max return code &2."

Explanation: &1was processed. Max return code &2.

DSS01706 "No dataset was specified."

Explanation: No dataset was specified.

DSS01707 "Unable to allocate dataset &1. Processing halted."

Explanation: Unable to allocate dataset &1. Processing halted.

DSS01708 "No processors were specified; selections not processed."

Explanation: No processors were specified; selections not processed.

DSS01709 "Processors selected: &1."

26


Explanation: This informational message indicates the processors which were invoked for this run ofPRO/JCL.

DSS01710 "Dataset '&1' is not a PDS, but members were specified."

Explanation: Dataset '&1' is not a PDS, but members were specified.

DSS01711 "JCL not found in &1; no processing done."

Explanation: JCL not found in &1; no processing done.

DSS01712 "PRO/JCL input limit has been reached."

Explanation: PRO/JCL input limit has been reached.

DSS01713 "Nomembers were selected based on &1."

Explanation: No members were selected based on &1.

DSS01714 "Nomembers were selected based on &1 (possibly because of excluded members)."

Explanation: No members were selected based on &1 (possibly because of excluded members).

DSS01715 "No valid input selection was found."

Explanation: No valid input selection was found.

DSS01716 "Maximum number of spannedmembers is &1. This run requires &2. Use multiple INPUT statements."

Explanation: Maximum number of spanned members is &1. This run requires &2. Usemultiple INPUTstatements.

DSS01717 "No INPUT statements to process."

Explanation: The SYSIN stream contains no 'INPUT' statement.

Action: At least one 'INPUT' statement is required, in order to identify the source of the JCL to bevalidated. Possible causes for this error includemisspelling the word 'INPUT'.

DSS01718 "The INFO/X Update Factory was NOT properly initialized. Please contact ASG Technologies CustomerSupport."

Explanation: An attempt was made to use the INFO/X Update Factory BEFORE it was actually created.


DSS01719 "Cannot perform database update; missing RTS Setting for DB2 Subsystem Name."

Explanation: Cannot perform database update; missing RTS Setting for DB2 Subsystem Name.

DSS01720 "Cannot perform database update; missing RTS Setting for DB2 Database Name."

Explanation: Cannot perform database update; missing RTS Setting for DB2 Database Name.

DSS01721 "Unidentified processing mode '&1'."

Explanation: The requested processing mode '&1' is not valid. Valid modes include 'JOB', 'PROC', 'IDCAMS','IEBGENER', 'IEBCOPY', 'IEHPROGM', and 'DB2'.

27

System Messages

DSS01722 "Input type specified '&1' does not agree with type found for dataset '&2'."

Explanation: The type of the dataset named '&2' is not '&1', the input type requested.

DSS01723 "No processing done for this input statement."

Explanation: No processing done for this input statement.

DSS01724 "Member '&1' was not updated. A JOB statement was found during PROCESS=PROCprocessing."

Explanation: A JOB statement is not allowed within a PROC.

Action: If this is a JOB and not a PROC, either change the input statement parameter to PROCESS=JOB,or exclude this member from PROCESS=PROC processing.

DSS01725 "Error found in input. All processing stopped."

Explanation: This is caused by a syntax error in the input stream.

Action: Review any accompanying error messages.

DSS01726 "There was an error in the INPUT cards for the DSSIAPI call."

Explanation: There was an error in the INPUT cards for the DSSIAPI call.

DSS01727 "The ISPF Edit Work Area was scanned. Max return code &1."

Explanation: The ISPF Edit Work Area was scanned. Max return code &1.

DSS01728 "The FROMDSN '&1' has already been specified. TODSN '&2' cannot be used for changedmembers."

Explanation: The FROMDSN '&1' has already been specified. TODSN '&2' cannot be used for changedmembers.

DSS01729 "The specified Selection list name &1 does not exist."

Explanation: The specified Selection list name&1 does not exist.

DSS01730 "When Type is LIST, only one selection list name per INPUT statement is allowed."

Explanation: When Type is LIST, only one selection list name per INPUT statement is allowed.

DSS01731 "When Type is LIST, a masked selection list name is not valid."

Explanation: When Type is LIST, a masked selection list name is not valid.

DSS01732 "'&1' dataset '&2' not found."

Explanation: The '&1' parameter was coded, but the dataset to which it refers, '&2', does not exist.

DSS01733 "OUTPUT dataset '&1' must be type '&2'."

Explanation: The TO dataset on the OUTPUT statement is not '&2'; processing stopped.

DSS01734 "Unable to access Firstproclib dataset &1."

Explanation: Unable to access Firstproclib dataset &1. The Input statement was not processed.

DSS01735 "Selection List member '&1', does not have any selected members'."

28


Explanation: '&1' Selection List member does not have any members to validate.

DSS01736 "JMP program &2 was used instead of &1. Your administrator has assigned program &2 to user &3."

Explanation: JMP program &2was used instead of &1. Your administrator has assigned program &2 to user&3.

DSS01737 "JMP dataset &2 was used instead of &1. Your administrator has assigned dataset &2 to user &3."

Explanation: JMP dataset &2was used instead of &1. Your administrator has assigned dataset &2 to user&3.

DSS01738 "Total: &1 remote members processed for this ROUTE card."

Explanation: Total: &1 remotemembers processed for this ROUTE card.

DSS01739 "Unable to process filename '&1' because of invalid file type '&2'."

Explanation: Filename '&1' with invalid file type '&2' was found in the database. File '&1' will not beprocessed.

DSS01740 "Allocation failed by ACS routine or exit. Return code=&1, reason code=&2."

Explanation: Allocation would be failed by your data center's ACS routine or ACS routine exit. Returncode=&1, reason code=&2.

DSS01741 "Error encountered with the '&1' file. No BETA42 processing done."

Explanation: Error encountered with the '&1' file. No BETA42 processing done.

DSS01742 "No TASKNAME supplied for BETA42. No BETA42 processing done."

Explanation: No TASKNAME supplied for BETA42. No BETA42 processing done.

DSS01743 "JCLmay be in ISPF packed format."

Explanation: The JCL statement has been flagged as an unidentified JCL statement by PRO/JCL. The formatof the statement indicates the JCL was saved with ISPF pack on.

DSS01744 "&1 process completed."

Explanation: &1 process completed.

DSS01745 "Scheduler &2 was used instead of &1. Your administrator has assigned scheduler &2 to user &3."

Explanation: Scheduler &2was used instead of &1. Your administrator has assigned scheduler &2 to user&3.

DSS01746 "No scheduler was used - Selected scheduler &1 was ignored. Your administrator requires no schedulerbe used for user &2."

Explanation: No scheduler was used - Selected scheduler &1was ignored. Your administrator requires noscheduler be used for user &2.

DSS01747 "&1 Statement requires a remote connection. Missing a ROUTE statement."

Explanation: &1 Statement requires a remote connection. Missing a ROUTE statement.

29

System Messages

DSS01748 "Nomembers were found to Send."

Explanation: No members were found to Send.

DSS01749 "Nomember name was provided for SYSeFileLock on dataset &1 of type &2."

Explanation: No member namewas provided for SYSeFileLock on dataset &1 of type &2.

DSS01750 "Cannot open directory &1. &2."

Explanation: Cannot open directory &1. &2.

DSS01751 "Do not specify a member name (&2) for a sequential dataset (&1). SYSeFileLock."

Explanation: Do not specify a member name (&2) for a sequential dataset (&1). SYSeFileLock.

DSS01752 "&1 sent to &2 on &3."

Explanation: &1 sent to &2 on &3.

DSS01753 "Connected to &1, System &2 on port &3 as user &4."

Explanation: Connected to &1, System &2 on port &3 as user &4.

DSS01754 "Member &1 was processed on &2. Max Return Code &3."

Explanation: Member &1was processed on &2. Max Return Code &3.

DSS01755 "&1 received from &2 on system &3."

Explanation: &1 received from &2 on system &3.

DSS01756 "Missing input dataset name."

Explanation: Missing input dataset name.

DSS01757 "Sent editwork area to &1."

Explanation: Sent editwork area to &1.

DSS01758 "Return code from ROUTE was &1."

Explanation: Return code from ROUTE was &1.

DSS01759 "The first parameter to runGetInputSelectionReport() should be a numeric report width not &1."

Explanation: The first parameter to runGetInputSelectionReport() should be a numeric report width not &1.

DSS01760 "The &1 keyword is not valid on a &2 statement."

Explanation: The &1 keyword is not valid on a &2 statement.

DSS01761 "Unable to &1 from SEQUENTIAL file &2 to library &3, no destination member name is available."

Explanation: Unable to &1 from SEQUENTIAL file &2 to library &3, no destination member name is available.

DSS01762 "Unable to &1multiple members from library &2 to SEQUENTIAL file &3."

Explanation: Unable to &1multiple members from library &2 to SEQUENTIAL file &3.

30


DSS01763 "&1members RECEIVED."

Explanation: &1members RECEIVED.

DSS01764 "RunGetRemoteSJLReport was called after RunTermMemSel. That is out of order."

Explanation: RunGetRemoteSJLReport was called after RunTermMemSel. That is out of order.

DSS01765 "Unable to allocate dataset &1. Missing Parameter &2."

Explanation: Unable to allocate dataset &1. Missing Parameter &2.

DSS01766 "Invalid length qualifier - All Dsname Level qualifiers must be 1 to 8 characters in length."

Explanation: Invalid length qualifier - All Dsname Level qualifiers must be 1 to 8 characters in length.

DSS01767 "Dataset namemasks with the first character of '*' are not supported. Specify the first character."

Explanation: Dataset namemasks with the first character of '*' are not supported.

Action: Specify the first character.

DSS01768 "CONNECT Statement specified a MUSH record &1 that does not exist in the PCFile."

Explanation: CONNECT Statement specified a MUSH record &1 that does not exist in the PCFile.

DSS01769 "&1 version &2 processing &3."

Explanation: &1 version &2 processing &3.

DSS01770 "Unable to disconnect from remote host, you are not connected."

Explanation: An attempt was made to disconnect a pass thru of API requests, but no remote connectionexists.

DSS01771 "An error occurred obtaining system name. Return code '&1' received."

Explanation: A return code of '&1' received while attempting to obtain the system name of this system.

DSS01772 "Unable to apply maintenance. APPLY failed, member has changed."

Explanation: Unable to apply maintenance. APPLY failed, member has changed.

DSS01773 "&1 processed &2 datasets and updated &3 in the '&4' INFO/X Repository."

Explanation: &1 processed &2 datasets and updated &3 in the '&4' INFO/X Repository.

DSS01774 "A &3member must be specified because user '&1' has an assigned &2 &3 list."

Explanation: A&3member must be specified because user '&1' has an assigned &2&3 list.

Action: Specify a &3member on the assigned list.

DSS01775 "A &3 '*LIST*' was assigned, but member '&1' no longer exists on the PCFILE. Please consult productadministrator."

Explanation: A&3 '*LIST*' was assigned, but member '&1' no longer exists on the PCFILE.

31

System Messages

Action: Consult product administrator. The User Configuration assigned &3member data needs to beupdated. The user '&2' was assigned a list of &3members but themember '&2' in the list nolonger exist on the PCFILE.

DSS01776 "A &1 '*LIST*' was assigned for user '&2', but there are no members in the list."

Explanation: A&1 '*LIST*' was assigned for user '&2', but there are no members in the list. The UserConfiguration assigned &3member data needs to be updated. The user '&2' has been assigneda list of &3members, but there are no members in the assigned list.

DSS01777 "Unable to connect to new remote host, you are already connected."

Explanation: An attempt was made to pass API requests through to a new host, a connection already exists.

Action: Disconnect first.

DSS01778 "The &4member '&1' was specified and is not one of the assigned &2 &4members in the list for user'&3'."

Explanation: The &4member '&1' was specified and is not one of the assigned &2&4members in the list foruser '&3'.

Action: Correct the &4member name and rerun the product.

DSS01779 "SJL not created because all sections of the SJL are turned off."

Explanation: SJL not created because all sections of the SJL are turned off.

Action: Review the JCL Listing Report options section of your RTS member.

DSS01780 "'&1' is an invalid input statement keyword for product '&2'."

Explanation: Input statement keyword '&1' is only valid for product '&3'.

DSS01781 "'&1' is an INFO/X function and is not compatible with '&2'."

Explanation: '&1' is an INFO/X function and is not compatible with '&2'.

DSS01782 "RTS member &2 was used instead of &1. Your administrator has assigned member &2 to user &3."

Explanation: RTS member &2was used instead of &1. Your administrator has assigned member &2 to user&3.

DSS01783 "Reformatter member &2 was used instead of &1. Your administrator has assigned member &2 to user&3."

Explanation: Reformatter member &2was used instead of &1. Your administrator has assigned member &2to user &3.

DSS01784 "Selection Exit &2 was used instead of &1. Your administrator has assigned Selection Exit &2 to user&3."

Explanation: Selection Exit &2was used instead of &1. Your administrator has assigned Selection Exit &2 touser &3.

DSS01785 "&1 setting PCFile version to &2."

32


Explanation: &1 setting PCFile version to &2.

DSS01786 "No changedmembers found during AIUFCE processing."

Explanation: The AIUFCE process did not find any changed members to process.

DSS01787 "An error occurred while getting the DD '&1' concatenation, rc = &2."

Explanation: An error occurred while getting the DD '&1' concatenation, rc = &2.

DSS01788 "The required input type was not specified for the requested DELETEFROMDATABASE using DDname'&1'."

Explanation: During a DELETEFROMDATABASE request, the required input type was not specified usingDDname '&1'.

DSS01789 "No datasets were found processing the DD '&1' concatenation."

Explanation: No datasets were found processing the DD '&1' concatenation.

DSS01790 "DELETEFROMDATABASE process completed. &1 member(s) deleted."

Explanation: DELETEFROMDATABASE process completed. &1member(s) deleted.

DSS01791 "The &4member '&1' was specified and is not one of the assigned &2 &4members in the list for user'&3'."

Explanation: The &4member '&1' was specified and is not one of the assigned &2&4members in the list foruser '&3'.

Action: Correct the &4member name and rerun the product.

DSS01792 "Dataset &1 has beenmigrated."

Explanation: An attempt was made to process dataset &1 that was migrated. Processing stopped.

DSS01793 "'&1' in dataset '&2' received frommachine '&3'."

Explanation: '&1' in dataset '&2' received from machine '&3'.

DSS01800 "CONTROL-M cannot allocate file '&1'."

Explanation: CONTROL-M cannot allocate file '&1'.

DSS01801 "CONTROL-M cannot initialize."

Explanation: CONTROL-M cannot initialize.

DSS01802 "Unable to load CONTROL-Mmodule '&1'."

Explanation: Unable to load CONTROL-M module '&1'.

DSS01803 "CONTROL-M '&1' op code '&2' return code '&3'."

Explanation: CONTROL-M '&1' op code '&2' return code '&3'.

DSS01804 "CONTROL-M op code '&1' is not valid."

Explanation: CONTROL-M op code '&1' is not valid.

33

System Messages

DSS01805 "CONTROL-M EXIT 2 returned zero addon count."

Explanation: CONTROL-M EXIT 2 returned zero addon count.

DSS01806 "CONTROL-M issued messages."

Explanation: CONTROL-M issued messages.

DSS01807 "CONTROL-M '&1' INIT failed."

Explanation: CONTROL-M '&1' INIT function was called and returned a non-zero return code.

DSS01808 "CONTROL-M detected premature end of member."

Explanation: CONTROL-M detected premature end ofmember.

DSS01809 "CONTROL-M requests that this run be cancelled."

Explanation: CONTROL-M requests that this run be cancelled.

DSS01956 "'&1' entry type '&2' is not valid for ALTER '&3'."

Explanation: '&1' entry type '&2' is not valid for ALTER '&3'.

DSS02000 "Could not find the &1 default &2 member."

Explanation: Could not find the default &2member for the &1 product.

Action: Check the Product Control file. Processing will continue, using the system defaults.

DSS02001 "Incorrect number of parameters were passed to function '&1'. &3 args were expected; &2 args werereceived."

Explanation: Incorrect number of parameters were passed to function '&1'. &3 args were expected; &2 argswere received.

DSS02002 "Unidentified Option Statement: '&1'."

Explanation: Unidentified Option Statement: '&1'.

DSS02003 "ASG product password advisory: &1."

Explanation: ASG product password advisory: &1.

DSS02004 "Could not load alternate Reformatter optionsmember '&1'. Will continue processing using Reformattermember 'DEFAULT'."

Explanation: Could not load alternate Reformatter options member '&1'. Will continue processing usingReformatter member 'DEFAULT'.

DSS02006 "An unexpected DDStmt concatenation was found in the RTS member."

Explanation: An unexpected DD Stmt concatenation was found in the RTS member.

DSS02008 "File '&1.MPL' not found."

Explanation: File '&1.MPL' not found.

34


DSS02009 "JESPROCdataset '&1' not found."

Explanation: JESPROC dataset '&1' not found.

DSS02010 "Unable to find &1 for Reformatter."

Explanation: Unable to find &1 for Reformatter.

DSS02011 "Could not load the &1 default &2 member."

Explanation: Could not load the default &2member for product &1.

Action: Check the product control file. Processing will continue, using system defaults.

DSS02012 "Could not find &1 alternate run optionsmember '&2'."

Explanation: Could not find alternate run options member '&2' for product &1.

DSS02013 "Could not find alternate Reformatter member '&1'."

Explanation: Could not find alternate Reformatter member : &1.

DSS02015 "&1member '&2' is in use."

Explanation: &1member '&2' is in use.

DSS02016 "'&1' is not a valid product name."

Explanation: '&1' is not a valid product name.

DSS02017 "Product password does not pass validation. Reason: &1 &2."

Explanation: The current product password does not pass validation for the following reason: &1&2.

Action: Contact ASG Technologies Customer Support for assistance.

DSS02018 "Product password has expired."

Explanation: Product password has expired.

DSS02019 "Product password not specified. See the System Administrator's Guide for instructions on specifying it."

Explanation: Product password was not specified.

Action: See the topic - Product Password in the System Administrator documentation for instructionson specifying it.

DSS02020 "Could not load &1 alternate run optionsmember '&2'. Processing will continue, using run optiondefaults."

Explanation: Could not load alternate run options member '&2' for product &1. Processing will continue,using run option defaults.

DSS02021 "&1member '&2' contains syntax errors. Member cannot be saved."

Explanation: &1member '&2' contains syntax errors. Member cannot be saved.

DSS02022 "OPTIONmember '&1' not found; PCCOPY ending."

Explanation: OPTIONmember '&1' not found; PCCOPY ending.

35

System Messages

DSS02023 "WARNING - The product password will expire in &1 days. Please contact ASG Technologies CustomerSupport."

Explanation: The product password will expire in '&1' days. PRO/JCL or INFO/XE are the products that maybe installed at your site.


DSS02024 "ERROR - Template name '&1' is already in use."

Explanation: If you want to replace template &1with a new template, please delete the existing template &1first.

DSS02025 "Output library member '&1(&2)' is in use and cannot be written to."

Explanation: Output library member '&1(&2)' is in use and cannot be written to. It is in use by ISPF EDIT oranother utility that uses the SPFEDIT ENQ.

DSS02026 "'&1' was called without access to either a local or a remote PCFILE."

Explanation: '&1' was called without access to either a local or a remote PCFILE.

DSS02027 "Connection to primary PCFILE was lost. Unable to write records to the local PCFILE."

Explanation: Write is not allowed to the local PCFILE, because any data written will be lost when theconnection to the primary PCFILE is reestablished.

DSS02028 "&1 is not licensed for &2. Contact ASG Technologies."

Explanation: &1 is not licensed for &2. Contact ASG Technologies.

DSS02029 "License for &1 does not start until &2."

Explanation: License for &1 does not start until &2.

DSS02030 "License for &1 expired on &2."

Explanation: License for &1 expired on &2.

DSS02031 "No &1 licensing information found for this platform/serial #: &2/&3."

Explanation: No &1 licensing information found for this platform/serial #: &2/&3.

DSS02032 "&1 is not licensed for serial number &2."

Explanation: &1 is not licensed for serial number &2.

DSS02033 "License has been tampered with. Signature does not match."

Explanation: License has been tampered with. Signature does not match.

DSS02034 "Unable to support client. PCFILE API is at version &1 and client is &2."

Explanation: Unable to support client. PCFILE API is at version &1 and client is &2.

DSS02035 "Connection to primary PCFILE was lost. Unable to delete records from the local PCFILE."

Explanation: Connection to primary PCFILE was lost. Unable to delete records from the local PCFILE.

36


DSS02036 "Unable to connect to PCFILE Server. Processing will continue with backup copy. No updating will takeplace."

Explanation: Unable to connect to PCFILE Server. Processing will continue with backup copy. No updatingwill take place.

DSS02037 "The OPTIONMPL in the current PCFILE is version &2. The version being added is &1. Therefore, noupdate will be made."

Explanation: The OPTIONMPL in the current PCFILE is version &2. The version being added is &1. Therefore,no update will bemade.

DSS02040 "The current product password does not permit running '&1'. Please contact ASG Technologies."

Explanation: The current product password does not permit running '&1'.

Action: Contact ASG Technologies for information on how to license this product.

DSS02041 "The connection to primary PCFILE was lost. Switching to the backup PCFILE."

Explanation: The connection to primary PCFILE was lost. Switching to the backup PCFILE.

DSS02042 "Requested template &1 not found in PCFile."

Explanation: Template specified in JMP &1 not found in the PCFile.

DSS02043 "User pressed cancel in response to &1 template / popup dialog."

Explanation: User pressed cancel in response to &1 template / popup dialog.

DSS02044 "Syntax error in mask: '&1'."

Explanation: Syntax error in mask: '&1'.

DSS02045 "ERROR - Profile name '&1' is already in use."

Explanation: If you want to replace profile &1with a new profile, please delete the existing profile &1 first.

DSS02100 "XML Error &4:&1. Expecting an attribute name at offset &2, in object &3."

Explanation: XML Error &4:&1. Expecting an attribute name at offset &2, in object &3.

DSS02101 "XML Error &4:&1. Expecting '=' after attribute name at offset &2, in object &3."

Explanation: XML Error &4:&1. Expecting '=' after attribute name at offset &2, in object &3.

DSS02102 "XML Error &4:&1. Expecting value for attribute at offset &2, in object &3."

Explanation: XML Error &4:&1. Expecting value for attribute at offset &2, in object &3.

DSS02103 "XML Error &4&1. Missing Tag Name after '<' at offset &2, in object &3."

Explanation: XML Error &4&1. Missing Tag Name after '<' at offset &2, in object &3.

DSS02104 "XML Error &4:&1. Missing closing '>' after '/' at offset &2, in object &3."

Explanation: XML Error &4:&1. Missing closing '>' after '/' at offset &2, in object &3.

37

System Messages

DSS02105 "XML Parsing Error. Missing closing '>' at offset &1, in object &2."

Explanation: XML Parsing Error. Missing closing '>' at offset &1, in object &2.

DSS02106 "XML Parsing Error. Missing closing tag at offset &1, in object &2."

Explanation: XML Parsing Error. Missing closing tag at offset &1, in object &2.

DSS02107 "XML Parsing Error. Missing '/' on what is supposed to be the close tag at offset &1, in object &2."

Explanation: XML Parsing Error. Missing '/' on what is supposed to be the close tag at offset &1, in object&2.

DSS02108 "XML Parsing Error. Cannot find closing tag in object &1."

Explanation: XML Parsing Error. Cannot find closing tag in object &1.

DSS02109 "XML Error &4:&1. Was expecting tag name after </ offset &2, in object &3."

Explanation: XML Error &4:&1. Was expecting tag name after </ offset &2, in object &3.

DSS02110 "XML Error &4:&1. Found an end tag with no opening tag at offset &2, in object &3."

Explanation: XML Error &4:&1. Found an end tag with no opening tag at offset &2, in object &3.

DSS02111 "XML Error &4:&1. End tag &2 does not match opening tag &3."

Explanation: XML Error &4:&1. End tag &2 does not match opening tag &3.

DSS02112 "XML Error &4:&1. Missing closing quote at offset &2 in &3."

Explanation: XML Error &4:&1. Missing closing quote at offset &2 in &3.

DSS02113 "XML Error &4:&1. Expecting XML tag '&2', but received '&3'."

Explanation: XML Error &4:&1. Expecting XML tag '&2', but received '&3'.

DSS02114 "Failed to find XML attribute '&1' in '&2'."

Explanation: Failed to find XML attribute '&1' in '&2'.

DSS03000 "Not enough parameters. Function '&1' expects &2 parameters."

Explanation: Not enough parameters. Function '&1' expects &2 parameters.

DSS03001 "Statement number &1 not found. Requested number possibly out of range."

Explanation: Statement number &1 not found. Requested number possibly out of range.

DSS03002 "Handle is not valid. Function '&1' expects parameter number &2 to be a valid statement handle."

Explanation: Handle is not valid. Function '&1' expects parameter number &2 to be a valid statementhandle.

DSS03003 "Handle is not valid. Function '&1' expects parameter number &2 to be a valid parm handle."

Explanation: Handle is not valid. Function '&1' expects parameter number &2 to be a valid parm handle.

DSS03004 "Handle is not valid. Function '&1' expects parameter number &2 to be a valid record handle."

38


Explanation: Handle is not valid. Function '&1' expects parameter number &2 to be a valid record handle.

DSS03005 "Handle is not valid. Function '&1' expects parameter number &2 to be a valid SQL query handle."

Explanation: Handle is not valid. Function '&1' expects parameter number &2 to be a valid SQL query handle.

DSS03006 "Parameter is not valid. Function '&1', parameter number &2."

Explanation: Parameter is not valid. Function '&1', parameter number &2.

DSS03007 "Handle is not valid. Function '&1' expects parameter number &2 to be a valid File handle."

Explanation: Handle is not valid. Function '&1' expects parameter number &2 to be a valid File handle.

DSS03008 "Function '&1' cannot find requested parm '&2'."

Explanation: Function '&1' cannot find requested parm '&2'.

DSS03009 "IDCAMS '&1' statement found. Reformatting will stop here."

Explanation: PRO/JCL will not reformat IDCAMS control cards after a '&1' statement is encountered.

DSS03010 "Function '&1' ended with return code &2."

Explanation: Function '&1' ended with return code &2.

DSS03011 "Handle is not valid. Function '&1' expects parameter number &2 to be a valid &3 statement handle."

Explanation: Handle is not valid. Function '&1' expects parameter number &2 to be a valid &3 statementhandle.

DSS03012 "Record number &1 not found. Requested number possibly out of range."

Explanation: Record number &1 not found. Requested number possibly out of range.

DSS03013 "Handle is not valid. Function '&1' expects parameter number &2 to be a valid keyword parm handle."

Explanation: Handle is not valid. Function '&1' expects parameter number &2 to be a valid keyword parmhandle.

DSS03014 "Handle is not valid. Function '&1' expects parameter number &2 to be a valid value parm handle."

Explanation: Handle is not valid. Function '&1' expects parameter number &2 to be a valid value parmhandle.

DSS03015 "Cannot retrieve the value of &1, because of symbolic usage."

Explanation: Cannot retrieve the value of &1, because of symbolic usage.

DSS03016 "Cannot change the value of '&1' to '&2', because of syntax errors."

Explanation: Cannot change the value of '&1' to '&2', because of syntax errors.

DSS03017 "Cannot change the value of '&1' to '&2', because of symbolic usage."

Explanation: Cannot change the value of '&1' to '&2', because of symbolic usage.

DSS03018 "In JMP Function '&1', error message '&2' is outside of user message range &3."

39

System Messages

Explanation: In JMP Function '&1', error message '&2' is outside of user message range &3.

DSS03019 "Unable to reformat statement because value '&1' won't fit on one line."

Explanation: Unable to reformat statement because value '&1' won't fit on one line.

DSS03020 "Unable to reformat statement because of syntax error in '&1' '&2'."

Explanation: Unable to reformat statement because of syntax error in '&1' '&2'.

DSS03021 "Unable to reformat parm."

Explanation: Currently, PRO/JCL does not support reformatting '&1' parms.

DSS03022 "File '&1(&2)' changed, but no output file was specified. Needed to update &3 records."

Explanation: File '&1(&2)' changed, but no output file was specified. Needed to update &3 records.

DSS03023 "Unrecognized Effective Value Name '&1'."

Explanation: Unrecognized Effective Value Name '&1'.

DSS03024 "Unable to reformat statement because comment does not fit."

Explanation: Unable to reformat statement because comment does not fit.

DSS03025 "Unable to reformat statement because not all the records came from the same place."

Explanation: Unable to reformat statement because not all the records came from the same place.

DSS03026 "Unable to reformat statement because the statement contains a generated record."

Explanation: Unable to reformat statement because the statement contains a generated record.

DSS03027 "Control card number '&1' not found. No error added."

Explanation: Error was supposed to be added to control card '&1', but '&2' control cards were found.

DSS03028 "Message is now 10301."

Explanation: Message is now 10301.

DSS03029 "Cannot reformat statement due to current statement construction."

Explanation: Cannot reformat statement due to current statement construction. This is usually due tosymbolics containing syntax characters like ',' or '('

DSS03030 "Cannot reformat. Missing keyword."

Explanation: This TSO/IDCAMS statement contains a keyword parameter without a keyword.

DSS03031 "Unable to reformat, because the continuation marker does not fit."

Explanation: Unable to reformat, because the continuation marker does not fit.

DSS03032 "JJ cannot reformat records longer than 80 characters."

Explanation: JJ cannot reformat records longer than 80 characters.

DSS03033 "PRO/JCL does not support reformatting statements with this style of comments."

40


Explanation: PRO/JCL does not support reformatting statements with this style of embedded comments.

DSS03034 "The 3rd parameter passed to JMPAddError was supposed to be a severity. Found '&1'."

Explanation: The 3rd parameter passed to JMPAddError was supposed to be a severity number. Found '&1'.

DSS03035 "User message severity '&1' is not valid. User message severity must be between 0 and &2."

Explanation: User message severity '&1' is not valid. User message severity must be between 0 and &2.

DSS03036 "The parm type for '&1' is not supported by JMP."

Explanation: The parm type for '&1' is not supported by JMP.

DSS03037 "Processing terminated by JMP program: &1."

Explanation: PRO/JCL processing was terminated by the JMP program '&1'.

Action: Refer to the JMP program to determine the reason for the termination.

DSS03038 "Processing terminated prematurely due to return code '&1'. Contact ASG Technologies CustomerSupport."

Explanation: &2 processing was prematurely terminated due to a return code of '&1'. This message isindicative of an internal problem encountered by &2.

Action: Contact ASG Technologies Customer Support for assistance.

DSS03039 "PRO/JCL does not reformat lines ending with symbolic resolving to zero length values."

Explanation: PRO/JCL does not reformat statements with lines ending in symbolic resolving to zero lengthvalues. Reformatting this type of statement could change its meaning or even introduce JCLerrors.

DSS03040 "JMPgetNthRecordFromDD is available only for JCL-DD statements."

Explanation: JMPgetNthRecordFromDD is available only for JCL-DD statements.

DSS03041 "Because of syntax error of severity &1, changes for &2 were not written to the output dataset."

Explanation: Because of syntax error of severity &1, changes for &2were not written to the output dataset.

DSS03042 "Unable to reformat, because another statement is embedded in this one."

Explanation: Unable to reformat, because another statement is embedded in this one. Probably a schedulercontrol statement.

DSS03043 "Unable to reformat, because this statement wasmodified by a selection exit."

Explanation: Unable to reformat, because this statement was modified by a selection exit.

DSS03044 "JMPaddKeywordParm failed because parm '&1' already exists."

Explanation: JMPaddKeywordParm failed because parm '&1' already exists.

DSS03046 "JMP function not performed because there was a JCL error in the edit work area."

41

System Messages

Explanation: The JMP function was not performed because it would require reformatting the JCL, the optionReformat w/Errors=Nwas specified, and an error was found in the JCL.

DSS03047 "JMP cannot insert or delete records in the edit work area when LRECL > 80."

Explanation: The JMP function was not performed because it would require modifying the edit work area ofa dataset whose LRECL is greater than 80.

DSS03048 "PRO/JCL does not reformat symbolics resolving to comments."

Explanation: PRO/JCL does not reformat statements with symbolics resolving to comments. Reformattingthis type of statement could change its meaning or even introduce JCL errors.

DSS03049 "Unable to fulfill request to change parameter order due to keywords or commaswithin symbolic values."

Explanation: Unable to fulfill request to change parameter order due to keywords or commas withinsymbolic values. In such cases, changing the order could result in JCL errors.

DSS03050 "Output file name &1 was greater than 44 characters. Last node, &2 truncated."

Explanation: Output file name&1was greater than 44 characters. Last node, &2 truncated.

DSS03051 "JMPsetPosValue failed because parmID '&1' is not of the form n, n.n, keyword.n or keyword.n.n."

Explanation: JMPsetPosValue failed because parmID '&1' is not of the form n, n.n, keyword.n orkeyword.n.n.

DSS03052 "PRO/JCL does not reformat symbolics resolving to values with leading blanks."

Explanation: PRO/JCL does not reformat statements with continuation lines that begin with symbolicsresolving to values with leading blanks. Reformatting this type of statement could change itsmeaning or even introduce JCL errors.

DSS03053 "Comment was truncated because length is greater than 69 characters."

Explanation: Comment was truncated because comment length + //* is greater than 72.

DSS03055 "Parm &1 not changed because it is effected by symbolics. &2."

Explanation: Parm &1 not changed because it is effected by symbolics. &2.

DSS03056 "Option '&1' not understood. Should be '&2'."

Explanation: Option '&1' not understood. Should be '&2'.

DSS03057 "Record not changed because data would be truncated."

Explanation: Record not changed because data would be truncated.

DSS03058 "Null file '&1' was written to &2 becauseWRITE=ALL was specified."

Explanation: File '&1' has no records, but was written to &2 becauseWRITE=ALL was specified on theOUTPUT stmt.

DSS04001 "&1 is running with LE/370 release &2; requires release &3 or later."

Explanation: &1 is running with LE/370 release &2; requires release &3 or later.

42


DSS04003 "Member '&1' successfully added to the product control file."

Explanation: Member '&1' successfully added to the product control file.

DSS04004 "An error occurred trying to add member '&1' to the product control file."

Explanation: An error occurred trying to add member '&1' to the product control file.


DSS04005 "Open failed for '&1'; RECFM for OUTFILE must be VB."

Explanation: Open failed for '&1'; RECFM for OUTFILE must be VB.

DSS04006 "The product is at release level '&1', but that release was not found in the product control file (PCFILE)."

Explanation: The PCFILE members required for release level '&1'were not found in the PCFILE. This could bebecause the installation of that release was not completed successfully, or because you areusing the wrong PCFILE.

DSS05003 "Non-zero return code returned bymodule '&1' in API call '&2'. Return code =&3."

Explanation: Non-zero return code returned by module '&1' in API call '&2'. Return code = &3.

DSS05020 "INVALIDPARAMETER: &1 IGNORED."

Explanation: INVALID PARAMETER: &1 IGNORED.

DSS05021 "INVALIDPARAMETER: &1 - PROCESSING TERMINATED."

Explanation: Invalid Parameter: &1 - Processing Terminated.

DSS05022 "STC ID =&1."

Explanation: STC ID = &1.

DSS05023 "OBSOLETE PARAMETERMAXUSERS IGNORED."

Explanation: Obsolete parameter MAXUSERS ignored.

DSS05024 "INITIAL PROCESSORTASKS =&1."

Explanation: Initial Processor Tasks = &1.

DSS05025 "MAXIMUMNUMBEROF PROCESSORTASKS =&1."

Explanation: MAXIMUM NUMBER OF PROCESSOR TASKS = &1.

DSS05026 "STARTEDTASK AT LEVEL &1 - &2."

Explanation: STARTED TASK AT LEVEL &1 - &2.

DSS05028 "TCP/IP Listener at port &1 on started task &2 failed to start."

Explanation: TCP/IP Listener at port &1 on started task &2 failed to start.

DSS05029 "TCP/IP Listener restart attempt &1 of &2 on port &3; started task &4."

Explanation: TCP/IP Listener restart attempt &1 of &2 on port &3; started task &4.

43

System Messages

DSS05027 "Started Task stopping because of listener failure. See SYSPRINT."

Explanation: Started Task stopping because of listener failure.

Action: See SYSPRINT.

DSS05037 "SAF option is INVALID or does NOT EXIST in Configuration File - Processing defaults to SAF=ON."

Explanation: PRO/JCL processing defaults to SAF="ON" when there is no configuration text or configurationtext does not have SAF option specified or the specified SAF is not ON/OFF/USER or SAF="". Fordetailed explanation, see the topic - Customizing the Security Interface in the SystemAdministrator documentation for programming considerations.

DSS05100 "Unable to synchronize PCFILE. Primary PCFILE is &1; secondary PCFILE is &2."

Explanation: Unable to synchronize PCFILE due to version incompatibility. Primary PCFILE is &1; secondaryPCFILE is &2.

DSS05101 "Unable to synchronize PCFILE. SYSTEM record not found in primary PCFILE."

Explanation: Unable to synchronize PCFILE. SYSTEM record not found in primary PCFILE.

DSS05103 "Unable to do PCFILE &1. Remote PCFileManager invoked instead of local PCFileManager."

Explanation: Unable to do PCFILE &1. Remote PCFileManager invoked instead of local PCFileManager.

DSS05104 "TCP/IP client not active. Unable synchronize with remote PCFILE."

Explanation: TCP/IP client not active. Unable synchronize with remote PCFILE.

DSS05105 "Unable to synchronize PCFILEs. DSSIAPI PCFsync returned 'not found'."

Explanation: Unable to synchronize PCFILEs. DSSIAPI PCFsync returned 'not found'.

DSS05106 "Unable to synchronize PCFILEs. DSSIAPI PCFsync returned unrecognized status '&1'."

Explanation: Unable to synchronize PCFILEs. DSSIAPI PCFsync returned unrecognized status '&1'.

DSS05107 "PCFILE sync started at &1 &2."

Explanation: PCFILE sync started at &1&2.

DSS05108 "PCFILE sync ended at &1 &2."

Explanation: PCFILE sync ended at &1&2.

DSS05109 "PCFILE sync sync'd &1 records."

Explanation: PCFILE sync sync'd &1 records.

DSS05110 "DJ0CSYNC requires a server address."

Explanation: DJ0CSYNC requires a server address.

DSS05111 "PCFILE sync ended with return code =&1."

Explanation: PCFILE sync ended with return code = &1.

44


DSS05112 "Unable to synchronize PCFILEs. Client is at release '&1' but server PCFILE does not contain thatrelease."

Explanation: Unable to synchronize PCFILEs. Client is at release '&1' but server PCFILE does not contain thatrelease.

DSS05113 "Synchronizing &1 with &2."

Explanation: Synchronizing &1with &2.

DSS05204 "DJ0YATTWAS PASSEDA BADPCB ADDRESS."

Explanation: DJ0YATTWAS PASSED A BAD PCB ADDRESS.

DSS05500 "Type name '&1' is not defined in INFO/X table IXT_TEM_TYPE."

Explanation: Type name '&1' is not defined in INFO/X table IXT_TEM_TYPE.

DSS05501 "This select expected to return 1 row. However it returned &1 rows. &2."

Explanation: This select expected to return 1 row. However it returned &1 rows. &2.

DSS05502 "Required attribute '&1' is missing from tag &2."

Explanation: Required attribute '&1' is missing from tag &2.

DSS05503 "Missing type on location name. Found '&1', format is 'name:type'."

Explanation: Missing type on location name. Found '&1', format is 'name:type'.

DSS05504 "Cannot find '&1' of type '&2' in location string."

Explanation: Cannot find '&1' of type '&2' in location string.

DSS05505 "Input file &1 did not contain valid XML."

Explanation: Input file &1 did not contain valid XML.

DSS05506 "Criteria missing for &1. Either loc=, type=, or mask=must be coded."

Explanation: Criteria missing for &1. Either loc=, type=, or mask=must be coded.

DSS05507 "Namesmay not contain imbedded quotes: &1."

Explanation: Names may not contain imbedded quotes: &1.

DSS05508 "The SQL error above was encountered during AIU processing. Processing terminated."

Explanation: During AIU processing, the SQL error above was encountered and processing was terminated.

DSS05509 "The CEEDUMP generated for the SQL error below is intentional. Please contact ASG Technologiescustomer support with the CEEDUMP immediately."

Explanation: The CEEDUMP generated for the SQL error below is intentional.

Action: Contact ASG Technologies customer support with the CEEDUMP immediately.

45

System Messages

DSS05510 "Attempted to fetch node num for node '&1' without a database connection. Please contact ASGTechnologies customer support about this issue."

Explanation: An attempt was made to fetch the node num for node '&1' without an existing databaseconnection.


DSS06001 "Function '&1' requires at least &2 parameter(s). &3 were passed."

Explanation: Function '&1' requires at least &2 parameter(s). &3were passed.

DSS06002 "DSSIAPI function '&1' is not valid."

Explanation: DSSIAPI function '&1' is not valid.

DSS06003 "&1member '&2' already exists."

Explanation: &1member '&2' already exists.

DSS06004 "&1member name '&2' is not valid."

Explanation: &1member name '&2' is not valid.

DSS06005 "The value should be '&1'."

Explanation: The value should be '&1'.

DSS06006 "Member '&1' could not be created."

Explanation: Member '&1' could not be created.

DSS06007 "Cannot edit RTS member '&1'; it is already being edited."

Explanation: Cannot edit RTS member '&1'; it is already being edited.

DSS06008 "DSSIAPI function '&1' must be called before function '&2'."

Explanation: DSSIAPI function '&1' must be called before function '&2'.

DSS06009 "Error message '&1' is outside of user message range &2."

Explanation: Error message '&1' is outside of user message range &2.

DSS06010 "DJ0YISPF is at level &1 but started task is at level &2."

Explanation: The REXX USER Function Package, DJ0YISPF, is at level &1 but started task is at level &2.

DSS06011 "Parentheses are not allowed in this usage of a dataset name."

Explanation: Parentheses are not allowed in this usage of a dataset name.

DSS06012 "The specified start row of '&1' is invalid. The start rowmust be at least 1."

Explanation: The specified start row of '&1' is invalid. The start row parameter indicates at which row to fetchdata returned by a SQL query. The start rowmust be at least 1 and cannot exceed the numberof rows in the result set.

46


DSS06013 "The INPUT statement designated to use input from the runMemAddInput API call. However, there wasno input provided."

Explanation: The INPUT statement designated to use input from the runMemAddInput API call. However,there was no input provided. The probable cause is that runMemAddInput call was not made.

DSS06014 "Unknown dataset type '&1', expecting 'PDS', 'PAN', or 'LIB'."

Explanation: Unknown dataset type '&1', expecting 'PDS', 'PAN', or 'LIB'.

DSS06015 "Function '&1' is limited to &2 parameter(s). &3 were passed."

Explanation: Function '&1' is limited to &2 parameter(s). &3were passed.

DSS06016 "User requested &1 capabilities to the PCFILE but the file is in &2mode."

Explanation: User requested &1 capabilities to the PCFILE but the file is in &2mode.

DSS06017 "Attempt to SEND file &1 to &2 failed. See next error message."

Explanation: Attempt to SEND file &1 to &2 failed. See next error message.

DSS06100 "The password for userid &1 will expire in &2 days."

Explanation: The password for the specified userid will expire in the specified days.

DSS06101 "The password for userid &1 has expired."

Explanation: The user must change the password as this password has expired and is not valid.

DSS06102 "Invalid Password specified for PSWGetStatus call."

Explanation: The password specified was not valid for the designated userid.

DSS06103 "Invalid Userid &1 specified for PSWGetStatus call."

Explanation: The userid specified was not a valid system userid.

DSS06104 "The RACROUTE macro failed for PSWGetStatus or PSWChangePassword."

Explanation: The RACROUTEmacro failed for PSWGetStatus or PSWChangePassword.

Action: See themessage log for the error that occurred.

DSS06105 "Userid and Password are valid, password does not expire."

Explanation: The system administrator has set up this password so that it does not expire.

DSS06106 "Access has been revoked for userid &1."

Explanation: The userid is no longer valid because access has been revoked by the system administrator.

DSS06110 "The password for userid &1 was successfully changed."

Explanation: The PSWChangePassword function completed successfully.

DSS06111 "The old password was invalid for the PSWChangePassword call."

Explanation: The old password must be the current password.

47

System Messages

DSS06112 "The new password was invalid for the PSWChangePassword call."

Explanation: The new password does not conform the password rules, or is invalid because it has been usedalready.

DSS06120 "Invalid parameter passed to DJ0YPSW."

Explanation: The PSWGetStatus or PSWChangePassword function call invoke DJ0YPSWwith an invalidaction parameter.

DSS06121 "Function &1 is not implemented on this platform."

Explanation: Function &1 is not implemented on this platform.

DSS06122 "The server returned XML tag &1. Which is not understood."

Explanation: The server returned XML tag &1. Which is not understood. This could be caused by an internalerror or the Server and Client are not compatible.

DSS06123 "Source &1: Server returned an ill formed XML packet. Missing Tag name."

Explanation: Source &1: Server returned an ill formed XML packet. Missing Tag name.

DSS06125 "Invalid password for userid &1."

Explanation: A TCP/IP connection was attempted, the userid is valid but the password is not correct.

DSS06126 "Invalid userid &1 specified."

Explanation: A TCP/IP connection was attempted with an invalid userid.

DSS06127 "Access for userid &1 has been revoked."

Explanation: A TCP/IP connection was attempted with a userid whose access has been revoked.

DSS06128 "EPASS &2 could not be decrypted on this machine, &1. It was generated for another user or on adifferent machine."

Explanation: EPASS &2 could not be decrypted on this machine, &1. It was generated for another user or ona different machine.

DSS06129 "Using EPASS frommachine &1; userid &2."

Explanation: Using EPASS from machine &1; userid &2.

DSS06130 "EPASS &1 contains invalid characters."

Explanation: EPASS &1 contains invalid characters.

DSS06131 "EPASS &1 has an internal formatting error."

Explanation: EPASS &1 has an internal formatting error.

DSS06140 "The &1 '&2' from '&3' &4 been deleted from the INFO/X Repository."

Explanation: The &1 '&2' from '&3' &4 been deleted from the INFO/X Repository.

DSS06141 "Host Name &1 resolves to multiple IP Addresses. Attempting to connect to &2."

48


Explanation: Host Name&1 resolves to multiple IP Addresses. Attempting to connect to &2.

DSS06142 "The &1 '&2' &3 been deleted from the INFO/X Repository."

Explanation: The &1 '&2' &3 been deleted from the INFO/X Repository.

DSS06143 "The '&1' API is obsolete. Please use the '&2' API instead."

Explanation: The '&1' API will be removed from PRO/JCL. Please change your code to use the '&2' APIinstead.

DSS06450 "Attempt to connect to a different database failed: GsqlMsg : '&1', RC='&2'."

Explanation: Attempt to connect to a different database in db_connect_reset() failed: GsqlMsg : '&1',RC='&2'.

DSS06451 "Attempt to connect to the database failed: Database : '&1', RC='&2'."

Explanation: Attempt to connect to the database in db_connect() failed: Database : '&1', RC='&2'.

DSS06452 "Attempt to commit the database failed: RC='&1'."

Explanation: Attempt to commit the database in db_commit() failed: RC='&1'.

DSS06453 "Attempt to rollback the database failed: RC='&1'."

Explanation: Attempt to rollback the database in db_rollback() failed: RC='&1'.

DSS06455 "Attempt to insert a record into the IXTDISCOVER table failed: RC='&1'."

Explanation: Attempt to insert a record into the IXTDISCOVER table in db_insert_dicover_record() failed:RC='&1'.

DSS06456 "Attempt to insert a record into the IXTSUBNET table failed: RC='&1'."

Explanation: Attempt to insert a record into the IXTSUBNET table in db_insert_subnet() failed: RC='&1'.

DSS06457 "Attempt to get the highwatermark for '&1' from the IXTHWM table failed: RC='&2'."

Explanation: Attempt to get the highwatermark for '&1' from the IXTHWM table in db_get_hwm() failed:RC='&2'.

DSS06458 "Attempt to get the hardware inventory for '&1' from the IXTHWINV table failed: RC='&2'."

Explanation: Attempt to get the hardware inventory for '&1' from the IXTHWINV table in db_get_hwinv()failed: RC='&2'.

DSS06459 "Attempt to get the software inventory for '&1' from the IXTSWINV table failed: RC='&2'."

Explanation: Attempt to get the software inventory for '&1' from the IXTSWINV table in db_get_swinv()failed: RC='&2'.

DSS06460 "Attempt to get the list of IP subnets from the IXTSUBNET table failed: RC='&1'."

Explanation: Attempt to get the list of IP subnets in function db_get_subnet_list() from the IXTSUBNET tablefailed: RC='&1'.

49

System Messages

DSS06461 "Attempt to get all managed on IP subnet '&1' from the IXTPLAT table failed: RC='&2'."

Explanation: Attempt to get all managed on IP subnet '&1' from the IXTPLAT table in db_get_managed_list()failed: RC='&2'.

DSS06462 "Attempt to get all unmanaged on IP subnet '&1' from the IXTDISCOVER table failed: RC='&2'."

Explanation: Attempt to get all unmanaged on IP subnet '&1' from the IXTDISCOVER table in db_get_unmanaged_list() failed: RC='&2'.

DSS06463 "Attempt to enter the hardware inventory for '&1' into the IXTHWINV table failed: RC='&2'."

Explanation: Attempt to enter the hardware inventory for '&1' into the IXTHWINV table in db_insert_hwinv()failed: RC='&2'.

DSS06464 "Attempt to enter the software inventory for '&1' into the IXTSWINV table failed: RC='&2'."

Explanation: Attempt to enter the software inventory for '&1' into the IXTSWINV table in db_insert_swinv()failed: RC='&2'.

DSS06465 "Attempt to add the IP subnet lightweight agent manager '&1' failed: RC='&2'."

Explanation: Attempt to add the IP subnet lightweight agent manager in db_add_slam() '&1' failed: RC='&2'.

DSS06466 "Attempt to add the lightweight agent '&1' failed: RC='&2'."

Explanation: Attempt to add the lightweight agent '&1' in db_add_la() failed: RC='&2'.

DSS06467 "Attempt to remove the lightweight agent '&1' failed: RC='&2'."

Explanation: Attempt to remove the lightweight agent '&1' in db_remove_la() failed: RC='&2'.

DSS06468 "Attempt to change the SLAM from '&1' to '&2' failed: RC='&3'."

Explanation: Attempt to change the SLAM from '&1' to '&2' in db_change_slam() failed: RC='&3'.

DSS06469 "Attempt to get information for '&1' from the IXTPLAT table failed: RC='&2'."

Explanation: Attempt to get information for '&1' from the IXTPLAT table in db_get_sam_info() failed:RC='&2'.

DSS06470 "Attempt to get filtered slams on IP subnet '&1' from the IXTPLAT table failed: RC='&2'."

Explanation: Attempt to get filtered slams on IP subnet '&1' from the IXTPLAT table in db_get_filtered_slam()failed: RC='&2'.

DSS06471 "Attempt to get filtered las on IP subnet '&1' from the IXTPLAT table failed: RC='&2'."

Explanation: Attempt to get filtered las on IP subnet '&1' from the IXTPLAT table in db_get_filtered_la()failed: RC='&2'.

DSS06472 "Attempt to get slam (& las) w/ IP address '&1' from the IXTPLAT table failed: RC='&2'."

Explanation: Attempt to get slam (& las) w/ IP address '&1' from the IXTPLAT table in db_get_slam_la() failed:RC='&2'.

50


DSS06473 "Parm IDs are not currently supported on IF statements, please remove the Parm ID to return thecomplete IF statement."

Explanation: Parm IDs are not currently supported on IF statements.

Action: Remove the Parm ID to return the complete IF statement.

DSS06474 "Client &1 sent contoken '&2' which does not match server contoken '&3'. Connection rejected."

Explanation: Client &1 sent contoken '&2' which does not match server contoken '&3'. Connection rejected.

DSS06475 "contoken '&1' on client &2 was rejected by server &3. Connection rejected."

Explanation: contoken '&1' on client &2was rejected by server &3. Connection rejected.

DSS06476 "Client &1 specified contoken '&2' but the server does not have a contoken. Connection rejected."

Explanation: Client &1 specified contoken '&2' but the server does not have a contoken. Connectionrejected.

DSS06477 "Client &1 did not specify a contoken and the server requires one. Connection rejected."

Explanation: Client &1 did not specify a contoken and the server requires one. Connection rejected.

DSS06479 "Client &1 attempted access &2 to Server &3. Access was not allowed by config file restrict definition."

Explanation: Client &1 attempted access &2 to Server &3. Access was not allowed by config file restrictdefinition.

DSS06480 "'&1' is not supported on '&2' statements."

Explanation: The '&1' API should not be used on '&2' statements.

DSS06481 "DSN '&1' was not found in the INFO/X repository."

Explanation: DSN '&1' was not found in the INFO/X repository.

DSS06482 "Database not updated because UPDATEDATABASE not specified."

Explanation: Database not updated because UPDATEDATABASE not specified.

DSS06483 "&1 entries were written to outfile '&2'."

Explanation: &1 entries were written to outfile '&2'.

DSS06501 "TCP/IP Error: Reason : '&1', RC='&2'."

Explanation: TCP/IP Error: Unknown error occurred.

Action: Check the return code.

DSS06502 "TCP/IP Error: Client port number changed from '&1' to '&2'. Error handing off socket from listener toserver."

Explanation: TCP/IP Error: Client port number changed from '&1' to '&2'. Error handing off socket fromlistener to server.

DSS06503 "TCP/IP Error: An invalid host name or a host address specified : '&1'."

51

System Messages

Explanation: The call to the function gethostbyname return with error.

DSS06504 "Invalid host name '&1' specified. This host name is not resolvable on this machine."

Explanation: The host name '&1' specified is not a valid host name on this machine.

DSS06505 "TCP/IP Error: A socket open operation failed, Reason : '&1', RC = '&2'."

Explanation: Could not open the socket for communication.

DSS06506 "TCP/IP givesocket failed, Reason : '&1', RC = '&2'."

Explanation: Could not givesocket.

DSS06507 "TCP/IP Error: A connect attempt to remote host '&1' on Port no: '&2' failed, Reason: '&3', RC='&4'."

Explanation: A socket connection could not bemadewith remote host '&1' on port '&2'.

Action: Make sure a server is properly configured on host '&1'.

DSS06508 "The hostname of this machine could not be retrieved. gethostname() returned '&1'."

Explanation: The hostname of this machine could not be retrieved for some unknown reason.

Action: Contact your network administrator for more information on possible causes.

DSS06509 "TCP/IP Error: Error occurred while reading from socket, Reason: '&1', RC='&2'."

Explanation: TCP/IP Error: Error occurred while reading from socket.

DSS06511 "TCP/IP Error: An invalid service name specified : '&1'."

Explanation: TCP/IP Error: An invalid service name specified or service namewas not configured inetc/services or windows/services file. Call to getservbyname return with error, which requiresto locate Port Number.

DSS06513 "TCP/IP Error: An invalid or no service name specified."

Explanation: TCP/IP Error: An invalid service name specified or service namewas not configured inetc/services or windows/services file. Call to getservbyname return with error, which requiresto locate Port Number.

DSS06515 "TCP/IP Error: Error occurred while writing to socket, Reason: '&1', RC='&2'."

Explanation: TCP/IP Error: Error occurred while writing to socket.

DSS06517 "TCP/IP Error: accept connection request from remote client fail, Reason : '&1', RC='&2'."

Explanation: TCP/IP Error: accept system call fail.

DSS06518 "Invalid parameter &1. Remote PCFILE IP addressmust specify either an IP address or host name."

Explanation: Invalid parameter &1. Remote PCFILE IP address must specify either an IP address or hostname.

DSS06519 "TCP/IP Error: could not bind to local IP address &1 with port &2, Reason : '&3', RC='&4'."

Explanation: TCP/IP Error: could not bind to local IP address.

52


DSS06520 "Remote PCFILE port number specified but no Remote PCFILE IP address or host name wasspecified."

Explanation: Remote PCFILE port number specified but no Remote PCFILE IP address or host namewasspecified.

DSS06521 "TCP/IP Error: could not start listen service, Reason : '&1', RC='&2'."

Explanation: TCP/IP Error: could not start listen service.

DSS06523 "TCP/IP Error: socket read request timeout, The timeout parameter was '&1' seconds."

Explanation: TCP/IP Error: socket read request timeout.

DSS06525 "TCP/IP Error: socket write request timeout, The timeout parameter was '&1' seconds."

Explanation: TCP/IP Error: socket write request timeout.

DSS06526 "TCP/IP Error: Error occurred while getting socket flags, Reason: '&1', RC='&2'."

Explanation: TCP/IP Error: Error occurred while getting socket flags.

DSS06527 "TCP/IP Error: Error occurred while setting socket blocking flag, Reason: '&1', RC='&2'."

Explanation: TCP/IP Error: Error occurred while setting socket blocking flag.

DSS06528 "TCP/IP Error: Error occurred while setting socket non-blocking flag, Reason: '&1', RC='&2'."

Explanation: TCP/IP Error: Error occurred while setting socket non-blocking flag.

DSS06529 "TCP/IP Error: &1 detected an error while checking timeout value while connected to &2, Reason: '&3',RC='&4'."

Explanation: TCP/IP Error: &1 detected an error while checking timeout value while connected to &2,Reason: '&3', RC='&4'.

DSS06530 "TCP/IP Error: Error occurred while calling select before a non-blocking read, Reason: '&1', RC='&2'."

Explanation: TCP/IP Error: Error occurred while calling select before a non-blocking read.

DSS06531 "TCP/IP Error: Error occurred while checking the socket read flag after calling select, Reason: '&1',RC='&2'."

Explanation: TCP/IP Error: Error occurred while checking the socket read flag after calling select.

DSS06532 "Destructor on GSSTalkSocket was called with an open socket. Shutting down socket before destroyingthe object."

Explanation: Destructor on GSSTalkSocket was called with an open socket. Shutting down socket beforedestroying the object.

DSS06535 "TCP/IP Error: Error occurred while reading socket header, Reason: '&1', RC='&2'."

Explanation: TCP/IP Error: Error occurred while reading socket header.

53

System Messages

DSS06536 "TCP/IP Error: Error occurred after reading socket header: too many bytes read, Reason: '&1',RC='&2'."

Explanation: TCP/IP Error: Error occurred after reading socket header: too many bytes read.

DSS06537 "TCP/IP Error: Error occurred while reading socket packet, Reason: '&1', RC='&2'."

Explanation: TCP/IP Error: Error occurred while reading socket packet.

DSS06538 "TCP/IP Error: Error occurred after reading socket packet: too many bytes read, Reason: '&1',RC='&2'."

Explanation: TCP/IP Error: Error occurred after reading socket packet: too many bytes read.

DSS06540 "TCP/IP Error: Error occurred while calling select before a non-blocking write, Reason: '&1', RC='&2'."

Explanation: TCP/IP Error: Error occurred while calling select before a non-blocking write.

DSS06541 "TCP/IP Error: Error occurred while checking the socket write flag after calling select, Reason: '&1',RC='&2'."

Explanation: TCP/IP Error: Error occurred while checking the socket write flag after calling select.

DSS06545 "TCP/IP Error: Error occurred while writing to socket, Reason: '&1', RC='&2'."

Explanation: TCP/IP Error: Error occurred while writing to socket.

DSS06546 "TCP/IP Error: Error occurred after writing to socket: too many bytes written, Reason: '&1', RC='&2'."

Explanation: TCP/IP Error: Error occurred after writing to socket: too many bytes written.

DSS06547 "ICMP Error: Could not issue ICMP Echo request – Because List of IP address for the IP subnet was notavailable."

Explanation: ICMP Error: This error may have occurred due to the Problem in Network address, e.g. wrongIP address.

DSS06548 "ICMP Error: Could not start Network Discovery Service because bad IP address received -- The IPaddress was '&1'."

Explanation: ICMP Error: This error may have occurred due to an incorrect IP address or host name.

DSS06549 "TCP/IP Error: &1 could not understand command &2 from sender at &3."

Explanation: TCP/IP Error: &1 could not understand command &2 from sender at &3. A packet was readthat did not contain a known command. This could be a programming error or an attempt wasmade to connect to the server with an unauthorized client.

DSS06550 "TCP/IP Error: Listener received an incorrect packet. Command=&1, Sender IP address=&2,PortNum=&3."

Explanation: TCP/IP Error: Listener received an incorrect packet. Command=&1, Sender IP address=&2,PortNum=&3.

54


DSS06551 "TCP/IP Error: Ill formed packet. command &1, was supposed to be followed by a length and didn't getone."

Explanation: TCP/IP Error: Ill formed packet. command &1, was supposed to be followed by a length anddidn't get one.

DSS06552 "TCP/IP Error: Ill formed packet. command &1, was supposed to be followed by a length, but contained&2."

Explanation: TCP/IP Error: Ill formed packet. command &1, was supposed to be followed by a length, butcontained &2.

DSS06553 "Source &1: Expecting ReadyLogon XML tag, but received :&2."

Explanation: Source &1: The proper response to START and LOGON is READY.

DSS06554 "Listener cannot attach server task &1, name =&2, error &3 occurred."

Explanation: A client requested theMVS Listener attach a dynamic server which was not defined to thelistener.

DSS06555 "Unable to use TCP/IP services because the user &1 does not have an OMVS segment defined toRACF."

Explanation: Unable to use TCP/IP services because the user &1 does not have an OMVS segment defined toRACF. Define userid &1 to RACF with an OMVS Segment.

DSS06557 "Unable to obtain info with the stat() function about file: &1. Error returned : $2."

Explanation: Unable to obtain info with the stat() function about file: &1. Error returned : $2.

DSS06558 "File: &1 is not an SUID. This must be run as a SUID process for user validation."

Explanation: File: &1 is not an SUID. This must be run as a SUID process for user validation.

DSS06559 "File: &1 is not an GUID. This must run as a GUID process to run the requested service."

Explanation: File: &1 is not an GUID. This must run as a GUID process to run the requested service.

DSS06560 "The USERID: &1 is not valid on this system. Password not checked."

Explanation: The USERID: &1 is not valid on this system. Password not checked.

DSS06561 "The supplied PASSWORD for USERID '&1' is not valid on this system. Make sure the password for thisuser is correct, including case."

Explanation: The supplied PASSWORD for USERID '&1' is not valid on this system.

Action: Make sure the password for this user is correct, including case.

DSS06562 "The USERID: &1 is not valid in this system's shadow file. Password not checked."

Explanation: The USERID: &1 is not valid in this system's shadow file. Password not checked.

DSS06563 "The PASSWORD for USERID: &1 is not valid in this system's shadow file."

Explanation: The PASSWORD for USERID: &1 is not valid in this system's shadow file.

55

System Messages

DSS06564 "The USERID: &1 is not in the default product group: &2. This user is not authorized."

Explanation: The USERID: &1 is not in the default product group: &2. This user is not authorized.

DSS06565 "The GroupID: &1 for USERID: &2 cannot be set. Error: &3."

Explanation: The GroupID: &1 for USERID: &2 cannot be set. Error: &3.

DSS06566 "The UID: &1 for USERID: &2 cannot be set. Error: &3."

Explanation: The UID: &1 for USERID: &2 cannot be set. Error: &3.

DSS06567 "The Host connection has been terminated."

Explanation: An error occurred in the host code. Connection has been terminated.

DSS06568 "A TCP/IP DSSIAPI call was issued but the APIClientIP object is not connected to the host yet. UseinitIP()."

Explanation: The constructor for APIClientIP does not automatically open a connection or you have issuedstopAPISession().

Action: Use initIP().

DSS06570 "The UNIX system command, open, failed on file: &1 with errno =&2. &3. Cannot create the file."

Explanation: The UNIX system command, open, failed on file: &1with errno = &2. &3. Cannot create the file.

DSS06571 "The UNIX command, chmod, failed on file: &1 with errno =&2. &3. Cannot change file permissions."

Explanation: The UNIX command, chmod, failed on file: &1with errno = &2. &3. Cannot change filepermissions.

DSS06572 "Attempt to change directory to &1 failed with error code &2: &3."

Explanation: In attempting to change directory to &1, the call to chdir function returned error code &2. Thisis interpreted as: &3.

DSS06573 "Attempt to get current directory failed with error code &1: &2."

Explanation: Attempt to get the name of the current directory using getcwd function returned errorno &1.This is interpreted as: &2.

DSS06574 "Attempt to fork a process from &1 failed with errno &2: &3."

Explanation: Attempt to fork a process from &1 failed and returned errno &2. This is interpreted as: &3. Outofmemory or maximum number of processes reached.

DSS06575 "Attempt to become session leader failed with errno &1: &2."

Explanation: Attempt to create a new session and become session leader failed and returned errno &2. Thisis interpreted as: &2. The process is already a group leader.

DSS06576 "Error '&1' occurred during readlink(). The error message is: &2."

Explanation: The path to the executable is a symbolic link. readlink() attempted to find the underlying file butfailed with errno &1. Error message: &2.

56


DSS06577 "The environment variable '&1' is not set. &2 was not started from script."

Explanation: The environment variable '&1' is not set indicating that executable '&2' was not started fromthe correct start up script. This must be done to make correct execution possible.

Action: Use the correct startup script for the executable.

DSS06578 "Error '&1' (message: '&3') in realpath() during search for product home directory. Execute wrapperscript provided for '&2' or set 'DSSIHOMEDIR' environment variable."

Explanation: System function 'realpath', called to find product home directory containing '&2', failed witherrno '&1'. Error message: '&3'.

Action: Define DSSIHOMEDIR environment variable or run this executable using the wrapper scriptprovided.

DSS06579 "Signal number '&1' received while executing a command from shell within the 'system' function."

Explanation: The signal number '&1' was received while executing a command within the shell using the'system' function. The shell returns 128 + the signal number. (We subtract the 128).

DSS06580 "Process terminated with signal number '&1'."

Explanation: Process terminated with signal number '&1'.

DSS06581 "Process STOPPEDwith signal number '&1'."

Explanation: Process STOPPED with signal number '&1'.

DSS06582 "Internal communication error. Client &1 received End Of Data before completion of handshaking during&2 while connected to &3. Connection canceled. Please try again."

Explanation: Internal communication error. Client &1 received End Of Data before completion ofhandshaking during &2while connected to &3. Connection canceled. Please try again.

Action: Try to reconnect.

DSS06583 "&1. Missing LOGON tag in LOGONpacket."

Explanation: &1. Missing LOGON tag in LOGONpacket.

DSS06584 "Client &1 did not receive a serverRandom from server &2."

Explanation: Client &1 did not receive a serverRandom from server &2.

DSS06585 "Client &1 did not receive a public key from server &2."

Explanation: Client &1 did not receive a public key from server &2.

DSS06586 "&1. Server requested an encryption option denied by the client."

Explanation: &1. Server requested an encryption option denied by the client.

DSS06587 "&2, Missing &1, required to generate symmetric key."

Explanation: &2, Missing &1, required to generate symmetric key.

DSS06588 "Did not receive LOGON information."

57

System Messages

Explanation: Did not receive LOGON information.

DSS06589 "Server &1 reports that handshaking did not pass preliminary tests. Connection from client &2 refused."

Explanation: Server &1 reports that handshaking did not pass preliminary tests. Connection from client &2refused.

DSS06590 "Client &1 did not receive a proper cipherSuite from server &2."

Explanation: &1. Client did not receive a proper cipherSuite.

DSS06591 "&1 &2 expecting data socket from &3 but received &4."

Explanation: &1&2 expecting data socket from &3 but received &4.

DSS06592 "Attempt to read data prior to completion of handshaking."

Explanation: Attempt to read data prior to completion of handshaking. Internal Error.

DSS06593 "Client &1 wasmissing &2 from LOGONpacket from server &3 using code page &4."

Explanation: Client &1was missing &2 from LOGONpacket from server &3 using code page &4.

DSS06594 "&1. Local Codepage &2, cannot be translated from &3."

Explanation: &1. Local Codepage &2, cannot be translated from &3.

DSS06595 "Client &1 did not provide supported translation modes to server &2."

Explanation: Client &1 did not provide supported translation modes to server &2.

DSS06596 "Server &1 requires encryption from client &2. Client/Server could not agree."

Explanation: Server &1 requires encryption from client &2. Client/Server could not agree.

DSS06597 "Client &1 sent incorrect public key &2, server &3 could not decode the signature &4."

Explanation: Client &1 sent incorrect public key &2, server &3 could not decode the signature &4.

DSS06598 "Error '&1' (message: '&3') was received while trying to find the real path corresponding to the specifiedpath '&2'."

Explanation: System function 'realpath()', called to find the real path corresponding to '&2', failed with errno'&1'. Error message: '&3'.

DSS06600 "Command &1 from &2 is not possible while &3 &4 socket in &5 state."

Explanation: Command &1 from &2 is not possible while &3&4 socket in &5 state.

DSS06601 "XML Error: Error encountered while parsing XML data received from Host: '&1', XML error message:'&2'."

Explanation: XML Error: Error encountered while parsing XML data received from remote host.

DSS06602 "Packet from &1 does not contain a properly formatted command. Packet Started with &2."

Explanation: Packet from &1 does not contain a properly formatted command. Packet Started with &2.

58


DSS06603 "Packet from &1, &2 defined length was &3, amount read was &4. Connection Terminated."

Explanation: Packet from &1, &2 defined length was &3, amount read was &4. Connection Terminated.

DSS06604 "&1. Attempt wasmade to read data prior to completion of handshaking, &2 socket in &3 state."

Explanation: &1. Attempt was made to read data prior to completion of handshaking, &2 socket in &3 state.

DSS06605 "Packet from &1, length &2 is beyond the limit of &3."

Explanation: Packet from &1, length &2 is beyond the limit of &3.

DSS06606 "XML sequence didn't receive &1 but did receive &2."

Explanation: XML sequence didn't receive &1 but did receive &2.

DSS06607 "Server for PCB &1 cancelled before taking control of TCP/IP socket."

Explanation: Server for PCB &1 cancelled before taking control of TCP/IP socket.

DSS06608 "DJ0CLSN - start of server &1 on socket &2 failed. Attempting take back of socket."

Explanation: DJ0CLSN - start of server &1 on socket &2 failed. Attempting take back of socket.

DSS06609 "DJ0CLSN - take back of socket &1 failed with Reason =&2, RC=&3."

Explanation: DJ0CLSN - take back of socket &1 failed with Reason = &2, RC = &3.

DSS06610 "DJ0CLSN - take back of socket completed. Closing retaken socket &1."

Explanation: DJ0CLSN - take back of socket completed. Closing retaken socket &1.

DSS06611 "DJ0CLSN - close of lost socket got RC=&1."

Explanation: DJ0CLSN - close of lost socket got RC = &1.

DSS06612 "DJ0CLSN - taking PCB &1 out of service."

Explanation: DJ0CLSN - taking PCB &1 out of service.

DSS06613 "Invalid servers keyword &1 on restrict definition, valid values are &2."

Explanation: Invalid servers keyword &1 on restrict definition, valid values are &2.

DSS06614 "A multithreaded application attempted a &2 request before a &1 request was finished."

Explanation: Amultithreaded application attempted a &2 request before a &1 request was finished.

DSS06650 "&1 started listener on port &2 for &3."

Explanation: &1 started listener on port &2 for &3.

DSS06651 "&1 stopped listener on port &2 for &3."

Explanation: &1 stopped listener on port &2 for &3.

DSS06652 "TCP/IP Listener was started on port &1 for host &2."

Explanation: The TCP/IP Listener was started using the specified port number.

59

System Messages

DSS06653 "TCP/IP Listener on port &1 is stopping. Requested by &2."

Explanation: The TCP/IP Listener on the specified port has been stopped.

DSS06654 "Connection rejected userid and password required."

Explanation: An attempt was made to connect to the Listener with no userid and password.

DSS06655 "No PCB available to TCP/IP task."

Explanation: An attempt to connect was made via TCP/IP and no PROCTASKs were available.

DSS06656 "Invalid length on userid or password."

Explanation: Userid and password for TCP/IP connections to OS/390must be no greater than 8 characters.

DSS06657 "TCP/IP listeners were started on the following ports."

Explanation: A LISTIP operator command was issued and this is the header for the list.

DSS06658 "The port number was transformed by the system from &1 to &2."

Explanation: The OS/390 TCP/IP subsystem changed the specified port number.

DSS06659 "Maximum number of listeners exceeded."

Explanation: Themaximum number of listeners allowed is 25.

DSS06660 "No TCP/IP Listeners are active."

Explanation: A LISTIP operator command was issued and no TCP/IP listeners are running.

DSS06661 "Invalid authentication flag in first IP packet, flag was '&1' from client &2."

Explanation: First IP packet did not translate properly, client is rejected.

DSS06662 "Invalid compression flag in first IP packet, flag was '&1' from client &2."


DSS06663 "Invalid encryption flag in first IP packet, flag was '&1' from client &2."


DSS06664 "Unable to allocate TCP/IP control block on PCB."

Explanation: Allocation error occurred, TCP/IP cannot proceed.

DSS06665 "Expected LOGONpacket, but was not received."

Explanation: Expected LOGONpacket, but was not received.

DSS06666 "Server &1 received LOGONpacket, but required userid wasmissing from client &2."

Explanation: Server &1 received LOGONpacket, but required userid was missing from client &2.

DSS06667 "Invalid task type specified, &1 not resolvable."

Explanation: The START packet specified an invalid task type or the FIPDEF buffer was corrupted.

60


DSS06668 "Unable to synchronize PCFILE. See the following message for details."

Explanation: Unable to synchronize local PCFILE with the primary PCFILE.

Action: Seemessage DSS06669 for details.

DSS06669 "Hostname &1 is invalid on IP address &2. Primary PCFILE unavailable, local PCFILE will be used inread only mode."

Explanation: Hostname&1 is invalid on IP address &2. Primary PCFILE unavailable, local PCFILE will be usedin read only mode. Bad path was &3.

DSS06670 "Remote PCFILE on host &1 and port &2 is not available. See error message on host &3. Local PCFILEwill be used in read only mode."

Explanation: Remote PCFILE on host &1 and port &2 is not available.

Action: See error message on host &3. Local PCFILE will be used in read only mode. Bad path was &4.

DSS06671 "Started task is a PCFILE secondary to host &1 at port &2."

Explanation: This started task will only use the local(secondary) PCFILE if the connection to the primary isunavailable.

DSS06672 "IP address &1 and port &2 is not reachable from IP &3, local PCFILE will be used in read only mode."

Explanation: IP address &1 and port &2 is not reachable from IP &3, local PCFILE will be used in read onlymode. Bad path was &4.

DSS06673 "Unable to connect to remote PCFILE; Duplicate connection found in configuration."

Explanation: Unable to connect to remote PCFILE; Duplicate connection found in configuration. Bad pathwas &1.

DSS06674 "Session terminated by operator KILL command."

Explanation: This TCP/IP session was terminated when the started task accepted a KILL command from theoperator.

DSS06675 "Invalid port number &1 specified, Port number must be between 1023 and 65536 (non-inclusive)."

Explanation: The port number for the STARTIP command must be between 1023 and 65536 (non-inclusive).

DSS06676 "Unable to communicate with the server at &1. Timeout occurred while waiting for data. Communicationis terminated."

Explanation: A timeout was specified before a read operation and the timeout occurred before the dataarrived.

DSS06677 "Unable to externally close socket. Socket Number invalid."

Explanation: An attempt was made to cancel a socket from outside the socket class. The socket numberspecified was not available to close.

DSS06678 "Host name &1 resolves to more than one IP address &2. Host name not useable. Pick one IP addressor use INADDR_ANY. Aborting Listener."

61

System Messages

Explanation: Listeners can only listen on one IP address or INADDR_ANY. The host name&1 specifiedresolves to more than one IP address &2.

DSS06679 "The -f option (use JPCONFIG file) conflicts with -r (remote PCFILE IP) and -m (remote PCFILE port)."

Explanation: The -f option (use JPCONFIG file) conflicts with -r (remote PCFILE IP) and -m (remote PCFILEport).

DSS06680 "The TCP/IP connection to the host was lost."

Explanation: A TCP/IP DSSIAPI call was issued but the APIClientIP object lost its connection to the host.

DSS06681 "TCP/IP connection cleaning up after an XMS session that didn't clean up."

Explanation: TCP/IP connection cleaning up after an XMS session that didn't clean up.

DSS06682 "Task terminated because PCB for TCP/IP task is not in a valid state. &1."

Explanation: Task terminated because PCB for TCP/IP task is not in a valid state. &1.

DSS06690 "Install Configuration File not specified."

Explanation: There was no Configuration filename given to install.

DSS06691 "Open for read error for configuration file: '&1', Error='&2'."

Explanation: Error occurred with fopen() to read for the configuration file: '&1', Error='&2'.

DSS06692 "FTP connect() error: Host= '&1', Error='&2'."

Explanation: FTP error occurred when attempting to connect to Host: '&1', Error='&2'.

DSS06693 "FTP get_response() error."

Explanation: No response was received from FTP server.

DSS06694 "FTP user() error: User= '&1'."

Explanation: FTP error, Invalid user: '&1'.

DSS06695 "FTP passwd() error."

Explanation: FTP error, Invalid password.

DSS06696 "FTP putfile() error."

Explanation: FTP error in call to putfile().

DSS06697 "REX rexec() error: '&1'."

Explanation: REX rexec() error: '&1'.

DSS06698 "This machine cannot install agent."

Explanation: This machine cannot install agent.

Action: Use an AIX agent.

DSS06699 "Start packet was ill-formed."

62


Explanation: Start packet was ill-formed.

DSS06700 "Member '&1' of dataset '&2' is locked by another user."

Explanation: Member '&1' of dataset '&2' is locked by another user with SPFEDIT.

DSS06701 "No Input Arrival Date was specified for this job."

Explanation: No Input Arrival Date was specified for this job.

DSS06702 "No Input Arrival Time was specified for this job."

Explanation: No Input Arrival Timewas specified for this job.

DSS06703 "No TWS subsystem was specified."

Explanation: No TWS subsystem was specified.

DSS06704 "Call to DJ0YFTCHParm:&1 returned &2."

Explanation: Call to DJ0YFTCH Parm:&1 returned &2.

DSS06705 "Call to EQQYCOMAction:&2 Resource:&3, returned &1."

Explanation: Call to EQQYCOM Action:&2 Resource:&3, returned &1.

DSS06706 "Call to DJ0YG24B unable to get storage, RC='&1'."

Explanation: Call to DJ0YG24B unable to get storage, RC='&1'.

DSS06707 "Unable to initialize EQQYCOM for subsystem '&1'."

Explanation: Unable to initialize EQQYCOM for subsystem '&1'.

DSS06708 "Insert of &1 records into the JS file failed. TWS processing was not done."

Explanation: Insert of &1 records into the JS file failed. Check record size of JS file. TWS processing was notdone.

DSS06709 "EQQYCOMSELECT JCLV failed for '&1'."

Explanation: EQQYCOM SELECT JCLV failed for '&1'.

DSS06713 "ENQ failed."

Explanation: ENQ failed.

DSS06714 "EQQYCOM LIST JCLPREPA failed."

Explanation: EQQYCOM LIST JCLPREPA failed.

DSS06715 "EQQYCOM returned JCL from the JS repository ... please delete."

Explanation: JCLPREPA call returned JCL from the TWS repository.

Action: The &1 occurrence needs to be edited and all records deleted.

DSS06716 "Input Arrival is beyond the Current Plan. Resolution of &O variablesmay be incorrect."

63

System Messages

Explanation: Input Arrival is beyond the Current Plan so the PRO/JCL AD occurrence could not bemodifiedto reflect the desired run date. Any TWS variables derived from the Occurrence date (&OMM,&ODD, etc.) will not reflect the desired date.

DSS06717 "EQQYCOMSELECT CPST failed."

Explanation: EQQYCOM SELECT CPST failed.

DSS06718 "ADID&1 is not active on &2. Variable substitution will fail."

Explanation: Application Description &1 is not active on &2. Variable substitution will fail.

DSS06719 "NoMatching Application Descriptions Found."

Explanation: No Matching Application Descriptions Found.

DSS06720 "No JCL returned by &1 for AD&2, Operation &3."

Explanation: No JCL returned by &1 for AD &2, Operation &3.

DSS06721 "EQQYCOM&1 &2."

Explanation: EQQYCOM &1&2.

DSS06722 "A dependency loop was detected while processing &1 &2. Process stopped. Check SYSPRINT DD."

Explanation: A dependency loop was detected while processing &1&2. No further operations will beprocessed. The SYSPRINT will have the list of operations where the loop was detected.

DSS06723 "TWS variable substitution failed."

Explanation: TWS variable substitution failed. Look at EQQ messages for a description.

DSS06800 "DJ0YESPX returned error: &1."

Explanation: DJ0YESPX returned error: &1.

DSS06801 "No ESP subsystem was specified."

Explanation: No ESP subsystem was specified.

DSS06802 "Required ESP event name was not specified."

Explanation: An ESP event namemust be specified for simulation.

DSS06803 "ESP return code was &1. Please check PRO/JCL SYSPRINT for ESP messages."

Explanation: ESP return code was &1. Please check PRO/JCL SYSPRINT for ESP messages.

DSS06804 "Unable to allocate storage for ESP zblocks."

Explanation: Unable to allocate storage for ESP zblocks.

DSS06805 "'&1' is not a qualified event name."

Explanation: '&1' does not have a valid qualifier. The event namemust be qualified and the qualifier must bebetween 1 and 8 characters.

64


DSS06806 "ESP event name '&1' does not have a valid qualifier."

Explanation: ESP event name '&1' does not have a valid qualifier. The event namemust be between 1 and 16characters with a qualifier of 1 to 8 characters.

DSS06807 "ESP event name '&1' is not valid."

Explanation: ESP event name '&1' is not valid. The event namemust be between 1 and 16 characters with aqualifier of 1 to 8 characters.

DSS06808 "ESP processed &1 of &2 records."

Explanation: Only &1 of &2 records were processed by ESP. The probable cause of this is the event used forsimulation does not contain enough records for PRO/JCL to substitute all its records. PRO/JCLcan substitute a maximum of 100 records for each record in the simulated event JCL.

DSS06900 "SMF record type &1 not written because length specified in RDW was less than 18 bytes."

Explanation: DJ0YSMFW cannot write SMF record of type &1. The length specified in the RDWwas less than18 bytes.

DSS06901 "SMF record type &1 not written because address space is not APF authorized."

Explanation: DJ0YSMFW cannot write SMF record of type &1 because the address space is not APFauthorized.

DSS06902 "SMF record type &1 not written because SMF is not active."

Explanation: DJ0YSMFW cannot write SMF record of type &1 because SMF is not active or has abended.

DSS06903 "SMF record type &1 not written because suppressed by installation exit."

Explanation: The SMF record of type &1was not written because it was suppressed by IEFU83 or anotherinstallation-written exit.

DSS06904 "SMF record type &1 not written because SMF lost the data."

Explanation: The SMF record of type &1 not written because SMF lost the data.

DSS06905 "SMF record type not written because SMF is not recording the record type '&1'."

Explanation: The SMF record was not written because SMF is not recording the record type specified in theSMFRECORDTYPE RTS option.

DSS06906 "SMF record type &1 not written due to SMF buffer shortage."

Explanation: The SMF record of type &1 not written because SMF had a buffer shortage and lost the data.

DSS06907 "SMF record type &1 not written because SMF could not establish recovery."

Explanation: The SMF record of type &1 not written because SMF could not establish an error recoveryenvironment.

DSS06908 "SMF record type &1 not written because caller not in primary ASCmode."

65

System Messages

Explanation: The SMF record of type &1 not written because the caller was not in primary ASC mode or theASID was incorrect.

DSS06909 "SMF record type &1 not written - return code '&2' from SMFWTM."

Explanation: SMF record type &1 not written - return code '&2' from SMFWTM.

DSS06910 "SMF record type &1 not written - record type should have been 128-255."

Explanation: SMF record type not written. The record type was '&1', should have been 128-255.

DSS06917 "'&1' address space not active. Cannot retrieve DDnames."

Explanation: '&1' address space not active. Cannot retrieve DD names.

DSS06918 "Too many DDs allocated in the &1 address space. Only the first &2 are returned."

Explanation: Too many DDs allocated in the &1 address space. Only the first &2 are returned.

DSS06919 "Could not retrieve &1 DDnames due to lack of APF authorization."

Explanation: Could not retrieve &1 DD names due to lack of APF authorization.

DSS06920 "'&1' address space not active. Cannot retrieve &2 datasets."

Explanation: '&1' address space not active. Cannot retrieve &2 datasets.

DSS06921 "Too many datasets for JES2/JES3 PROCLIB. Only the first &1 are returned."

Explanation: Too many datasets for JES2/JES3 PROCLIB. Only the first &1 are returned.

DSS06922 "DJ0YJ2PDRC=&1. Please call ASGSoftware Technical Support."

Explanation: DJ0YJ2PD RC=&1. Please call ASG Software Technical Support.

DSS06923 "Could not retrieve JES2/JES3 PROCLIB datasets due to lack of APF authorization."

Explanation: Could not retrieve JES2/JES3 PROCLIB datasets due to lack of APF authorization.

DSS06924 "Error when activating a extended MCS console with MCSOPERmacro specifyingREQUEST=ACTIVATE."

Explanation: Error when activating a extended MCS console with MCSOPER macro specifyingREQUEST=ACTIVATE.

DSS06925 "Error when using the MCSOPMSGmacro to get a message from an extended MCS console."

Explanation: Error when using theMCSOPMSGmacro to get a message from an extended MCS console.

DSS06926 "The extended MCS console name has already been used."

Explanation: The extended MCS console name has already been used.

DSS06927 "Error when deactivating a extended MCS console with MCSOPERmacro specifyingREQUEST=DEACTIVATE."

Explanation: Error when deactivating a extended MCS console with MCSOPER macro specifyingREQUEST=DEACTIVATE.

66


DSS06928 "Alert detected the extended MCS console will be deactivated."

Explanation: Alert detected the extended MCS console will be deactivated.

DSS06929 "Extended MCS console queueing stopped because the memory limit has been exceeded."

Explanation: Extended MCS console queueing stopped because thememory limit has been exceeded.

DSS06930 "Extended MCS console queueing stopped because the depth limit has been exceeded."

Explanation: Extended MCS console queueing stopped because the depth limit has been exceeded.

DSS06931 "Extended MCS console encountered an internal system error."

Explanation: Extended MCS console encountered an internal system error.

DSS06932 "Extended MCS console encountered a queue depth alert."

Explanation: Extended MCS console encountered a queue depth alert.

DSS06933 "&1."

Explanation: This message contains the output from a command issued on an extended MCS console.

DSS06934 "Required attribute missing or not available for file=&1."

Explanation: Dataset &1 for JES2 PROCLIB definitions does not have the required attributes of type, dsorg,recfm, or lrecl.

DSS06935 "Non PDS FB 80 attributes on file=&1. Dataset skipped."

Explanation: Dataset &1 for JES2 PROCLIB definitions must be a PDS with FB 80 bytes records.

DSS06936 "No JES2 PROCLIB information was returned from a $DPROCLIB(*) command."

Explanation: Program DJ0YCONS issued a $D PROCLIB(*) command, and no JES2 PROCLIB information wasreturned.

DSS06937 "Could not retrieve JES2 PROCLIB dataset name for entry &1 in &2. Please contact ASG TechnologiesCustomer Support."

Explanation: Could not retrieve JES2 PROCLIB dataset name for entry &1 in &2. Possibly an internal issue.Please contact ASG Technologies Customer Support.

DSS07100 "&1 of &2 failed with rc=&3, error=&4."

Explanation: &1 of &2 failed with rc=&3, error=&4.

DSS09999 "&1 &2 &3 &4."

Explanation: DO NOT REMOVE OR CHANGE THIS MESSAGE!

DSS10000 "Member namemust be specified."

Explanation: When you use parentheses to indicate a PDS member name, themember namemust not beleft entirely blank.

67

System Messages

Action: At least one character is required in order for themember name to be valid. Related IBMmessage: IEF646I.

DSS10001 "Member name is too long. Length = &1; maximum length is 8."

Explanation: The length of themember name you specified (&1) exceeds themaximum member namelength (8). Related IBM message: IEF642I.

DSS10002 "Member name '&1' not valid. Use '&2(+&1)' if relative GDG number."

Explanation: The numeric digit '&1' is not a valid member name.

Action: If you intended to refer to a generation dataset, use '&2(+&1)' instead. Related IBM message:IEF647I.

DSS10003 "Member namemay not start with '&1'."

Explanation: The character '&1' is not valid at the start of a member name.

Action: Member names must start with an uppercase alphabetic ('A'-'Z') or national character (nationalcharacters are '@', '#', and '$'). Related IBM message: IEF647I.

DSS10004 "Member namemay not contain '&1' (position &2)."

Explanation: The character '&1' at position &2 in themember name specified is not valid.

Action: Valid characters at this location include uppercase alphabetic ('A'-'Z'), numeric ('0'-'9'), andnational characters ('@', '#', or '$') only. Related IBM message: IEFC620I.

DSS10005 "Relative generation number '&1' is not valid."

Explanation: '&1' is not valid as a relative number to access a generation dataset in a generation data group.

Action: Only numeric digits between 0 and 255 are allowed (a single leading '+' or '-' is also required,except for relative number '0'). Related IBM message: IEF366I.

DSS10006 "JCLLIB statement can only be coded once per JOB."

Explanation: Only one JCLLIB statement can be coded in any JOB. Related IBM message: IEFC020I.

DSS10007 "GDG base must be non-temporary dataset."

Explanation: Only a permanent dataset can be used as the base for a generation data group. This error couldbe caused by failure to resolve a symbolic variable, resulting in leaving an '&' at the beginning ofthe dataset name. Related IBM messages: either IEFC651I, IEFC626I, or IEF647I.

DSS10008 "Length of PARM field, &1, exceedsmaximum of 100."

Explanation: Length of PARM field, &1, exceeds maximum of 100.

DSS10009 "GDG base name length &1 is not valid; maximum length is 35."

Explanation: GDG base name length &1 is not valid; maximum length is 35. Themaximum length of a DSNused as a generation data group base is 35. The reason for this restriction is that themaximumlength of any dataset name is 44, and the system constructs the names of individual generationdatasets within the generation data group by taking the generation data group name and

68


appending a node of the form '.GnnnnVnn', which consumes 9 positions of the dataset name.Therefore, themaximum base length is 44 - 9, or 35. Related IBM message: IDC3523I.

DSS10010 "Dataset name '&1' has length &2. Maximum is 44."

Explanation: Dataset names may be only up to 44 characters in length. The dataset name indicated ('&1') hasa length of &2. Related IBM message: IEF642I.

DSS10011 "Node &1 of dataset '&2' ('&3') has length &4. Maximum is 8."

Explanation: The node at position &1 in dataset name '&2' ('&3') is &4 characters long.

Action: Themaximum length for any node in a dataset name is 8 (a 'node' is a segment of a datasetname between periods). Related IBM message: IEF642I.

DSS10012 "Node &1 of dataset '&2' may not start with a period (position &3)."

Explanation: Individual nodes within a dataset namemay not start with periods. A period was found at thestart of node &1 in dataset name '&2' (position &3 relative to the start of the dataset name).Possible causes of this error include coding two periods in a row, or having an unresolvedsymbolic in the dataset name. Related IBM message: IEF647I.

DSS10013 "Character '&1' at position &2 of DSN '&3' is not valid at the start of a node."

Explanation: Character '&1' at position &2 of DSN '&3' is not valid at the start of a node.

Action: Only uppercase alphabetic ('A'-'Z') and national ('@', '#', and '$') characters can appear at thestart of a node of a dataset name (a 'node' is a segment of a dataset name between periods).Related IBM messages: IEF647I,IEFC620I.

DSS10014 "Character '&1' at position &2 of DSN '&3' is not valid in non-quoted DSN's."

Explanation: Character '&1' at position &2 of DSN '&3' is not valid in non-quoted DSN's. The character '&1' isnot valid in a dataset name, unless the entire dataset name is enclosed in single quotes.

Action: The only characters that are valid at this location in non-quoted DSN's are uppercase alphabetic('A'-'Z'), numeric ('0'-'9'), national ('@', '#', and '$'), hyphen ('-'), and left curly brace ('{' - EBCDIChex 'C0'). Related IBM message: IEFC620I.

DSS10015 "Dataset name '&1' may not end with a period."

Explanation: The dataset name specified ('&1') may not end with a period.

Action: If the dataset name ends with a period, the entire dataset namemust be enclosed within singlequotes, and will be treated as an unqualified dataset name. Related IBM message: IEFC624I.

DSS10016 "Temporary dataset name ('&1') may not contain periods. Possible unresolved symbolic."

Explanation: Temporary dataset name ('&1') may not contain nodes. A dataset name that starts with anampersand ('&') cannot contain periods. Possible causes of this error include failure to properlyresolve a symbolic coded as the first node of a permanent dataset name. Related IBM message:IEFC624I.

DSS10017 "Temporary dataset name length &1 is not valid."

69

System Messages

Explanation: Temporary dataset names must have between 1-8 characters following the initial ampersand.The temporary dataset name specified contains &1 characters after the ampersand. RelatedIBM messages: IEF642I, IEF643I.

DSS10018 "Character '&1' is not valid at the start of temporary dataset name '&2'."

Explanation: The character '&1' may not be used to begin the name of a temporary dataset('&2').

Action: Only uppercase alphabetic ('A'-'Z') or national ('@', '#', or '$') characters may be used at thebeginning of the name of a temporary dataset. Related IBM messages: IEF647I, IEFC620I.

DSS10019 "Character '&1' at position &2 of temporary dataset name '&3' is not valid."

Explanation: The character '&1' is not valid at position &2 in the temporary dataset name '&3'.

Action: The only characters that are valid at this location are uppercase alphabetic ('A'-'Z'), numeric ('0'-'9'), national ('@', '#', and '$'), hyphen ('-') and left curly brace ('{' - EBCDIC hex 'C0'). Related IBMmessage: IEFC620I.

DSS10020 "A 'JCLLIB' statement may not be coded after an 'EXEC', 'IF', or 'INCLUDE' statement."

Explanation: If a 'JCLLIB' statement is used in a JOB, it must appear prior to the first 'EXEC', 'IF', or 'INCLUDE'statement. Related IBM message: IEFC019I.

DSS10021 "Node &1 of '&2' is not &3."

Explanation: In '&2', the node at position &1 is not &3. DDNAME's and STEPNAME's must be 1-8 charactersin length.

Action: The first character must be alphabetic (uppercase 'A'-'Z') or national ('@', '#', or '$'), and all othercharacters must be uppercase alphabetic or numeric ('0'-'9'). Related IBM messages: IEFC620I,IEF645I.

DSS10022 "All masking characters were used in &1. This is not allowed."

Explanation: This field may not have only masking characters ('*', '%').

DSS10023 "'&1' parameter invalid with entry type of dataset '&2'."

Explanation: Cannot alter &1 for entry types INDEX, DATA, GDGBASE, ALIAS, AIX, or PATH.

DSS10024 "IDCAMS 'ELSE' is unmatched by a previous 'IF'."

Explanation: An IDCAMS 'ELSE' statement was coded for which no previous 'IF' statement was found. WhenIDCAMS encounters this statement, it will set the statement's 'condition code' to 16, resultingin flushing all subsequent statements. In order to do as much validation as possible, PRO/JCLwill set the condition code to 16, but will not flush all subsequent IDCAMS statements. RelatedIBM message: IDC4227I.

DSS10025 "Restricted entry name '&1' was specified; it is not allowed."

Explanation: An attempt was made to alter a VSAM volume dataset ('ALTER &1'). IDCAMS does not allowALTER to operate against VSAM volume datasets. This restriction applies regardless of whetherthe VSAM volume dataset namewas specified explicitly or generically. Related IBM message:IDC3191I.

70


DSS10026 "'&1' was not expected after password."

Explanation: This IDCAMS parsing error was issued because '&1' was found after a dataset name, a slash,and a complete password. This could be caused by having a stray space within the passwordfield. Related IBM message: IDC3209I.

DSS10027 "'&1' is too long to be a valid password."

Explanation: '&1' is too long to be a valid password. Valid passwords may only be up to 8 characters inlength. Related IBM message: IDC3201I.

DSS10028 "JOB CARDdoes not have a job name."

Explanation: No JOBNAMEwas found on the JOB CARD. Related IBM message: IEFC635I.

DSS10029 "Expected slash was not found."

Explanation: In an IDCAMS statement, the only characters that can appear between the dataset name andits closing parenthesis are a slash ('/') followed by a password. A possible cause of this errorwould be leaving the slash out or mistyping the slash. Related IBM message: IDC3209I.

DSS10030 "Element name '&1' is improperly specified."

Explanation: Element name '&1' is improperly specified.

Action: If this message appears, contact ASG Technologies.

DSS10031 "Dataset name is missing."

Explanation: A dataset namemust be specified for this statement. Related IBM message: IDC3205I.

Action: Specify a dataset name for the statement.

DSS10032 "Underscore on the SCHENV parameter cannot end the statement."

Explanation: The underscore character is valid for the SCHENV parameter, but it cannot be coded in the lastposition.

DSS10033 "DDNAME ismissing or not valid."

Explanation: The DDNAME specified does not conform to the rules for ddnames. ddnames must be 1-8characters in length.

Action: The first character must be alphabetic (uppercase 'A'-'Z') or national ('@', '#', or '$'), and all othercharacters must be uppercase alphabetic or numeric ('0'-'9').

DSS10034 "'AMSDUMP' DD statement must be provided when the 'FULL' parameter is specified."

Explanation: In a step that issues an IDCAMS 'PARM TEST' statement that uses the 'FULL' parameter, the'AMSDUMP' DD statement must be allocated.

DSS10035 "Two subparameters were expected for 'MARGINS'."

Explanation: The IDCAMS 'PARM MARGINS' statement requires two subparameters - the left margin and theright margin. One or both of these subparameters weremissing, or too many subparameterswere specified.

71

System Messages

DSS10036 "Left margin &1 is too large; Should be less than SYSIN LRECL (&2)."

Explanation: In an IDCAMS 'PARM MARGINS' statement, the value specified for the left margin (&1) exceedsthe LRECL of the SYSIN dataset (&2). Statements to the left of column &1will not be processed.

DSS10037 "Right margin &1 is too large; Should be less or = to SYSIN LRECL (&2)."

Explanation: In an IDCAMS 'PARM MARGINS' statement, the value specified for the right margin (&1)exceeds the LRECL of the SYSIN dataset (&2). The effective value used will be the LRECL of theSYSIN dataset.

DSS10038 "Margins are not valid; resetting to default (2-72)."

Explanation: An IDCAMS 'PARM MARGINS' statement was encountered with incorrect values for the leftmargin, the right margin, or both. Because of this error, themargins are being reset to thedefault (2-72) until a subsequent valid 'PARM MARGINS' statement, if any, is processed.

DSS10039 "Incorrect use of apostrophe."

Explanation: This may be caused by two apostrophes preceding a PARM value. Related IBM message:IEFC629I.

DSS10040 "The Length of the value of symbol '&1' (&2) exceeds the maximum of 255."

Explanation: The length of the value of '&1' is &2 and exceeds themaximum length of 255.

DSS10041 "The first character of the VOLUMEENTRIES parmmust be 'V'."

Explanation: Failure to code the 'V' as the first character may result in the Volume Entry not being found.

DSS10042 "Extraneous comma was found and ignored."

Explanation: In the IDCAMS 'SET' and 'IF' statements, the keywords 'MAXCC' and 'LASTCC' can be specifiedwith embedded commas (example, 'SETMA,X,,,C,C' is valid). This message is issued as anadvisory, in case the user wishes to avoid this coding style.

DSS10043 "Spaces were found within value and ignored."

Explanation: In the IDCAMS 'SET' and 'IF' statements, the keywords 'MAXCC' and 'LASTCC' can be specifiedwith embedded spaces (example, 'SETMA X C C' is valid). This message is issued as an advisory,in case the user wishes to avoid this coding style.

DSS10044 "Comments were found within value and ignored."

Explanation: In the IDCAMS 'SET' and 'IF' statements, the keywords 'MAXCC' and 'LASTCC' can be specifiedwith embedded comments (example, 'SETMA/*A*/X/*B*/C/*C*/C' is valid). This message isissued as an advisory, in case the user wishes to avoid this coding style.

DSS10045 "Parameter '&1' is unrecognized."

Explanation: The parameter '&1' is not recognized in the context of the IDCAMS statement being processed.Possible causes of this error include specifying a keyword from one type of IDCAMS statementon a different statement, or a typographical error.

72


DSS10046 "Missing closing parenthesis; ')' needs to be inserted."

Explanation: The statement being processed ends before all matching right parentheses have been foundfor each left parenthesis. Although this is not an error, this message is issued in case the userwishes to avoid this coding style.

DSS10047 "Non-standard coding was found in '&1'."

Explanation: Non-standard coding was found in '&1'. In the IDCAMS 'SET' and 'IF' statements, manyacceptable ways exist to code the 'MAXCC', 'LASTCC', operand ('EQ', etc.) and valuesubparameters. In the statement being processed, a 'non-standard' technique wasencountered. This may be accompanied by a more specific message. Although this is not anerror, themessage is issued in case the user wishes to avoid this coding style.

DSS10048 "'&1' is not a recognized IDCAMS statement name."

Explanation: While processing IDCAMS statements, the statement '&1' was encountered. This is not arecognized IDCAMS statement name.

DSS10049 "Statement ends with '&1'; missing continuation is likely."

Explanation: An IDCAMS statement was found that ends with '&1'. Although the statement is syntacticallycorrect, it is unlikely that the statement performs as the user expected. For example, theIDCAMS statement 'IF MAXCC=4 THEN' (note the absence of a continuation mark) would causethis message to be issued, because themeaning of that statement is 'if themaximum conditioncode is equal to 4, then do nothing'.

DSS10050 "Positional parm '&1' is not allowed after keyword."

Action: All positional parameters, if coded, must appear before any keyword parameters. In this case,the positional parameter '&1' was found after a keyword parameter had already beenencountered.

DSS10051 "A JOB statement is not allowed within a PROCor INCLUDE."

Explanation: JOB statements may only appear in JCL members that are not used as PROC's or INCLUDE's.

DSS10052 "An EXEC statement must be preceded by a valid JOB or PROCstatement."

Explanation: EXEC statements may only appear after JOB or PROC statements. An EXEC statement wasfound before a valid JOB or PROC statement.

Action: Possible causes of this error includemisspelling the word 'JOB' or 'PROC' in a previousstatement.

DSS10053 "A DD statement must be preceded by a valid JOB or PROCstatement."

Explanation: DD statements may only appear after JOB or PROC statements. A DD statement was foundbefore a valid JOB or PROC statement.

Action: Possible causes of this error includemisspelling the word 'JOB' or 'PROC' in a previousstatement.

73

System Messages

DSS10054 "IDCAMS 'IF' statementsmay not be nested deeper than 10 levels."

Explanation: IDCAMS places a restriction on the depth of nesting of 'IF' statements – ten is themaximumdepth allowed. In order to provide as much validation in one pass as possible, PRO/JCL doesnot enforce this restriction, but rather notifies the user via this message so that the problemcan be corrected prior to a re-scan.

DSS10055 "A 'JOBLIB' DD statement must precede all other DD statements."

Explanation: If the special 'JOBLIB' DD statement is coded to indicate the libraries which should be searchedfirst for load modules, it must appear before all other DD statements. In this case, the 'JOBLIB'DD statement was found after some other DD statement had already been processed.

DSS10056 "A DD statement must be preceded by a valid EXEC statement."

Explanation: In general, DD statements may only appear after EXEC statements A DD statement was foundbefore a valid EXEC statement.

Action: Possible causes of this error includemisspelling the word 'EXEC' in a previous statement.

DSS10057 "The '&1' DD statement must precede all EXEC statements."

Explanation: The 'special' DD statement '&1' must appear before any EXEC statements.

Action: Examples of 'special' DD statements include 'JOBPROC', 'PROCLIB', and 'DYNAPROC', each ofwhich can be used to indicate from which libraries PROCs are to be expanded (via non-IBMproducts).

DSS10058 "Syntax error; parsing stopped at '&1'."

Explanation: A severe error was found while attempting to 'parse' (i.e. pull apart) the previous statementinto its component parts. This error results in ignoring the entire line after which it appears. Thecharacters '&1' were found near where the parser stopped.

DSS10059 "Premature end of '&1' statement; missing continuation is likely."

Explanation: The '&1' statement immediately preceding ended without specifying what action to take underthe indicated condition. This is often caused by omitting a continuation mark on the previousline. Although this is not a syntax error, themessage is issued to alert the user to a probabledifference between the behavior that will occur and what was intended.

DSS10060 "Job '&1' has no steps."

Explanation: JOB '&1' executes no steps that invoke a program, either directly or indirectly (via PROCs orINCLUDEs).

DSS10061 "CC&1 is greater than 16; treated as 16."

Explanation: In an IDCAMS 'SET' or 'IF' statement, an attempt to reference the condition code '&1' will betreated as if it had been a reference to 16, themaximum IDCAMS condition code.

DSS10062 "Parameter missing following IDCAMS DEFINE."

Explanation: No parameter was found following an IDCAMS DEFINE statement.

74


Action: Possible cause of this error is a missing continuation.

DSS10063 "Parameter missing following IDCAMS DELETE."

Explanation: No parameter was found following an IDCAMS DELETE statement.

Action: Possible cause of this error is a missing continuation.

DSS10064 "First character of value '&1' must be non-numeric."

Explanation: The value '&1' contains a number as the first character, but the first character is not permittedto be numeric.

DSS10065 "Parameter '&1' is unidentified."

Explanation: The parameter '&1' on the statement is not recognized as a valid parameter for the statementbeing processed.

Action: Possible causes of this error includemisspelling the parameter, or attempting to use aparameter that belongs on a different type of statement.

DSS10066 "Positional parameter '&1' is not valid."

Explanation: The positional parameter '&1' was found, but is not a valid parameter in the context of thecurrent statement.

Action: Possible causes includemisspelling the parameter, attempting to use a parameter that belongson a different type of statement, or omitting a keyword name.

DSS10067 "'&1' is an unidentified JCL statement, possibly a valid operator command."

Explanation: The JCL statement '&1' is not recognized as a valid JCL statement type.

Action: If this is a valid operator command, this message can be suppressed by specifying messagenumber (10067) and the value '&1' in theMessage Table.

DSS10068 "Expanded JCLmay be in ISPF packed format."

Explanation: The JCL statement has been flagged as an unidentified JCL statement by PRO/JCL. The formatof the statement indicates the PROC or INCLUDE was saved with ISPF pack on.

DSS10069 "Value '&1' must be in uppercase."

Explanation: The value '&1' contains a lowercase character, but uppercase is required.

Action: Ensure all characters are uppercase.

DSS10070 "Unidentified character '&1' was found in the '&2' field."

Explanation: The character '&1' was found while scanning the '&2' field. This character is not valid in the &2field.

DSS10071 "Value '&1' contains a non-valid character '&2'."

Explanation: The character '&2' was the first non-valid character found while scanning the value '&1'.

Action: The acceptable values that could have been coded are &3.

DSS10072 "Expected continuation was not received at EOF."

75

System Messages

Explanation: Themember being processed ended while a continuation line was expected. For JCL the lastparameter was followed with a comma or the last line had a nonblank coded in column 72. ForIDCAMS the last line ended with a hyphen or a plus sign.

DSS10073 "Expected quoted continuation was not received."

Explanation: The previous line terminated in themiddle of a quoted string, indicating that a continuation ofthe string was expected on the next line. This expected string continuation was not found.

DSS10074 "Expected continuation was not received."

Explanation: A line ended with a comma, or with a non-blank character in column 72, either of whichindicates that a continuation line was expected to follow. No such continuation line was found.

DSS10075 "Continuation line starts beyond column 16."

Explanation: The continuation line in this statement starts past column 16.

Action: The first two positions must contain '//' followed by at least 1 but no more than 13 blanksbefore the first character of the continuation line.

DSS10076 "'&1' is an unidentified JCL statement."

Explanation: The JCL statement '&1' is not recognized as a valid JCL statement type.

Action: Possible causes of this error include omitting at least one space after the '//' and before the'operator' field.

DSS10077 "'&1' should not appear here; it is treated as a comment."

Explanation: In an IDCAMS 'DO' or 'END' statement, '&1' was found after the 'DO' or 'END'. At this location inthe statement '&1' has no effect in IDCAMS and is treated as a comment. Expected statementmay not be executed.

DSS10078 "'&1' is mutually exclusive with '&2'."

Explanation: The '&1' and '&2' parameters cannot both be coded simultaneously.

DSS10079 "'&1' requires '&2'."

Explanation: If the '&1' parameter is coded, then the '&2' parameter must also be coded.

DSS10080 "Value '&1' should have been &2."

Explanation: The value coded ('&1') is not valid. The acceptable values that could have been coded are &2.

DSS10081 "STEPCAT may be specified only once in each job step."

Explanation: The 'STEPCAT' DD statement, which indicates the catalog name to be searched instead of theusual catalog search order, may only be specified once per job step. A 'STEPCAT' DD statementwas found after already having encountered another 'STEPCAT' DD statement in the same step.

DSS10082 "Syntax error; keyword was expected - found '&1'."

Explanation: The characters '&1' were found at the point in the statement where a keyword would havebeen expected.

76


Action: Possible causes of this error include typographical errors and omission of keyword names.

DSS10083 "Syntax error; ')' was expected."

Explanation: A right parenthesis ')' was required at this point in the statement to close a group that had beenopened with a left parenthesis ('(').

Action: Possible causes of this error are coding too many left parentheses, or too few rightparentheses.

DSS10084 "Syntax error; trying to rename '&1', but '*' required in '&2'. Must define both entryname and newnameas generic."

Explanation: To give an altered entry a newname, if you include generic names, you must define bothentryname and newname as generic.

Action: Refer to IBM BookManager Documentation (Title: DFSMS/MVS V1R5 Access Method Servicesfor the Integrated Catalog Facility, Doc #: SC26-4906-05, Ch.5.5.2 Optional Parameters).

DSS10085 "Misplaced statement; '&1' was not expected at this time."

Explanation: The '&1' statement, while acceptable in some contexts, may not be coded here.

Action: Possible causes of this error include omitting a prerequisite statement to the '&1' statement -for example, coding an 'ELSE' statement without coding its corresponding 'IF' statement, ormisspelling its corresponding prerequisite statement type name.

DSS10086 "Parameter '&1' may only appear once."

Explanation: The '&1' parameter, if it appears, may only be coded once on this statement.

DSS10087 "The first node of an entry namemay not be specified generically."

Explanation: Although this statement allows the entry name to be specified generically (that is, usingasterisks), there are restrictions on what may be specified. In particular, the high-level (first)nodemay not be specified generically. For example, the IDCAMS statement 'DELETE *.PROCLIB'is not permitted.

DSS10088 "Only one nodemay be specified generically in an entry name."

Explanation: Although this statement allows the entry name to be specified generically (that is, usingasterisks), there are restrictions on what may be specified. In particular, only one node cancontain an asterisk. For example, the IDCAMS statement 'DELETE SYS1.*.*.PROCLIB' is notpermitted.

DSS10089 "'*' cannot be preceded or followed by any other character when used in an entry name node."

Explanation: Although this statement allows the entry name to be specified generically (that is, usingasterisks), there are restrictions on what may be specified. In particular, an asterisk is used byitself as a node. The IDCAMS statement 'DELETE SYS1.PROC*B' is not permitted.

DSS10090 "Syntax error. First parameter of an OUTPUT statement must be four letter alphanumeric, or single '*'.'&1' was found."

77

System Messages

Explanation: For an OUTPUT statement, only the items shown are valid. The characters '&1' wereencountered, however.

Action: Possible causes of this message include typographical errors.

DSS10091 "Expected continuation line after comment continuation marker was not received."

Explanation: A statement ended with a marker indicating that continuation of a comment would follow.However, the next line did not contain the continuation of that comment.

DSS10092 "Priority must be from 1 to 15."

Explanation: The priority specified was outside the range of acceptable values (numbers from 1 to 15,inclusive).

Action: Specify a priority from 1 to 15.

DSS10093 "A JES2 /*OUTPUT continuation must be preceded by a valid /*OUTPUT statement."

Explanation: A JES2 /*OUTPUT statement with a valid codemust precede any JES2 /*OUTPUT continuationstatement.

DSS10094 "'//' (null) statement was found. Rest of &1 skipped."

Explanation: Because a null statement ('//') was found in the JCL member, all lines following it are consideredto be flushed, and will not be scanned, changed, or reformatted unless a valid JOB card isfound.

Action: This is consistent with the behavior if themember were to be submitted via the TSO 'SUBMIT'command, but PRO/JCL's behavior can be changed by modifying the TSOSUBMIT run-timesetting, if desired.

DSS10095 "'PROC' statement was expected; found '&1'."

Explanation: At this point in themember being scanned, a 'PROC' statement should have been found.Instead, the characters '&1' were found.

Action: Possible causes of this error includemisspelling 'PROC' as '&1', or omission of the PROCstatement altogether.

DSS10096 "PROC '&1' has no steps."

Explanation: Every PROC must contain at least one step. The PROC named '&1', however, contains no stepsat all.

DSS10097 "Parenthesis nesting of 3 or more is not allowed at column &1."

Explanation: The parenthesis nesting level reached 3when column &1 of the line was scanned. This is anerror, as parenthesis nesting levels of only 0, 1, and 2 are permitted here.

Action: Possible causes of this error include coding a left parenthesis where a right parenthesis wasintended.

DSS10098 "Mismatched ')' was found in column &1."

Explanation: The right parenthesis in column &1was not matched by a corresponding left parenthesis.

78


Action: Possible causes of this error include coding a right parenthesis where a left parenthesis wasintended, or coding too many right parentheses.

DSS10099 "Mismatched '(': closing ')' is missing."

Explanation: There is no closing parenthesis to match the indicated opening parenthesis.

Action: Possible causes include coding the wrong parenthesis where the other one was intended.

DSS10100 "Error was found in symbolic name format '&1'."

Explanation: The symbolic name '&1' must be 1 to 8 characters in length, and begin with an alphabetic ornational ('$','#','@') character. The remaining six characters can be alphanumeric or national.

DSS10101 "PROCstatement may not use reserved name '&1' as a symbolic name."

Explanation: '&1' is a valid parameter on the EXEC statement, and cannot be used as a symbolic name.

DSS10102 "DD '&1' has already been overridden. This DDwill be an addon."

Explanation: An attempt was made to override the DD named '&1' twice for the same step. The effect of thisis that the second 'override' will be treated as an 'addon', yielding possibly unexpected results.

DSS10103 "PROC '&1' was not found."

Explanation: PROC '&1' was not found in any available libraries.

Action: Check the JESPROC concatenations, FIRSTPROCLIB, and JCLLIB ORDER=.

DSS10104 "PROCnesting level is deeper than 15 for '&1'."

Explanation: IBM currently restricts PROC nesting to no more than 15 levels deep. When the PROC named'&1' was encountered, the PROC nesting level exceeded 15. In order to providemaximumvalidation in a single pass, PRO/JCL ignores this restriction and continues scanning anyway, onthe assumption that the nesting-level error will be corrected before the next re-scan.

DSS10105 "INCLUDE nesting level is deeper than 15 for '&1'."

Explanation: IBM currently restricts INCLUDE nesting to no more than 15 levels deep. When the INCLUDEnamed '&1' was encountered, the INCLUDE nesting level exceeded 15. In order to providemaximum validation in a single pass, PRO/JCL ignores this restriction and continues scanninganyway, on the assumption that the nesting-level error will be corrected before the next re-scan.

DSS10106 "'&1' exceeds the maximum of 255 volume serial numbers."

Explanation: Only 255 volume serial numbers can be specified for this statement. An attempt was made toprocess 256 or more volume serial numbers ('&1').

DSS10107 "Instream data found in a PROCor INCLUDE: DDNAME '&1'."

Explanation: While processing a PROC or an INCLUDE, instream data was found for DDNAME '&1'. Sinceinstream data must be processed by JES, and JES processing is finished before PROC orINCLUDE expansion takes place, instream data is not permitted within a PROC or an INCLUDE.

79

System Messages

DSS10108 "Duplicate '&1' DD statement."

Explanation: The DD statement '&1' has already been encountered for this step.

DSS10109 "Referback '&1' not valid: DDNAME '&2' not found."

Explanation: The indicated referback ('&1') is not valid because the DDNAME to which it refers ('&2') was notfound.

DSS10110 "Reference '&1' not valid: step '&2' not found."

Explanation: The indicated reference ('&1') is not valid because the step name to which it refers ('&2') was notfound.

DSS10111 "'&1' is not valid as used."

Explanation: In the context of the current statement, '&1' is not a valid keyword, positional parameter, orsubkeyword.

DSS10112 "Missing label on the '&1' statement."

Explanation: The '&1' statement being processed requires a label (a name). None was found.

DSS10113 "'IF' statement '&1' missing 'THEN'."

Explanation: JCL 'IF' statements require a 'THEN' clause. The 'IF' statement named '&1' does not have a'THEN' clause.

DSS10114 "A 'PROC' statement was found out of sequence."

Explanation: The 'PROC' statement was not found in its proper sequence. For example, a 'PROC' statementshould not be encountered while processing overrides for a step.

DSS10115 "A 'PROC' statement was found out of sequence."

Explanation: The 'PROC' statement was not found in its proper sequence. For example, a 'PROC' statementshould not be encountered while processing overrides for a step.

DSS10116 "PROC '&1' was found out of sequence within an instream PROC."

Explanation: While processing an instream PROC, another PROC ('&1') was encountered without a 'PEND'statement being found.

Action: Possible causes of this error include omitting the 'PEND' statement from a prior instream PROC.

DSS10117 "Required parameter 'PROC' or 'PGM' must precede all other parameters on EXEC statement."

Explanation: Although the (optional) 'PROC=' or 'PGM=' parameters on the EXEC statement are consideredto be keywords, they are special in that one or the other of them must appear first, before anyother keywords on the statement. This is so that the system can distinguish between theexecution of a PROC and the execution of a program, which have different requirements forwhat the remainder of the parameters are allowed to be. For example, 'EXECPGM=XYZZY,REGION=2M' is valid, but 'EXEC REGION=2M,PGM=XYZZY' is not.

Action: A possible cause of this error is misspelling 'PGM='.

80


DSS10118 "'PEND' found without matching 'PROC'."

Explanation: A 'PEND' statement was found for which no corresponding 'PROC' statement has yet beenencountered.

Action: Possible causes of this error includemisspelling the 'PROC' statement that was intended tocorrespond to this 'PEND' statement.

DSS10119 "Statement label '&1' exceeds 8 characters in length."

Explanation: Statement labels (names) can only be up to 8 characters in length. The statement namespecified ('&1') is longer than 8 characters.

Action: Ensure the statement name specified ('&1') is not longer than 8 characters.

DSS10120 "Statement label '&1' contains an improper character at position &2."

Explanation: Only uppercase alphabetic ('A'-'Z'), national ('@', '#', and '$'), and numeric ('0'-'9') characters areallowed in a statement name. The first character must be alphabetic or national. The characterat position &2 of '&1' is not valid.

DSS10121 "Statement label '&1' containsmore than 2 nodes."

Explanation: The statement label '&1' contains more than one period ('.'). The periods separate thestatement label into 'nodes'. Although statement labels are always allowed to have 2 nodes,they are never allowed to have 3 nodes.

In the case of 2-node statement labels, there are cases where only the last node is used forany meaningful purpose. For example, '//STEP1.S1 EXEC...' is valid, but will be treated thesame as '//S1 EXEC...'.

DSS10122 "PROCprocessing stopped because of a recursive execution of '&1'."

Explanation: PROC processing stopped because of a recursive execution of '&1'.

DSS10123 "Format error in 'IF' statement '&1'. Found '&2'; was expecting '&3'."

Explanation: The JCL 'IF' statement coded does not conform to the syntax rules for such statements.

Action: In particular, '&3' should have been coded instead of '&2'.

DSS10124 "Nomatching 'PEND' was found for PROC '&1'."

Explanation: The PROC called '&1' is missing its 'PEND' statement.

DSS10125 "In the 'IF' statement named '&1', stepname '&2' not valid as used."

Explanation: Either the stepname '&2' is not a syntactically-valid stepname, or too many words were codedbetween the 'IF' and its corresponding 'THEN'.

DSS10126 "In the 'IF' statement named '&1', no operand was found."

81

System Messages

Explanation: In the 'IF' statement named '&1', no operand was found. Possible causes of this error includecoding 'THEN' before finishing the comparison to be used by the 'IF' - for example, thestatement '// IF THEN' will cause this error message.

DSS10127 "In the 'IF' statement named '&1', a step namemust be specified with 'RUN'."

Explanation: In the 'IF' statement named '&1', an attempt was made to check whether a step had executedvia the 'RUN' keyword, but no step namewas provided.

Action: A step namemust be provided before the word 'RUN', separated by a period ('.') - example, '//IF STEP1.RUN THEN'.

DSS10128 "INCLUDE processing stopped because of a recursive include of '&1'."

Explanation: INCLUDE processing stopped because of a recursive include of '&1'.

DSS10129 "DDNAME reference to DD concatenation refers only to the first DD."

Explanation: The JCL DDNAME keyword has been used to refer to a DD concatenation. When the object of aDDNAME reference is a concatenation ofmultiple DDs, only the first DD in the concatenation isactually referenced. The first DD in the referenced concatenation is associated with thereferencing DD. The remaining (unlabeled) DDs in the referenced concatenation areconcatenated to the labeled DD immediately preceding the concatenation. Related IBMMessage IEF694I.

DSS10130 "Control Card limit of &1 exceeded for DD&2. Only &1 Control Cards will be displayed."

Explanation: The Control Card Table in the Run Time Settings is set to display a maximum of &1 Control Cardstatements for DD &2.

Action: Increase this number or delete the table entry to display all of the Control Card statements.

DSS10131 "In the 'IF' statement named '&1', '&2' is incompatible with '&3'."

Explanation: In the 'IF' statement named '&1', '&2' is incompatible with '&3'. There was a syntax error in theformat of the 'IF' statement named '&1'.

Action: Possible causes include incorrectly coding the number against which a return or ABEND code isto be compared.

DSS10132 "Possible unresolved symbolic '&1'."

Explanation: The symbolic named '&1' was unresolved. This will probably result in an additional syntax error.

DSS10133 "Overridden step '&1' not found in procedure '&2'."

Explanation: The attempt to override the step named '&1' in the PROC named '&2' was unsuccessful,because the PROC '&2' does not contain a step called '&1'.

DSS10134 "'IF' nesting level is deeper than 15 for '&1'."

Explanation: IBM currently restricts 'IF' statement nesting to no more than 15 levels deep. When the 'IF'statement '&1' was encountered, the 'IF' nesting level exceeded 15. In order to providemaximum validation in a single pass, PRO/JCL ignores this restriction and continues scanning

82


anyway, on the assumption that the nesting-level error will be corrected before the next re-scan.

DSS10135 "Override for DDNAME '&1' was specified out of order. Results are unpredictable."

Explanation: DDNAME '&1' represents a SYSIN DD statement.

Action: Overriding of SYSIN DD statements must be done in the same order that the correspondingSYSIN statements appear in the underlying PROC, due to JES restrictions.

DSS10136 "Symbolic '&1' was not used in procedure."

Explanation: The symbolic named '&1' was not referenced with the current PROC.

DSS10137 "In the 'IF' statement named '&1', return code '&2' is not valid; should be 0-4095."

Explanation: The 'IF' statement named '&1' attempts to test a return code against '&2'.

Action: The only valid values for a return code test on an 'IF' statement are numbers between 0 and4095, inclusive.

DSS10138 "Due to the position of DD '&1', it will be treated as an addon, not as an override."

Explanation: This attempt to override a SYSIN DD ('&1') will be treated as an 'addon' rather than as anoverride, because of its position in the JCL stream.

DSS10139 "Referback '&1' not valid; step '&2' was bypassed."

Explanation: The referback coded as '&1' is not valid because the step to which it refers, '&2', will have beenbypassed. Only steps that are not bypassed may be used in referbacks.

DSS10140 "Character '&1' at position &2 is not valid in referback."

Explanation: In the referback coded, the character '&1' at column &2makes the entire referback incorrect.

DSS10141 "Referback '&1' not valid; &2 is too many nodes."

Explanation: In the referback '&1', there are &2 nodes. This is more nodes than allowed by the operatingsystem.

Action: Possible causes include insertion of an extraneous period ('.') into the referback.

DSS10142 "In the 'IF' statement named '&1', there are unbalanced parentheses."

Explanation: The 'IF' statement named '&1' does not contain the same number of opening and closingparentheses, or the opening and closing parentheses do not occur in the correct order tomatch properly.

Action: Correct the number and/or arrangement of the parentheses in the statement.

DSS10143 "'IF' statement named '&1' has no matching 'ENDIF' statement."

Explanation: The 'IF' statement named '&1' does not have a corresponding 'ENDIF' statement to indicate thescope of the 'IF'.

Action: Possible causes includemisspelling the intended 'ENDIF' statement.

DSS10144 "'ELSE' statement named '&1' has no matching 'IF' statement."

83

System Messages

Explanation: The 'ELSE' statement named '&1' does not have a corresponding 'IF' statement.

Action: Possible causes for this error includemisspelling the 'IF' statement which was intended tomatch this 'ELSE' statement.

DSS10145 "'ENDIF' statement named '&1' has no matching 'IF' statement."

Explanation: The 'ENDIF' statement named '&1' does not have a corresponding 'IF' statement.

Action: Possible causes for this error includemisspelling the 'IF' statement which was intended tomatch this 'ENDIF' statement.

DSS10146 "'&1' has already been specified."

Explanation: The parameter '&1' has already been specified, and may not be specified again.

DSS10147 "'&1' may not be coded because it was already coded for a specific step."

Explanation: '&1' may not be coded for the procedure because it was already coded with a step name.

DSS10148 "'&1' may not be coded because it has already been coded for the procedure."

Explanation: The attempt to specify '&1' is not valid, because '&1' was found in the PROC already.

DSS10149 "'&1' is not a valid positional parm."

Explanation: The parameter you entered, '&1', is not valid.

Action: Possible causes of this error include omitting a required keyword, or misspelling the parameter.

DSS10150 "DDNAME '&1' not resolved on DDNAME parm."

Action: A 'DDNAME=' parameter was found on a DD statement which referred to the DDNAME '&1'.However, the DDNAME '&1' was not found.

DSS10151 "Missing or incorrect return code in the CONDparm. 0-4095 is valid."

Explanation: When the 'COND=' parameter is coded, the return codes to which it refers must be numbersbetween 0 and 4095, inclusive.

DSS10152 "Stepname '&1' is not valid in the CONDparm."

Explanation: Stepname '&1' is not valid in the COND parm. When the 'COND=' parameter is coded, the stepnames to which it refers must be syntactically-valid and existent within the JOB.

Action: Syntactically-valid stepnames are from 1-8 characters long; the first character must beuppercase alphabetic ('A'-'Z') or national ('@', '#', or '$'). The remaining characters must beuppercase alphabetic, national, or numeric ('0'-'9').

DSS10153 "Missing a valid comparison operator in the 'COND' parm."

Explanation: When the 'COND=' parameter is coded, the comparisons operators that are allowed are 'EQ','GE', 'GT', 'LE', 'LT', and 'NE'.

Action: Provide a valid comparison operator for the 'COND=' parameter.

DSS10154 "'COND' value '&1' not valid."

Explanation: The 'COND=' parameter coded specifies an incorrect value ('&1').

84


DSS10155 "'&1' dataset '&2' not found."

Explanation: The '&1' parameter was coded, but the dataset to which it refers, '&2', does not exist.

DSS10156 "'LIKE' dataset '&1' is not on a DASD volume."

Explanation: 'LIKE' dataset '&1' is not on a DASD volume.

DSS10157 "PROC '&1' excluded by user request."

Explanation: The PROC named '&1' was found in the PROC exclusion table. Processing of this PROC isbypassed per the exclusion request.

DSS10158 "'&1' reference to generation data group '&2' is not valid."

Explanation: The '&1' parameter was coded, which must refer to a dataset name, but instead referred to thegeneration data group '&2'.

Action: A generation data group base is not a dataset, and cannot be used as one in this context.

DSS10159 "DSN '&1' ignored for &2 because the name does not start with '&'."

Explanation: If a dataset name is specified on a &2 DD statement, in this case '&1', it must be a temporarydataset name (a dataset name that begins with an ampersand).

DSS10160 "Model DSCB '&1' not found in catalog."

Explanation: Themodel DSCB to which this statement refers, '&1', is not in the system catalog and istherefore unusable.

DSS10161 "'&1' is a GDG base. This is not allowed for model DSCB's."

Explanation: The reference to '&1' as a model DSCB is not valid because '&1' is not a dataset but is a GDGbase name.

Action: Only dataset names are allowed as model DSCB's.

DSS10162 "Excessive parameter '&1' found in the 'COND' parm."

Explanation: Excessive parameter '&1' found in the 'COND' parm. Related IBM message: IEF646I.

DSS10163 "Dataset '&1' on volume '&2' is not a DSCB and cannot be used as a model."

Explanation: Only datasets that reside on DASD volumes can be used for model DSCB's. The dataset '&1' onvolume '&2' is not a valid DSCB.

Action: Possible causes of this error include attempting to use a model DSCB that refers to a TAPEdataset.

DSS10164 "Referback '&1' not valid: OUTPUT statement '&2' not found."

Explanation: '&1' refers to an 'OUTPUT' statement named '&2', which does not exist in this JOB. Thereference is not valid.

DSS10166 "In the 'IF' statement named '&1', there is a missing value between '&2' and '&3'."

85

System Messages

Explanation: A parenthesized expression was found in the 'IF' statement named '&1', but no value wasspecified between '&2' and '&3'.

Action: Specify a value between '&2' and '&3'.

DSS10167 "'IF' statement named '&1' is missing a value before operator '&2' in column &3."

Explanation: At column &3 in the 'IF' statement named '&1', a value should have been specified before theoperator '&2'.

Action: Specify themissing value.

DSS10168 "'IF' statement '&1' is missing a value after operator '&2' in column &3."

Explanation: At column &3 in the 'IF' statement named '&1', a value should have been specified after theoperator '&2'.

Action: Specify themissing value.

DSS10170 "Dataset '&1' has a catalog entry type of &2. Catalog entry type of &3 was expected."

Explanation: Because of the way that the dataset named '&1' is used, it was expected to have the catalogentry type '&3'. However, '&1' actually has the catalog entry type '&2'.

DSS10171 "DDNAME '&1' exceeds DDNAME limit of 5."

Explanation: Only 5 'DDNAME=' parameters may be 'active' at a time in any given step. An 'active' parameteris one which has not yet been resolved.

Action: Any number of 'DDNAME=' parameters may be used in a step, as long as no more than 5 areever unresolved simultaneously.

DSS10172 "More than 255 'EXEC's in this JOB."

Explanation: There is a system-imposed limit of 255 steps in any JOB. This JOB exceeds that limit. In order toprovidemaximum validation in a single pass, PRO/JCL will continue to scan the steps, althoughOS/390would have flushed the JOB.

DSS10173 "Extraneous '&1' found in the 'COND' parm."

Explanation: The 'COND=' parameter has too many '&1' parameters coded.

DSS10174 "Found &1 tests in the 'COND' parm; 8 is the maximum allowed."

Explanation: Each 'COND=' parameter may specify only up to 8 conditional tests. In the statement beingprocessed, &1 tests were attempted.

DSS10176 "DD '&1' excluded at user request."

Explanation: The DD named '&1' was found in the DD exclusion table. Processing of this DD is bypassed perthe exclusion request.

DSS10177 "Allocation type or length is missing in SPACE parm."

Explanation: The first positional parameter of the SPACE parm must contain an allocation unit of TRK or CYLor a block or record length or ABSTR for specific tracks.

86


DSS10178 "Primary space missing in SPACE parm."

Explanation: The second positional parameter of the SPACE parm must contain the number of tracks,cylinders, blocks or records to be allocated.

DSS10179 "'$IAM' is unrecognized; IAM simulation processing is off."

Explanation: If you want to simulate IAM processing for this CLUSTER, set INTERFACES IAM=Y in your RTSmember.

DSS10180 "DDNAME reference to itself is treated as DDDUMMY."

Explanation: DDNAME reference to itself is treated as DD DUMMY.

DSS10181 "Duplicate temporary dataset name ('&1')."

Explanation: Duplicate temporary dataset name ('&1'). A temporary dataset with the same namewascreated in a prior step. The number of temporary datasets is dependent upon howmanyvolumes are available for a particular site.

DSS10182 "Expected comment continuation not found. Check column 72 on the previous line."

Explanation: Expected comment continuation not found.

Action: If the last line of a JCL statement contains a non-blank in column 72, then the next linemusthave a blank in column 3. This line is treated as a comment.

DSS10183 "Expected continuation not received. Column 3 is non-blank."

Explanation: All JCL continuation records must have a blank in position 3 and start on or before column 16.Either your continuation starts in column 3 or there is an extra comma at the end of theprevious line.

DSS10184 "Expected continuation not received. A NULL statement was found."

Explanation: // (null) statements signal the end of a JOB. However, the previous statement ended in acomma which signals a continuation.

DSS10185 "Quoted string continued beginning in column &1, but should begin in column 16 or later."

Explanation: Quoted strings are continued in JCL by leaving off the quote on the first line and thencontinuing the string in column 16 on the next line. This line was not blank in columns 3through 15.

DSS10186 "Expected continuation not received. Found non-JCL record."

Explanation: The previous JCL record ended in a comma. The next record did not start with //.

DSS10187 "Duplicate '&1' OUTPUT statement."

Explanation: The OUTPUT statement '&1' has already been encountered.

DSS10188 "DD&1 is ineligible because of its use as 'DDNAME=&1' on &2."

Explanation: DD &1 is ineligible for use as a referback because it is used as a forward reference (that is,DDNAME=&1) on &2.

87

System Messages

DSS10189 "&1 field contains a reference to a DDnot previously resolved."

Explanation: &1 field contains a reference to a DD not previously resolved.

DSS10190 "&1 is not valid. A procmay not specify a JOB level OUTPUT statement."

Explanation: &1 is not valid. A proc may not specify a JOB level OUTPUT statement.

DSS10191 "Unable to resolve symbolic '&1'."

Explanation: The symbolic named '&1' was unresolved. This will probably result in an additional syntax error.

DSS10192 "Maximum of 128 Output values exceeded. Found &1 values."

Explanation: Maximum of 128 Output values exceeded. Found &1 values.

DSS10193 "Unrecognized JES2 keyword '&1'."

Explanation: Unrecognized JES2 keyword '&1'.

DSS10194 "Unable to read &1 as a sequential dataset."

Explanation: Unable to read &1 as a sequential dataset.

DSS10195 "SYSINDDdelimiter '&1' was not found."

Explanation: The end of the JCL was reached because the assigned delimiter '&1' was not found.

DSS10196 "JCL not found in &1; no processing done."

Explanation: JCL not found in &1; no processing done.

DSS10197 "Symbolic &1 is coded more than once on &2 statement, only the first value is used."

Explanation: Symbolic &1 is coded more than once on &2 statement, only the first value is used.

DSS10198 "Symbolic &1 is coded more than once on &2 statement, only the last value is used."

Explanation: Symbolic &1 is coded more than once on &2 statement, only the last value is used.

DSS10199 "PARM.&1 has already been specified."

Explanation: The parameter PARM.&1 has already been specified.

DSS10200 "CONDparm error. Test of current step '&1' not allowed."

Action: Stepnames in COND parameters cannot reference the current jobstep/procstep name (e.g.//S1 EXEC PGM=X,COND=(0,EQ,S1)).

DSS10201 "'&1' is NOT allowed as the first two characters of the value for '&2'."

Explanation: Do not code '&1' as the first two characters for the value of '&2'.

DSS10202 "Value '&1' must be quoted or is quoted incorrectly."

Explanation: The value '&1' was entered without quotes where quotes are required, or quotes are used butare not properly balanced.

DSS10203 "Character '&1' is not valid outside of quotes."

88


Explanation: Character '&1' is not valid outside of quotes. All characters in a job control statement mustbelong to the character sets defined in the OS/390 MVS JCL User's Guide. RelatedIBM message: IEFC620I.

DSS10204 "Step name '&1' is a duplicate of a previous step name."

Explanation: Step name '&1' is a duplicate of a previous step name.

DSS10205 "JOB JCL unavailable, therefore step name '&1' could not be confirmed."

Explanation: JOB JCL unavailable, therefore step name '&1' could not be confirmed.

DSS10206 "'&1' must be coded after '&2'."

Explanation: '&1' must be coded after '&2'.

DSS10207 "ALTERwith '&1' parameter not valid for entry type of '&2'."

Explanation: On an ALTER statement only certain parameters are allowed depending on the type of entry.'&1' is not valid for entry type of '&2'.

DSS10208 "Dataset '&1' is not an IAM dataset."

Explanation: An IAM alternate indexmust be related to an IAM dataset. '&1' is not an IAM dataset.

DSS10209 "INCLUDE Member '&1' was not found."

Explanation: INCLUDEMember '&1' was not found in any available libraries.

Action: Check the JESPROC concatenations, FIRSTPROCLIB, and JCLLIB ORDER=.

DSS10210 "Incorrect use of ampersand(&). Possibly misspelled or unresolved symbolic."

Explanation: Incorrect use of ampersand(&). Possibly misspelled or unresolved symbolic.

DSS10211 "Use of AVGREC is ignored because of SPACE parameter &1, use record length instead."

Explanation: Use of AVGREC is ignored because of SPACE parameter &1.

Action: Use record length instead.

DSS10212 "Keyword JESDS is not valid after the first EXEC statement."

Explanation: The JESDS keyword of the OUTPUT statement is not valid after the first EXEC statement.

DSS10213 "The '&1' part of a DD&1 statement is coded within a symbolic value."

Explanation: The '&1' part of a DD &1 statement is coded within a symbolic value. When run under MVS thiswould result in themessage IEF465I and possibly a S0C7 abend.

DSS10214 "Improper use of parentheses for '&1'."

Explanation: Improper use of parentheses for '&1'. The value for '&1' contains parentheses in the wrongplaces, or is missing parentheses where they are needed.

DSS10215 "Left parenthesis missing following keyword '&1'."

89

System Messages

Explanation: Left parenthesis missing following keyword '&1'. The keyword '&1' is followed by otherkeywords which should be enclosed within parentheses.

DSS10216 "'&1' is not allowed as the first character of the value for '&2'."

Explanation: Do not code '&1' as the first character for the value of '&2'.

Action: First character must be a '&3'.

DSS10217 "JCL statement treated as comment due to continuation character in column 72 of previous statement."

Explanation: Comment continuation expected, but found possible new statement. If the last line of a JCLstatement contains a non-blank in column 72, then the next linemust have a blank in column 3and will be treated as a comment. Reformatting will be disabled for this statement.

DSS10218 "Possible missing comma, causing next line to be treated as comment."

Explanation: Comment continuation expected, but found possible additional keywords. If the last line of astatement contains a non-blank in column 72, then the next linemust have a blank in column 3and will be treated as a comment. Perhaps the previous line is missing a comma.

DSS10219 "Possibly missing '/' in column 2 of record '&1'."

Explanation: Possibly missing '/' in column 2 of record '&1'. Record treated as though '//' was coded incolumns 1 and 2.

DSS10220 "Catalog entry type &1 is not valid for IDCAMS DELETE."

Explanation: A&1 cannot be deleted independent of the CLUSTER.

Action: Specify the CLUSTER name on the DELETE statement to delete all components.

DSS10221 "Dataset &1 is not a valid JCLLIB. LRECLmust be 80 but was found to be &2."

Explanation: Dataset &1 is not a valid JCLLIB. LRECL most be 80 but was found to be &2.

DSS10222 "Dataset &1 is not a valid JCLLIB. RECFMmust be F or FB but was found to be &2."

Explanation: Dataset &1 is not a valid JCLLIB. RECFM must be F or FB but was found to be &2.

DSS10223 "Unable to find instream data for &1 DD *. Check for errors on previous instream data DD's."

Explanation: Unable to find instream data for &1 DD *. Check for errors on previous instream data DD's.

DSS10224 "The program (member) name cannot be found in this TSOCALL statement."

Explanation: The program (member) name is missing. The default program 'TEMPNAME' will be executed.

DSS10225 "TSOCALL statement requires a dataset name, or *, with a program (member) name."

Explanation: TSO CALL statement requires a dataset name, or *, with a program (member) name.

DSS10226 "The *(membername) on a TSOCALL statement must be unquoted."

Explanation: When '*' is used for dsname on a TSO CALL statement the string must be unquoted.

DSS10227 "Extraneous character(s) were found after the member name."

90


Explanation: Extraneous character(s) were found between the closing parenthesis and the end of datasetname.

DSS10228 "No closing quote found at end of dataset name."

Explanation: No closing quote found. The dataset name starts with a quote, but does not end with a quote.

DSS10229 "The dataset name cannot start with an open parenthesis."

Explanation: The dataset name cannot start with an open parenthesis. The dataset name cannot beenclosed in parenthesis.

DSS10230 "Value '&1' for &2 should have been &3."

Explanation: The value coded ('&1') is not valid for &2.

Action: The acceptable values that could have been coded are &3.

DSS10231 "Expected '=' or '(' following &1 found '&2'."

Explanation: Keyword &2 should have been followed by '=' or '('.

DSS10232 "All BLSR sub parameters must be within quotes."

Explanation: All BLSR sub parameters must be within quotes.

DSS10233 "The following parameters are mutually exclusive: &1."

Explanation: The &1 parameters cannot be coded together.

DSS10234 "The last node of an entry namemay not contain an '*'."

Explanation: Although this statement allows the entry name to be specified generically (that is, usingasterisks), there are restrictions on what may be specified. For example, the IDCAMS statementfor 'LISTCAT LEVEL (SYS1.*)' is not permitted.

DSS10235 "MASK is required if more than one node has an '*' or '%' specified in an entry name."

Explanation: Although this statement allows the entry name to be specified generically (that is, using asteriskor percent characters), there are restrictions on what may be specified. Multiple nodescontaining an mask character(* or %)must code theMASK parameter. For example, theIDCAMS statement 'DELETE SYS1.*.*.PROCLIB' is not permitted unless MASK parameter iscoded.

DSS10236 "MASK parameter is required when '*' or '%' precedes or follows any other character in an entry name."

Explanation: Although this statement allows the entry name to be specified generically (that is, using asteriskor percent characters), there are restrictions on what may be specified. In particular, a maskcharacter is embedded in a node. The IDCAMS statement 'DELETE SYS*.PROCLIB' is notpermitted unless MASK is coded.

DSS10237 "Symbolic substitution on record &1 resulted in a length of &2 which will cause an I/O error in z/OS."

Explanation: Symbolic substitution on record &1 resulted in a length of &2which will cause an I/O error inz/OS.

91

System Messages

DSS10238 "The steps in this proc will not be executed because of an EXPORT statement."

Explanation: The steps in this proc will not be executed because an EXPORT has been coded and a SETstatement is the first statement in the proc. Adding a PROC statement to cataloged proc &1willchange this behavior.

DSS10239 "&1 file sequences were specified for &2 volumes."

Explanation: The number of file sequences specified (&1) is not the same as the number of volumes specified(&2).

DSS10240 "MASK parameter is not allowed for a PDS member delete."

Explanation: MASK parameter is not allowed for a PDS member delete.

DSS10241 "Mask '**' is not allowed with any other characters in that node."

Explanation: Mask '**' is not allowed with any other characters in that node.

DSS10242 "CATALOG parameter is required if the first node is masked."

Explanation: CATALOG parameter is required if the first node is masked.

DSS10243 "Misplaced comma coded in the &1 field. Subparameter list not valid."

Explanation: Misplaced comma coded in the &1 field. Subparameter list not valid.

DSS10244 "Misplaced SCHEDULE statement. Only one is allowed."

Explanation: Only one SCHEDULE statement is allowed per JOB.

DSS10245 "SCHEDULE statement must immediately follow the JOB card."

Explanation: A SCHEDULE statement must immediately follow the JOB card.

DSS10246 "HOLDUNTLmust not be later than STARTBY."

Explanation: HOLDUNTL timemust not be later than STARTBY time.

DSS10247 "What appeared to be Substring parameters for a system symbol were ignored by the symbol resolutionprogram."

Explanation: What appeared to be Substring parameters for a system symbol were ignored by the symbolresolution program.

DSS10248 "PROCprior JES3MAIN statement not valid if PROCLIB is also on JCLLIB."

Explanation: PROC prior JES3MAIN statement not valid if PROCLIB is also on JCLLIB.

DSS10249 "PROCLIB in prior JES2 JOBPARM statement is not valid if PROCLIB is also on JCLLIB."

Explanation: PROCLIB in prior JES2 JOBPARM statement is not valid if PROCLIB is also on JCLLIB.

DSS10250 "Misplaced statement '&1' statement; No '&2' found to complete JOBSET/JOBGROUP."

Explanation: The '&1' statement was coded prior to the associated '&2' statement was coded.

DSS10251 "'&1' statement name '&2' does not match the coded '&3' name '&4'."

92


Explanation: '&1' statement name '&2' does not match the coded '&3' name '&4'. The correspondingstatement names must match.

DSS10252 "'&1' has already been coded for either a JOBGROUP/GJOB/JOBSET/SJOB statement. A unique '&2'statement name is required."

Explanation: '&1' statement requires a unique statement name.

DSS10253 "'&1' statement requires a unique statement name and start in column 3, must be 1 through 8alphanumeric or national characters."

Explanation: '&1' statement requires a unique statement name and start in column 3, must be 1 through 8alphanumeric or national characters.

DSS10254 "The NAME '&1' coded on the AFTERor BEFORE statement must match a GJOB or JOBSETstatement name. Maximum of 10 namesmay be referenced."

Explanation: The NAME '&1' coded on the AFTER or BEFORE statement must match a GJOB or JOBSETstatement name. Maximum of 10 names may be referenced.

DSS10255 "The NAME keyword is required to be specified first for the AFTERand BEFORE statements."

Explanation: The NAME keyword is required to be specified first for the AFTER and BEFORE statements.

DSS10256 "No GJOB/SJOB statements coded within the JOBGROUP/ENDGROUP statements."

Explanation: No GJOB/SJOB statements coded within the JOBGROUP/ENDGROUP statements.

DSS10257 "No Operands or Commentsmay be coded."

Explanation: No Operands or Comments may be coded.

DSS10258 "Format error. Found '&1'; was expecting '&2'."

Explanation: The JES Execution Control statement coded does not conform to the syntax rules for suchstatements. In particular, '&2' should have been coded instead of '&1'.

DSS10259 "Misplaced statement; '&1' was not expected when coding JES Execution Control statements."

Explanation: The '&1' statement, while acceptable in some contexts, may not be coded here. Possible causesof this error include omitting a prerequisite statement to the '&1' statement - for example,coding an 'ENDGROUP' statement without coding its corresponding 'JOBGROUP' statement, ormisspelling its corresponding prerequisite statement type name.

DSS10260 "For the '&1' parm coded, there are unbalanced parentheses."

Explanation: "The '&1' parm does not contain the same number of opening and closing parentheses, or theopening and closing parentheses do not occur in the correct order to match properly.

DSS10261 "'&1' is incompatible with '&2'."

Explanation: '&1' is incompatible with '&2'.There was a syntax error in the format of the 'WHEN or ERROR'parm. Possible causes include incorrectly coding the number against which a return or ABENDcode is to be compared.

93

System Messages

DSS10262 "Incorrect context coded for either ABENDCC, ABEND, RCor RUN."

Explanation: Incorrect context coded for either ABENDCC, ABEND, RC or RUN.

DSS10263 "Incorrect 'WHEN' or 'ERROR' parm has a conditional keyword '&1' coded."

Explanation: Incorrect 'WHEN' or 'ERROR' parm has a conditional keyword '&1' coded.

DSS10264 "Coded Return code '&1' is incorrect; should be 0-4095."

Explanation: Coded Return code '&1' is incorrect; should be 0-4095.

DSS10265 "'&1' statement is missing an '&2' statement with the name of '&3'."

Explanation: '&1' statement is missing an '&2' statement with the name of '&3'.

DSS10266 "'WHEN' or 'ERROR' parmmissing value between '&1' and '&2'."

Explanation: A parenthesized expression was found in the 'WHEN' or 'ERROR' parm, but no value wasspecified between '&1' and '&2'.

DSS10267 "'WHEN' or 'ERROR' parmmissing a value before operator '&1' in column &2."

Explanation: At column &2 in the 'WHEN' or 'ERROR parm', a value should have been specified before theoperator '&1'.

DSS10268 "'WHEN' or 'ERROR' parm '&1' is missing a value after operator '&2' in column &3.

Explanation: At column &3 in the 'WHEN' or 'ERROR' parm, a value should have been specified after theoperator '&2'.

DSS10269 '&1' has already been coded for either a GJOB/JOBSET/SJOB statement. A unique '&2' statementname is required."

Explanation: '&1' statement requires a unique statement name.

DSS10270Missing label on the NOTIFY statement.

Explanation: Missing label on the NOTIFY statement.

DSS10271 "Must code a matching ENDSET statement for the prior JOBSET statement '&1'. JOBSET nesting is notvalid."

Explanation: Must code a matching ENDSET statement for the prior JOBSET statement '&1'. JOBSET nestingis not valid.

DSS10272 "'&1' was already coded on a CONCURRENT or GJOB statement."

Explanation: '&1' was already coded on a CONCURRENT or GJOB statement.

DSS10273 "Name '&1' coded on a CONCURRENT statement but no matching GJOB found."

Explanation: Name '&1' coded on a CONCURRENT statement but no matching GJOB found.

DSS10280 "Path &1 cannot be cataloged in &2. It must be in the same catalog as &3."

94


Explanation: This is caused by attempting to catalog a VSAM PATH in a different catalog from the relatedVSAM dataset (example, when defining an ALIAS catalog entry).

DSS10290 "No recognized &1 statement was found in the first &2 records. &1 processing stopped for this step."

Explanation: No recognized &1 statement was found in the first &2 records. &1 processing stopped for thisstep.

DSS10295 "IDCAMS DEFINE/ALTERLIMIT parm is &1 when EXTENDED is not coded."

Explanation: IDCAMS DEFINE/ALTER LIMIT parm is &1when EXTENDED is not coded.

DSS10296 "Parameters &1 and &2 can not both have values."

Explanation: Parameters &1 and &2 can not both have values.

DSS10300 "User requested same record to be changed 2 different ways. Second change ignored. First='&1';second='&2'."

Explanation: User requested same record to be changed 2 different ways. Second change ignored. First='&1';second='&2'.

DSS10299 "BYPASSNONJCL turned ON; First record recognized as NONJCL in &1, all following records areignored."

Explanation: BYPASSNONJCL turned ON and NONJCL input will get error message DSS10299 and Return codeas 1.BYPASSNONJCL turned OFF and NONJCL input will get DSS10196& DSS01711with return code8.

DSS10301 "2 user-requested changes resulted in extra records. Second change ignored. Extra record is '&1'."

Explanation: 2 user-requested changes resulted in extra records. Second change ignored. Extra record is '&1'.

DSS10400 "The path namemust begin with a '/'."

Explanation: The first character of the PATH parameter must be a slash ('/').

DSS10401 "Path or file not found."

Explanation: The specified path or file does not exist on this system.

DSS10402 "The path cannot be created because it already exists."

Explanation: The specified path already exists on this system.

DSS10403 "The path cannot be deleted because it does not exist or was deleted by a previous step."

Explanation: The specified path does not exist on this system or it was deleted by a step in the JCL beingscanned.

DSS10404 "You do not have permission to access this path."

Explanation: IBM's BPX1STA routine returned 111, which indicates that you do not have access to this path.

DSS10405 "The path name is too long."

95

System Messages

Explanation: The specified path name is longer than allowed by z/OS.

DSS10406 "Unexpected RC from BPX1STA =&1. Please call ASG customer support."

Explanation: Unexpected RC from BPX1STA = &1.


DSS10407 "An error in the symbolics used in the path name caused a loop."

Explanation: An error in the symbolics used in the path name caused a loop.

DSS10408 "DJ0RPATHparm block length error. Please call ASG customer support."

Explanation: DJ0RPATH parm block length error.


DSS10409 "A node in the path name is not a directory."

Explanation: A node in the path name is not a directory BPX1STA RC=&1, Rsn=&2.

DSS10410 "File system not started. Check the first node. BPX1STA RC=&1, Rsn=&2."

Explanation: File system not started. Check the first node. BPX1STA RC=&1, Rsn=&2.

DSS10411 "Path parameter is incorrect. BPX1STA RC=&1, Rsn=&2."

Explanation: Path parameter is incorrect. BPX1STA RC=&1, Rsn=&2.

DSS10412 "A directory in the path name was not found."

Explanation: A directory in the path namewas not found BPX1STA RC=&1, Rsn=&2.

DSS11001 "Improper continuation for &1 control card."

Explanation: The &1 control card does not properly specify its continuation.

DSS11002 "Possible creation of an improper member name: '&1'."

Explanation: Due to the continuation rules for this utility control statement, it is possible that the namebeing created, '&1', is not what the user intended.

Action: Verify that the name '&1' is really what was intended.

DSS11003 "Parameter '&1' should not be split across lines."

Explanation: Parameter '&1' was split across lines.

Action: Due to the continuation rules for this utility control statement, it is best to split linesimmediately after commas.

DSS11004 "A non-blank character is required in the continuation column for a line ending with a comma."

Explanation: When this utility control statement ends with a comma, a valid non-blank character is requiredin the continuation column to indicate to the utility that the next line is a continuation of thecurrent statement.

DSS11005 "Improper continuation of SORT statement."

96


Explanation: The SORT statement continuation must begin in column 16 in this case.

DSS11006 "This '&1' statement will be ignored; a '&2' statement has already been processed."

Explanation: DFSORT ignores duplicate statements, therefore this '&1' statement will be ignored.

DSS11007 "Sequential output dataset '&1' must have variable spanned RECFM."

Explanation: If the output dataset for IEBCOPY is sequential, it must have record format variable spanned.The RECFM of dataset '&1' is not variable spanned.

DSS11008 "Dataset for '&1' is not a PDS or a sequential file with variable spanned records."

Explanation: The dataset allocated for '&1' must either be a partitioned dataset ('PDS') or a sequentialdataset whose record format is variable spanned ('VS').

DSS11009 "Unable to associate '&1' to a copy operation."

Explanation: The '&1' specification is not valid because no 'COPY' operation has yet been initiated.

Action: Possible causes of this error includemisspelling the 'COPY' statement or omitting it altogether.

DSS11010 "Cannot specify 'SELECT' and 'EXCLUDE' in the same operation."

Explanation: Although both 'SELECT' and 'EXCLUDE' are valid ways of specifying members to be copied, it isnot valid to use both 'SELECT' and 'EXCLUDE' in the same 'COPY' operation.

DSS11011 "Cannot specify duplicate member name for select/exclude/rename: '&1'."

Explanation: Themember name '&1' has already been 'SELECT'ed or 'EXCLUDE'd in the current 'COPY'operation and may not be specified again.

DSS11012 "Input DDNAME specified is not valid."

Explanation: The input DDNAME specified was not valid. Valid DDNAME's are 1-8 characters in length; thefirst character must be uppercase alphabetic ('A'-'Z') or national ('@', '#', or '$'). All remainingcharacters must be uppercase alphabetic, national, or numeric ('0'-'9'). Also, the input DDNAMEmust be allocated in the current step.

DSS11013 "Valid OUTDDwas not specified for this operation."

Explanation: The output DDNAME specified was not valid. Valid DDNAME's are 1-8 characters in length; thefirst character must be uppercase alphabetic ('A'-'Z') or national ('@', '#', or '$'). All remainingcharacters must be uppercase alphabetic, national, or numeric ('0'-'9'). Also, the outputDDNAMEmust be allocated in the current step.

DSS11014 "Incomplete list of values in the SORT FIELDS parameter."

Explanation: Incomplete list of values in the SORT FIELDS parameter.

DSS11015 "Position or length '&1' has an invalid displacement for type 'CH'."

Explanation: Position or length '&1' has an invalid displacement for type 'CH'. Related IBM message:ICE018A.

Action: If the position or length contains a decimal position it must be .0 for the data type CH.

97

System Messages

DSS11016 "'&1' will be copied.The member named '&1' will be copied to the output dataset."

Explanation:

DSS11017 "'&1' will be copied and renamed.The member named '&1' will be copied and renamed."

Explanation:

DSS11018 "'&1' will not be replaced in the output dataset."

Explanation: Because themember named '&1' already exists in the output dataset and replacement was notrequested, themember will not be copied, and will not replace the like-named member alreadyin the output dataset.

DSS11019 "Member '&1' was selected but was not found in any input dataset."

Explanation: Themember named '&1' was requested to be copied, but it is not in the input datasetsallocated to this step; therefore, this member will not appear in the output dataset.

DSS11020 "Duplicate symbol name: &1."

Explanation: The SORT symbol '&1' has already been added.

DSS11021 "Copy selected from: '&1'."

Explanation: Themembers explicitly 'SELECT'ed will be copied from DDNAME '&1'.

DSS11022 "Copy non-excluded from: '&1'."

Explanation: Themembers not explicitly excluded will be copied from DDNAME '&1'.

DSS11023 "Copy all from: '&1'."

Explanation: All themembers will be copied from DDNAME '&1' (no 'SELECT's or 'EXCLUDE's were found).

DSS11024 "to: '&1'."

Explanation: Themembers will be copied to DDNAME '&1'.

DSS11025 "member: '&1'."

Explanation: Themember named '&1' is being copied.

DSS11026 "'INDD' is not allowed for an ALTERMODoperation."

Explanation: The 'ALTERMOD' operation does not support specification of the 'INDD' parameter.

DSS11027 "Rename/replace not allowed with ALTERMODoperation."

Explanation: The 'ALTERMOD' operation does not support specification of rename and/or replace.

DSS11028 "Operation was not performed due to an error in subsequent statement."

Explanation: Amodifier specified on a later statement, such as 'SELECT' or 'EXCLUDE', was in error. Therefore,the entire operation was bypassed.

DSS11029 "Replace specifier should be 'R': '&1' was found instead."

98


Explanation: The character that requests replacement of like-named members in the output dataset issupposed to be specified as 'R'. Instead, '&1' was found.

DSS11030 "Rename/replace is not allowed with EXCLUDE."

Explanation: If an 'EXCLUDE' statement is specified, rename and/or replace specifications are not valid.

DSS11031 "&1 detected End Of File mark in SYSIN. Subsequent records will be ignored."

Explanation: &1 detected End Of File mark in SYSIN. Subsequent records will be ignored.

DSS11032 "Operator '&1' is not valid with format '&2'."

Explanation: Operator '&1' is not valid with format '&2'.

DSS11033 "A format is required for this comparison."

Explanation: A format is required for this comparison.

DSS11034 "Expecting a format but found '&1' at column &2."

Explanation: Expecting a format but found '&1' at column &2.

DSS11035 "Expecting a number but found '&1' at column &2."

Explanation: Expecting a number but found '&1' at column &2.

DSS11036 "Expecting a comparison operator but found '&1' at column &2."

Explanation: Expecting a comparison operator but found '&1' at column &2.

DSS11037 "Null value is not allowed in INCLUDE/OMIT statement. Parsing stopped."

Explanation: Null value is not allowed in INCLUDE/OMIT statement. Parsing stopped.

DSS11038 "Expecting an 'AND' or 'OR' but found '&1' at column &2."

Explanation: Expecting an 'AND' or 'OR' but found '&1' at column &2.

DSS11039 "Comparison is not complete near column &1."

Explanation: Comparison is not complete near column &1.

DSS11040 "Parameter 'COND' is missing from INCLUDE/OMIT statement."

Explanation: Parameter 'COND' is missing from INCLUDE/OMIT statement.

DSS11042 "A valid FORMAT was expected near column &1 found &2."

Explanation: A valid FORMAT was expected near column &1 found &2.

DSS11043 "NOSORT ORMERGE CONTROL STATEMENT was found."

Explanation: NO SORT ORMERGE CONTROL STATEMENT was found.

DSS11044 "EXCLUDE is not allowed with a COPYGRP statement."

Explanation: EXCLUDE is not allowed with a COPYGRP statement.

DSS11045 "RECFM of dataset '&1' will be changed to VS."

99

System Messages

Explanation: The UNLOAD process will change the record format of '&1' to VS.

DSS11046 "Dataset '&1' is not an unloaded dataset."

Explanation: Dataset '&1' is not an unloaded dataset.

DSS11047 "Improper character '&1' found in symbolic name."

Explanation: Improper character '&1' found in symbolic name.

DSS11048 "Error in symbol name."

Explanation: A valid symbol namewas not found in this statement.

DSS11049 "Records for &1(&2) are in ISPF PACKED format."

Explanation: ISPF EDIT command PACK ONwas previously specified for &1(&2).

Action: Use PACK OFF while in an ISPF EDIT session to unpack this file.

DSS11050 "Unrecognized keyword '&1'. Assumed to be a valid command or program."

Explanation: The keyword '&1' is not a recognized DB2 command or keyword. It is assumed that this is avalid TSO command, CLIST name, REXX EXEC name, or program name on the system.

DSS11051 "Unrecognized '&1' keyword '&2'."

Explanation: The '&1' command does not have a keyword named '&2'. Check the spelling of '&2'.

DSS11052 "'&2' is an incorrect value for '&1'."

Explanation: '&1' does not accept '&2' as a valid value.

DSS11053 "Location specifier '&1' not valid."

Explanation: The location specifier '&1' is not correct.

Action: Check the spelling.

DSS11054 "Member &1 was not found in either LIBRARY() or DBRMLIB DDdata sets."

Explanation: Member &1was not found in either data sets specified by the LIBRARY() or DBRMLIB DD.

DSS11055 "Package specifier '&1' not valid."

Explanation: The package specifier '&1' is not correct.

Action: Check the spelling.

DSS11056 "Extraneous program information is ignored - '&1'."

Explanation: DB2will only execute the first program specified and will ignore - '&1'.

DSS11066 "A period must precede the version specifier."

Explanation: The version specifier must be preceded with a period ('.').

DSS11076 "The number of member names encountered exceeds that specified by the 'MAXNAME' parameter."

100


Explanation: The 'MAXNAME' parameter indicates themaximum number ofmember names that can bespecified on this statement. That number was exceeded.

DSS11077 "The number of IDENT parameters encountered exceeds that specified by the 'MAXGPS' parameter."

Explanation: The 'MAXGPS' parameter indicates themaximum number of 'IDENT' parameters that can bespecified on this statement. That number was exceeded.

DSS11078 "The number of FIELD parameters encountered exceeds that specified by the 'MAXFLDS' parameter."

Explanation: The 'MAXFLDS' parameter indicates themaximum number of 'FIELD' parameters that can bespecified on this statement. That number was exceeded.

DSS11079 "Field &1 causes the length of literals processed to exceed that specified by the 'MAXLITS' parameterby &2."

Explanation: The 'MAXLITS' parameter indicates themaximum total length of literals that can be specified onthis statement. Field #&1 caused that maximum to be exceeded by &2.

DSS11080 "The previousMEMBER statement needs a record identifier."

Explanation: There was no record identifier ('IDENT') on the previous 'MEMBER' statement.

Action: The record identifier is required.

DSS11081 "No value was specified for the RECORDFIELD parameter."

Explanation: The RECORD FIELD parameter must contain a value list but no value list was specified.

DSS11082 "Syntax error; '(' was found following a keyword and an equal sign(=)."

Explanation: An equal sign(=) or a right parenthesis must be coded after a keyword.

DSS11084 "'MULTIIN' parmmust be specified when coding '&MULTIINDD'"

Explanation: "'MULTIIN' parm must be specified when coding '&MULTIINDD'"

DSS11085 "Continuation must start in column 16: was found in &1."

Explanation: The continuation column for this type of statement is 16. Instead, the continued line began incolumn &1.

DSS11086 "The '&1' statement may not be specified when using the SYNCSORT 'MULTIIN' facility."

Explanation: The '&1' statement may not be specified when using the SYNCSORT 'MULTIIN' facility.

DSS11087 "'&MULTIINDD' may not be specified on the '&1' control statements."

Explanation: '&MULTIINDD' may not be specified on the '&1' control statements.

DSS11088 "Connection to '&1' attempted while already connected to '&2'."

Explanation: Simultaneous connection to '&1' and '&2' is not permitted. The connection to '&1' must bedropped before the connection to '&2' can bemade.

DSS11089 "TSOwill append the userid to '&1' which is not enclosed in quotes."

101

System Messages

Explanation: TSO appends the userid as the high level qualifier for catalog entry names that are not enclosedin quotes.

DSS11090 "Comment terminator not found."

Explanation: A comment was found but not terminated within the statement.

DSS11091 "Error(s) possibly caused by unterminated comment."

Explanation: The error(s) were possibly caused by an unterminated comment.

DSS11092 "No closing quote was found in this statement."

Explanation: An opening quote was encountered for which no matching closing quote was found.

DSS11093 "Comment terminator not found."

Explanation: A comment was found but not terminated within the statement.

DSS11094 "Embedded comment found within a comment."

Explanation: A comment was found in a comment; possibly unterminated.

DSS11095 "Operand field does not terminate in a comma or blank. The previous line is a comment."

Explanation: Because the 'operand' field did not end with a comma or a blank, the previous line will betreated as a comment. It is unlikely that this is what was intended.

Action: Check the statement carefully, especially noting whether it unintentionally flows beyondcolumn 72.

DSS11096 "MASK parameter is required for this data set specification."

Explanation: MASK parameter is required for this data set specification.

Action: Check the statement and make sure if the data set specification has MASK parameter.

DSS11097 "All membersmatching &1 will be deleted."

Explanation: All members matching &1will be deleted.

DSS11098 "Member namemay not be specified with generically specified data sets."

Explanation: Member namemay not be specified with generically specified data sets.

DSS11099 "Member name '&1' is not valid."

Explanation: Member name '&1' is not valid.

DSS11100 "JES3 '&1' statement cannot be continued."

Explanation: JES3 '&1' statement cannot be continued.

DSS11101 "JES3 'DATA SET' statement on line '&1' was coded without an 'ENDDATASET' statement."

Explanation: JES3 'DATA SET' statement on line '&1' was coded without an 'ENDDATASET' statement.

DSS11102 "JES3 '&1' statement was coded after '&2' statement."

Explanation: The JES3 '&1' statement cannot be coded after a JES3 '&2' statement has been coded.

102


DSS11103 "Expected continuation of JES3 '&1' statement on line '&2' was not received."

Explanation: Expected continuation of JES3 '&1' statement on line '&2' was not received.

DSS11104 "The JES3 '&1' command cannot be coded in JCL."

Explanation: The JES3 '&1' command cannot be coded in JCL.

DSS11105 "An 'NJB' or 'JOB' statement must immediately follow the JES3 'ROUTE XEQ' statement."

Explanation: An 'NJB' or 'JOB' statement must immediately follow the JES3 'ROUTE XEQ' statement.

DSS11106 "An NJB statement must follow a //*ROUTE XEQ statement in a job submitted through TSO."

Explanation: The 'JOB' keyword in the JOB statement following the JES3 //*ROUTE XEQ statement should becoded as 'NJB' for jobs submitted through TSO. JES3will change the 'NJB' to 'JOB' during itsprocessing of the JOB stream.

DSS11107 "Improper JES3 '&1' statement format coded. Parameter '&2' was coded in column &3; it was expectedin column &4."

Explanation: Improper JES3 '&1' statement format coded. Parameter '&2' was coded in column &3; it wasexpected in column &4.

DSS11108 "The '&1' keyword coded on the next record was changed to '&2'."

Explanation: The '&1' keyword coded on the next record was changed to '&2'.

DSS11109 "RESTART step '&1' not found."

Explanation: The step name '&1' specified as the target of a RESTART= parameter does not exist in this JOB.

DSS11110 "'SYSCHK' DD is required for restart checkpoint '&1'."

Explanation: 'SYSCHK' DD is required for restart checkpoint '&1'.

DSS11111 "Comma not coded in column &1 of '&2' statement."

Explanation: Comma not coded in column &1 of '&2' statement.

DSS11112 "Generic request not valid with member name."

Explanation: Generic request not valid with member name.

DSS11113 "Member name is required in NEWNAME when specified in ALTER target."

Explanation: Member name is required in NEWNAMEwhen specified in ALTER target.

DSS11114 "Cannot change both dataset name andmember name at the same time."

Explanation: Although this statement may be used to change either the dataset name or themember name,it is not valid to attempt to change both the dataset name and themember namesimultaneously. Two statements must be coded to accomplish this.

DSS11115 "Preceding record(s) from '&1' ignored; processing begins with the following JOB statement."

103

System Messages

Explanation: Because themember does not start with a JOB statement, all lines will be flushed until a validJOB card is encountered. At that point, validation will begin.

Action: Specify 'Y' for Run-Time Option TSO Submit to generate a JOB card if a JOB card does not exist.

DSS11116 "A ')' was found in column 1 of line &1. This member is assumed to be an ISPF skeleton and skipped."

Explanation: A ')' was found in column 1 of line &1. This member is assumed to be an ISPF skeleton andskipped.

DSS11117 "JES3 SIGNONstatement requires the work-station-name to start in column 16."

Explanation: JES3 SIGNON statement requires the work-station-name to start in column 16.

DSS11118 "JES3 SIGNONstatement requires the remote job processing password to start in column 25."

Explanation: JES3 SIGNON statement requires the remote job processing password to start in column 25.

DSS11119 "JES3 SIGNONstatement requires the current work station password to start in column 35."

Explanation: JES3 SIGNON statement requires the current work station password to start in column 35.

DSS11120 "Restart step '&1' was not found."

Explanation: The step name '&1' specified by a parameter to &2 does not exist in this JOB.

DSS11121 "All record(s) from '&1' ignored; no valid JOB statement found."

Explanation: Because themember does not contain a valid JOB statement, all records were ignored.

Action: Specify 'Y' for Run-Time Option TSO Submit to generate a JOB card if a JOB card does not exist.

DSS11122 "Ampersand(&) at position &1 of DSN&2 is not valid. Possible unresolved symbolic."

Explanation: Ampersand(&) at position &1 of DSN&2 is not valid. Possible unresolved symbolic.

DSS11123 "Ampersand(&) in member name &1 is not valid. Possible unresolved symbolic."

Explanation: Ampersand(&) in member name&1 is not valid. Possible unresolved symbolic.

DSS11124 "Value '&1' is missing quotes or contains an unresolved symbolic."

Explanation: Value '&1' is missing quotes or contains an unresolved symbolic.

DSS11125 "Value '&1' should have been at least '&2'."

Explanation: Value '&1' is too small. It should have been at least '&2'.

DSS11126 "JES3 requires a value for the '&1' parameter."

Explanation: JES3 requires a value for the '&1' parameter. A null value is not allowed.

DSS11127 "JOBRC step '&1' not found."

Explanation: The step name '&1' specified as the target of a JOBRC= parameter does not exist in this JOB.

DSS11180 "Value '&1' should have been &2. Possibly caused by an unresolved symbolic."

Explanation: The value coded ('&1') is not valid. The acceptable values that could have been coded are &2.Possibly caused by an unresolved symbolic.

104


DSS11150 "&1 requires a PARM."

Explanation: No PARM was given for the invocation of &1.

DSS11151 "Not enough subparameters in PARM for DFSRRC00 (IMS)."

Explanation: Theremust be at least 2 subparameters in the PARM for DFSRRC00 (IMS).

DSS11152 "&1 is not within this DBD."

Explanation: &1 is not within this DBD.

DSS11153 "&1 is not within this PSB."

Explanation: &1 is not within this PSB.

DSS11154 "&1 is before release 3.1 and not supported."

Explanation: &1 is before release 3.1 and not supported.

DSS11155 "PSB '&1' has no DBDnames."

Explanation: PSB '&1' has no DBD names.

DSS11156 "DBD '&1' not found."

Explanation: DBD '&1' not found.

DSS11157 "'&1' is not a valid &2."

Explanation: '&1' is not a valid &2.

DSS11158 "No datasets specified for IMSACBDSNS."

Explanation: No datasets specified for IMSACBDSNS.

DSS11159 "Unable to find &1 '&2'."

Explanation: Unable to find &1 '&2'.

DSS11160 "First parm for DFSRRC00 (&1) is not correct."

Explanation: First parm for DFSRRC00 (&1) is not correct.

DSS11161 "&1 length is incorrect for parm &2. The length must be &3."

Explanation: The length specified for parm '&2' is incorrect.

DSS11162 "'&1' Value is incorrect for parm &2. The value must not be '&3'."

Explanation: The value specified for parm &2 is incorrect.

DSS11163 "IMS application program not specified."

Explanation: IMS application program not specified in the DFSRRC00 parm field.

DSS11200 "Specified volume '&1' not found in any allocated DD."

105

System Messages

Explanation: The volume '&1' must be allocated to the step via some DD statement. No DD statement wasfound in this step that pointed to the volume '&1'.

DSS11201 "Specified CVOL '&1' not found in any allocated DD."

Explanation: The CVOL '&1' must be allocated to the step via some DD statement. No DD statement wasfound in this step that pointed to the CVOL '&1'.

DSS11300 "'&1' is not a recognized DFSMSDSS statement name."

Explanation: While processing DFSMSDSS statements, the statement '&1' was encountered. This is not arecognized DFSMSDSS statement name.

DSS11311 "Asterisk at position &1 of node '&2' of DSN '&3' is misplaced."

Explanation: Asterisk at position &1 of node '&2' of DSN '&3' is misplaced. It may only be used as the firstand/or last character of the qualifier.

DSS11312 "Quote at the end of '&1' is mismatched."

Explanation: An extraneous quote was found at the end of '&1'. A quotemay bemissing from the beginningof '&1'.

DSS11400 "'&1' is not a recognized DB2 utility statement name."

Explanation: While processing DB2 utility statements, the statement '&1' was encountered. This is not arecognized DB2 utility statement name.

DSS20000 "Dataset '&1' was allocated to DDNAME '&2'."

Action: The dataset named '&1' has been allocated to the DD statement identified by '&2' (which maybe part of a concatenation).

DSS20001 "Member '&1' was not found in dataset '&2'."

Explanation: The dataset named '&2' does not contain themember '&1'.

DSS20002 "DDNAME '&1' was not found in TIOT."

Explanation: The DDNAME '&1' was not allocated to this step.

DSS20003 "DDNAME '&1' is already allocated."

Explanation: DDNAME '&1' is already allocated. Although the second and subsequent allocations willsucceed, the datasets specified in these allocations will not be used by the processing programunless it has been coded to expect this situation (which is very unlikely).

Deallocation will succeed for these datasets, possibly resulting in adjustments to thecatalog or VTOC entries.

DSS20004 "DCB was not opened for input: '&1'."

Explanation: This program attempted to read from DD &1, but the DD was not opened for input.

106


DSS20005 "DCB was not opened for output for DDNAME '&1'."

Explanation: This program attempted to write to DD &1, but the DD was not opened for output.

DSS20006 "Member '&1' was not found."

Explanation: Themember '&1' does not exist in this dataset. It may have been deleted by a previous step orJOB, or it may have been misspelled. If this is a PGM=, then the program cannot be found inthe LPA, LINKLIST, or a STEPLIB or JOBLIB.

DSS20007 "Cannot open dataset '&1' with DSORG '&2'; because DSORG is '&3'."

Explanation: This program expected dataset '&1' to have a DSORG of '&2'. However, dataset '&1' actually hasa DSORG of '&3'. This can be because of a DSORG parameter on the DD statement, the DSORGof the dataset itself, or SMS may have set the DSORG.

DSS20008 "Multiple DDNAME parameters in the step refer to DD statement '&1'."

Explanation: DDNAME parameters may only refer to one DD statement in a job step. The job will end with aJCL error. Related IBM message: IEF654I.

DSS20009 "Program '&1' is not executable."

Explanation: The program named '&1', although found in a program library accessible to this step, is marked'not executable', and therefore will not be run.

DSS20010 "DD '&1' failed allocation."

Explanation: An attempt was made to open DD &1, but the DD was not allocated.

DSS20011 "DD '&1' was not allocated."

Explanation: An attempt was made to open DD &1, but the DD was not found for this step.

DSS20012 "JCL RECFM '&1' does not match the volume entry RECFM '&2'."

Explanation: If the program does not override the record format, an open error may occur if RECFM '&1'from the JCL is used to open the dataset which has a RECFM of '&2' on the VTOC.

DSS20013 "PRO/JCL does not support this statement type for reformatting."

Explanation: Currently, PRO/JCL does not support reformatting '&1' statements.

DSS20014 "Member '&1' cannot be deleted from dataset '&2'. Member not found."

Explanation: Member '&1' cannot be deleted from dataset '&2'. Member not found.

DSS20015 "Zero (0) not allowed as primary space for a VSAM dataset. DSN: '&1'."

Explanation: A value other than zero (0)must be supplied for this VSAM dataset. DSN: '&1'.

DSS20016 "Cannot open dataset '&1' with DSORG '&2'; because DSORG is '&3'."

Explanation: This program expected dataset '&1' to have a DSORG of '&2'. However, dataset '&1' actually hasa DSORG of '&3'. This can be because of a DSORG parameter on the DD statement, the DSORGof the dataset itself, or SMS may have set the DSORG.

107

System Messages

DSS20017 "IDCAMS CANCEL command simulated; IDCAMS processing ended for this step."

Explanation: The IDCAMS CANCEL command has been simulated, causing the remainder of the commandstream not to be processed.

DSS20018 "'&1' will be bypassed because &2 =&3."

Explanation: The IDCAMS '&1' statement will not be executed, because of a previous 'IF' statement. Thespecific reason that the statement will be bypassed is that the '&2' field has the value '&3'.

DSS20019 "SMS-managed dataset '&1' is in deferred roll-in status."

Explanation: SMS-managed dataset '&1' is in deferred roll-in status. It will be available after this step hasexecuted, when it will be rolled in to the Catalog, unless it is deleted prior to the end of the step.

DSS20020 "The DDNAME ismissing or a statement is misplaced."

Explanation: An unnamed DD statement was encountered, and it is not part of a concatenation.

Action: Possible causes of this error include deleting the 'base' DD of a concatenation without updatingthe DDNAME, or adding an unrelated statement between concatenated DD's.

DSS20021 "'&1 &2': step was simulated, CONDCODE '&3'."

Explanation: The indicated step would give the return code &3when executed at this point in the JOB. Thisreturn code has been simulated for purposes of condition code testing in subsequent steps.

DSS20022 "'&1' must be &2 '&3'."

Explanation: '&1' must be &2 '&3'. For the IDCAMS 'ALTER' statement, both the 'BUFND' and 'BUFNI'parameters must be at least one higher than the value either specified or defaulted for 'STRNO'.

DSS20023 "DDNAME '&1', DSN '&2' should have been a VSAM dataset."

Explanation: An attempt was made to open DDNAME '&1' as a VSAM dataset. However, dataset &2 is not aVSAM dataset.

DSS20024 "&3 '&1' is already cataloged in '&2'."

Explanation: The attempt to catalog the &4 '&1' in the catalog '&2' will fail, because a catalog entry alreadyexists in '&2' pointing to '&1'.

DSS20025 "Cannot obtain DDNAME='&1', DSN='&2'."

Explanation: DDNAME '&1' for dataset '&2' was needed to access and provide complete validation; however,the dataset was unavailable. Possible causes: DASD volumewas off line, input was generatedduring run, input is from temporary file, or dataset resides on tape.

Action: Check system messages for further information.

DSS20026 "Dataset '&1' must be a PDS."

Explanation: An attempt was made to open '&1' as a PDS. However, this dataset is not a PDS.

DSS20027 "DDNAME '&1', DSN '&2' should have been a physical sequential dataset. Actual DSORG is &3."

108


Explanation: An attempt was made to open DDNAME '&1' as a sequential dataset. However, dataset &2 isnot sequential.

DSS20028 "Dataset '&1' was not found in catalog."

Explanation: The dataset '&1' cannot be located via catalog &2. Possible causes of this error includemisspelling the dataset name.

DSS20029 "Cannot delete dataset '&1'; it is not on volume '&2'."

Explanation: An attempt was made to delete dataset '&1' from volume&2. However, it does not exist there.It may have been deleted in a prior job or have never existed on this volume. Volume '&2' mayhave been a candidate volume.

DSS20030 "Dataset '&1' is not on volume '&2'."

Explanation: The dataset '&1' has no VTOC entry on the volume '&2'. It may have been deleted by a priorstep or job.

DSS20031 "Dataset '&1' is not in catalog '&2'; therefore, it cannot be uncataloged."

Explanation: The attempt to uncatalog dataset '&1' from the catalog named '&2' will fail, because there is noentry in '&2' for the dataset '&1'.

DSS20032 "Unable to determine whether VSAM data component '&1' is on volume '&2'."

Explanation: Either '&1' is not on volume '&2' or the name on the DSCB does not match the name in thecatalog. For identification purposes, sometimes DFSMS will generate a VTOC entry containingan additional low level qualifier. This is the case when key ranges are involved.

DSS20033 "Cannot create path '&1' to non-existent entry '&2'."

Explanation: Because there is currently no catalog entry called '&2', the attempt to create a PATH of it called'&1' will fail.

DSS20034 "Cannot create path '&1' of '&2:&3'."

Explanation: Cannot create path '&1' of '&2:&3'. Paths can only be created for AIX or CLUSTER type catalogentries.

DSS20035 "I/O is not allowed on unopened DD '&1'."

Explanation: If this message appears, please contact ASG Technologies.


DSS20036 "In DD '&1' - DSN '&2', DSORG '&3' cannot be concatenated with DSORG '&4'."

Explanation: In a concatenation of DD statements, all the DSORG's must be compatible. For the DDNAME'&1', the DSORG's '&3' and '&4' are incompatible.

DSS20037 "The JES2 '&1' statement must precede the JOB statement."

Explanation: Certain JES2 statements are only valid before a JOB statement is encountered. The JES2 '&1'statement is one of these.

109

System Messages

DSS20038 "The JES2 '&1' statement will be ignored."

Explanation: The '&1' statement must be coded after the JOB statement and before the first EXECstatement.

DSS20039 "Duplicate dataset name '&1' on volume '&2'."

Explanation: There is already a dataset named '&1' on the volume '&2'; therefore, the attempt to createanother one will fail.

DSS20040 "Unit name was not found for dataset '&1'. DD: '&2'."

Explanation: A unit name is required for this reference to dataset &1. However, no unit type could be found.

DSS20041 "Member '&1' cannot be accessed; DD '&2' is not open."

Explanation: An attempt was made to find or savemember '&1' for DD &2. However, this DD was notopened.

DSS20042 "Cannot read directory; DD '&1' is not open."

Explanation: An attempt was made to open DD '&1'. However, it was not previously opened.

DSS20043 "Unidentified unit name '&1'."

Explanation: The UNIT name '&1' was not found on your system.

Action: If this unit name is valid, consider entering it in the UNIT table in your RTS member.

DSS20044 "Preceding command '&1' will be bypassed due to condition codes."

Explanation: &1will be bypassed. PRO/JCL determined that a return code from a previous command met acondition which would result in the command being bypassed.

DSS20045 "Unable to scratch dataset '&1'; cannot find VOLSER '&2'."

Explanation: VOLSER '&2' cannot be found.

Action: Check that the VOLSER is correct for your system.

DSS20046 "Dataset for DD:'&1' has been migrated. No processing done."

Explanation: Dataset for DD:'&1' has been migrated and will not be recalled. Any control cards will bepresumed correct and will not be processed.

DSS20047 "Dataset '&1' has been migrated."

Explanation: Dataset '&1' will probably be recalled during the actual execution of this step.

DSS20048 "No space specified for new dataset '&1'."

Explanation: Whenever a newDASD dataset is allocated, information must bemade available regarding howmuch space is to be occupied. This information may be provided directly on the statement, orvia an SMS routine. For the dataset '&1', however, no such space information was available.

DSS20049 "Unidentified unit name '&1'."

Explanation: The UNIT name '&1' was not found on your system.

110


Action: If this unit name is valid, consider entering it in the UNIT table in your RTS member.

DSS20050 "Dataset '&1' will be cataloged in '&2'."

Explanation: The dataset '&1' will be cataloged in the catalog named '&2'.

DSS20051 "Dataset '&1' specified DSORG '&2' will be ignored with directory space '&3' specified."

Explanation: If directory space is specified in the SPACE parameter, any DSORG specified other than PO willbe ignored, and a partitioned dataset will be created.

DSS20052 "Unable to uncatalog DSN '&1'; it was not found in catalog."

Explanation: In order to uncatalog dataset '&1', it must already exist in a catalog.

DSS20053 "Dataset '&1' will be uncataloged from '&2'."

Explanation: The dataset '&1' will be removed from the catalog named '&2'.

DSS20054 "Dataset '&1' will be scratched from '&2'."

Explanation: The dataset '&1' will be scratched from the VTOC for volume '&2'.

DSS20055 "Member '&1' will be deleted."

Explanation: Themember '&1' will be deleted from the indicated dataset.

DSS20056 "Member '&1' will be renamed to '&2'."

Explanation: Themember '&1' will be renamed to '&2' in the indicated dataset.

DSS20057 "Required keyword 'CLUSTER' is missing."

Explanation: The 'CLUSTER' keyword is required, and was not provided.

DSS20058 "Misplaced comma was found in column &2 of this &1 statement and ignored."

Explanation: In this &1 statement, extraneous commas are allowed between words, but they have no effect.An extraneous comma was found in column &2. This message is issued in case the user wantsto be alerted to change this coding style.

DSS20059 "Member may not be specified with generic delete: '&1'."

Explanation: In an IDCAMS 'DELETE' statement that specifies entry names generically (with '*' as part of thedataset name), no member namemay be given (it is not possible to delete the samememberfrom multiple libraries with a single IDCAMS 'DELETE' statement).

DSS20060 "Member name is not allowed for '&1' with DSORG=&2."

Explanation: Dataset &1was specified with a MEMBER NAME. However,it is not a PDS. The DSORG of '&1' is&2.

DSS20061 "Step '&1' will be bypassed due to true evaluation of the CONDparm."

Explanation: The condition on the COND parm was met. Therefore, step '&1' will be bypassed.

DSS20062 "Space may not be specified for new tape dataset '&1'."

111

System Messages

Explanation: Spacemay not be specified for new tape dataset '&1' When creating a dataset on a tapevolume, the SPACE parameter must not be specified.

DSS20063 "Dataset '&1' expected to be a catalog; found on device '&2'."

Explanation: Dataset &1 is being used as a catalog and therefore is assumed to exist on a DASD volume.However, it was found on a &2 device.

DSS20064 "Dataset '&1' expected to be a catalog; however, it has DSORG '&2'."

Explanation: Because of the way dataset '&1' is used, it was expected to be a catalog dataset. However,dataset '&1' has a DSORG of '&2', which would not be valid for a catalog dataset.

DSS20065 "Dataset '&1' expected to be a catalog."

Explanation: Dataset &1 is being used as a catalog; however, it is apparently not a catalog.

DSS20066 "Cannot create GDG base '&1'. No limit specified."

Explanation: When creating the base for a generation data group (GDG), the 'limit' must be specified. The'limit' indicates howmany generation datasets (GDS's) may reside in the GDG at one time.

DSS20067 "Cannot uncatalog '&1'; non-empty generation data groups cannot be removed without FORCE."

Explanation: 'The catalog entry for &1' is a GDG base entry that still holds generations. Therefore it cannot beuncataloged.

Action: If you still wish to delete the dataset, use IDCAMS DELETE and specify the 'FORCE' parameter.

DSS20068 "Unable to catalog dataset '&1'; cannot determine unit name &2."

Explanation: An attempt to simulate cataloging dataset &1was made. However, the unit name&2 isunidentified.

DSS20069 "Unable to catalog dataset '&1'; no VOLSER."

Explanation: Unable to catalog dataset '&1'; no VOLSER could be found or generated.

DSS20070 "Unable to catalog dataset; no dataset name."

Explanation: In order to catalog a dataset a dataset namemust be provided.

DSS20071 "Cannot associate dataset '&1' type '&2' to dataset '&3' type '&4'."

Explanation: When associating one catalog entry to another there are certain types which cannot be related.In this case an attempt to associate dataset '&1' of type '&2' with dataset '&3' type '&4' wasmade.

DSS20072 "Cannot register '&1', because '&2' is not a GDGBase. It is a '&3'."

Explanation: An attempt was made on DDNAME '&1' to use data Set '&2' as a GDG. However, it is really a &3.

DSS20073 "No GDG base entry exists for '&1' in catalog '&2'."

112


Explanation: The last node of dataset &1 appears to be a GDG generation. However, there is no GDGcataloged by that name. While this will not produce a JCL error, it is something that should beavoided.

DSS20074 "DDNAME '&1', DSN '&2' should have been a GDG base; was a &3."

Explanation: DDNAME '&1', DSN '&2' should have been a GDG base since a relative generation number wassupplied. However, the dataset was cataloged as a &3.

DSS20075 "GDGBase '&1' is in an inconsistent state. Cannot find association for generation G&2Vxx."

Explanation: An attempt was made to retrieve generation &2. However, the catalog did not contain aG&2Vxx entry.

DSS20076 "Expected to find catalog '&1' for dataset '&2', but it does not exist."

Explanation: Expected to find catalog '&1' for dataset '&2', but it does not exist.

DSS20077 "Dataset '&1' is not a catalog."

Explanation: Dataset '&1' was expected to be a catalog; however, it was a &2.

DSS20078 "Missing VOLSER for new catalog '&1'."

Explanation: A VOLSER must be provided when creating a catalog.

DSS20079 "For GDG '&1', relative generation '&2' does not exist."

Explanation: The attempt to refer to relative generation '&2' of GDG '&1' will fail because relative generation'&2' does not exist.

DSS20080 "Relative generation '&2' already exists."

Explanation: DSN '&1': Cannot create relative generation '&2' because it already exists.

DSS20081 "In DSN '&1', cannot create a new generation dataset with relative number '&2'."

Explanation: NewGDG generations must be created with a relative number greater than 0.

DSS20082 "Generation Data Group '&1' contains no generations."

Explanation: Dataset '&1' is a GDG group name. However, it contains no generations.

DSS20083 "Cannot add association &1:&2 for alias &3."

Explanation: Cannot add association &1:&2 for alias &3, because it already has an association.

DSS20084 "Cannot create alias '&1' to non-existent entry '&2'."

Explanation: Because there is currently no catalog entry called '&2', the attempt to create an ALIAS of itcalled '&1' will fail.

DSS20085 "Cannot create alias '&1' of '&2:&3'."

Explanation: Cannot create alias '&1' of '&2:&3'. Aliases can only be created for NONVSAM or CATALOG typecatalog entries.

113

System Messages

DSS20086 "Dataset '&1' is not a catalog."

Explanation: An attempt was made to use the dataset '&1' as a catalog; however, this dataset is not acatalog.

DSS20087 "Temporary dataset '&1' has not yet been created."

Explanation: An attempt was made to refer to the temporary dataset named '&1'; however, at this point inthe JOB, this dataset does not yet exist.

DSS20088 "Temporary dataset '&1' not found."

Explanation: Cannot find temporary dataset '&1'. It did not match the names of any passed datasets. Avolumewas not obtained.

Action: Check the spelling of the dataset.

DSS20089 "Cannot find volume for quoted dataset '&1'."

Explanation: Cannot find volume for quoted dataset '&1'.

DSS20090 "Second disposition '&1' not valid for temporary dataset. 'PASS' substituted."

Explanation: The normal deallocation disposition specified for this temporary dataset, '&1', is not permittedfor a temporary dataset. The statement will be interpreted as if 'PASS' had been coded instead.

DSS20091 "On DDNAME '&1', GDG base '&2' was not found."

Explanation: On DDNAME '&1', GDG base '&2' was not found.

DSS20092 "Step '&1' will be bypassed due to restart on job '&2': '&3'."

Explanation: Step '&1' will be bypassed due to restart on job '&2': '&3'.

DSS20093 "Step '&1' will be bypassed due to a parameter on '&2': '&3'."

Explanation: Step '&1' will be bypassed due to a parameter on '&2': '&3'.

DSS20094 "Unable to locate volume '&1' for dataset '&2', DD '&3'."

Explanation: Unable to locate volume '&1' for dataset '&2', DD '&3'.

DSS20095 "Unable to delete dataset '&1'; not on volume '&2'."

Explanation: The dataset '&1' does not reside on the volume '&2'. This is not necessarily a problem, becauseOS/390 attempts to remove all 'NEW' non-SMS-managed datasets that have not been explicitlydisposed of at end-of-JOB, and may issue these advisory messages at that time.

DSS20096 "Unable to determine VOLSER for dataset '&1'."

Explanation: Unable to determine VOLSER for dataset '&1'.

DSS20097 "Dataset '&1' will be created on '&2'."

Explanation: An entry will bemade to record the presence of dataset '&1' on VOLSER '&2'.

DSS20098 "DSN label &1 mismatch. Requested DSN '&2'; Tape DSN '&3'."

114


Explanation: The dataset located at position &1 on the indicated tape is not '&2', as was specified, but rather'&3'.

Action: Possible reasons for this error includemisspelling the dataset name requested, or mistypingthe label number for the tape.

DSS20099 "Label &1 is not on volume '&2'."

Explanation: The dataset label expected at position &1 is not on tape volume '&2'.

DSS20100 "&1 request failed: dataset '&2' has catalog entry type &3; expected entry type &4."

Action: &1 request failed: dataset '&2' has catalog entry type &3; expected entry type &4.

DSS20101 "Unexpected association type &1 found for dataset '&2' in catalog '&3'."

Explanation: Unexpected association type &1 found for dataset '&2' in catalog '&3'.

DSS20102 "DDNAME '&1' DSN '&2' expects sequential &3."

Explanation: DDNAME '&1' DSN '&2' expects sequential &3. If a PDS was specified, a member is required.

DSS20103 "Step '&1' will be bypassed due to evaluation of '&2' as &3."

Explanation: Step '&1' will be bypassed due to evaluation of '&2' as &3.

DSS20104 "JES statement not allowed in a PROCor INCLUDE."

Explanation: JES statement not allowed in a PROC or INCLUDE.

DSS20105 "'&1 &2': step would ABEND, CODE '&3'."

Explanation: '&1&2': step would ABEND, CODE '&3'. This message is generated when PRO/JCL detects apotential ABEND. Should this job be submitted in the current environment, ABEND &3 is likelyto occur.

DSS20106 "'RECFM for '&1' must be 'U', RECFM is '&2'."

Explanation: '&1' must be a LOAD library which must be RECFM 'U'. The RECFM for this dataset is '&2'. MVSwould not find the PGM and the step would ABEND.

DSS20107 "Program '&1' assigned system ABENDcode '&2'."

Explanation: Program '&1' assigned system ABEND code '&2'.

DSS20108 "Program '&1' assigned user ABEND code '&2'."

Explanation: Program '&1' assigned user ABEND code '&2'.

DSS20109 "Program '&1' assigned return code '&2'."

Explanation: Program '&1' assigned return code '&2'.

DSS20110 "Dataset '&1' status unchanged on VOLSER(S) '&2' ('KEPT')."

Explanation: The dataset '&1' will be kept on the indicated volume serial numbers.

115

System Messages

This message may occur even for datasets that do not actually exist on the indicatedvolume, if the dataset was never opened (example, if the program executed was'IEFBR14'). This behavior duplicates OS/390's handling of the same situation.

DSS20111 "SMS-managed dataset '&1' will be cataloged. '&2' has been ignored."

Explanation: SMS-managed datasets are always cataloged, even if the disposition specified was '&2'.Therefore, the dataset '&1' will be cataloged.

DSS20112 "SMS-managed dataset '&1' will be cataloged in '&2' in deferred roll-in status."

Explanation: The SMS-managed dataset '&1' will be cataloged immediately in the catalog named '&2', indeferred roll-in status.

DSS20113 "Permanent SMS-managed dataset '&1' had disposition 'PASS'. SMS has overridden it to 'KEEP'."

Explanation: Passed non-temporary SMS-managed datasets are treated as if they had disposition of 'KEEP'.

DSS20114 "Subsystem '&1' does not exist."

Explanation: The subsystem name specified, '&1', is not an active subsystem on your system.

Action: Check the spelling of the subsystem name.

DSS20115 "'/* ' not allowed in a PROCor INCLUDE."

Explanation: '/* ' not allowed in a PROC or INCLUDE.

DSS20116 "Label &1 on tape '&2' is already occupied by dataset '&3'."

Explanation: VOLSER '&2' already contains dataset '&3'. This was caused by over-writing label &1. This is notan error, generally. However, it should probably be confirmed that this is what you intended.

DSS20117 "DD statement '&1' was allocated to DDNAME '&2'."

Explanation: The statement named '&1' has been allocated to the DDNAME identified by '&2'. A DDNAME ispointing to it, or it is referring to a DD DUMMY statement.

DSS20118 "DD statement '&1' is now considered a DUMMY dataset due to referback."

Explanation: DD statement '&1' is now considered a DUMMY dataset due to referback.

DSS20119 "Results may be unpredictable when comparing an ABEND code using '&1'."

Explanation: Results may be unpredictable when comparing an ABEND code using '&1'.

DSS20120 "Catalog entry '&1' will be renamed to '&2'."

Explanation: Catalog entry '&1' will be renamed to '&2'.

DSS20121 "Dataset '&1' will be renamed to '&2' on '&3'."

Explanation: Dataset '&1' will be renamed to '&2' on '&3'.

DSS20122 "Dataset '&1' is not a PDS. Found DSORG&2."

116


Explanation: In the context of the statement being scanned, the dataset '&1' was expected to be apartitioned dataset ('PDS'). It is not a PDS.

Action: Possible causes of this error include specifying a member namewith a sequential dataset.

DSS20123 "No catalog entriesmatching '&1'."

Explanation: An attempt was made to read the catalog using a mask of &1. However, there were no entriesthat matched that mask.

DSS20124 "Key length &1 + offset &2 =&3, which exceeds record length &4."

Explanation: Key length &1 + offset &2 = &3, which exceeds record length &4. VSAM does not allow the keypart of the record go past the end of the record.

DSS20125 "DDNAME '&1'; unit=aff invalid on newDASDdataset."

Explanation: DDNAME '&1'; unit=aff invalid on newDASD dataset.

DSS20126 "&1 is unable to open required DD '&2'.

Explanation: Program '&1' needs DD '&2'. However, this DD was unavailable. This can be caused by omittingthe DD from the step, or by an error on the DD that prevents it from being allocated properly.

DSS20127 "Dataset '&1' will be rolled in to catalog '&2'."

Explanation: Dataset '&1' will be rolled in to catalog '&2'.

DSS20128 "Volume '&1' is not mounted."

Explanation: The volume '&1' is offline or otherwise not accessible to the system.

DSS20129 "Second disposition '&1' not valid for quoted dataset. 'KEEP' substituted."

Explanation: Second disposition '&1' not valid for quoted dataset. 'KEEP' substituted.

DSS20130 "Your security system would deny access to dataset '&1' in &2 mode by user &3."

Explanation: Your security system would deny access to dataset '&1' in &2mode by user &3.

DSS20131 "BLKSIZE &1 is not a multiple of LRECL &2 for this FB dataset."

Explanation: BLKSIZE &1 is not a multiple of LRECL &2 for this FB dataset.

DSS20132 "Dataset name '&1' is a JES reserved name."

Explanation: Dataset name '&1' is a JES reserved name.

DSS20133 "For DDNAME '&1', dataset '&2' must have DSORG 'DA'."

Explanation: An attempt was made to open DDNAME '&1' as a direct access dataset. However, dataset '&2'does not support this access method.

DSS20134 "Destination '&1' is not valid."

Explanation: Destination '&1' is not available on this system.

DSS20135 "Missing 'ROUTE' parameter - must be 'PRINT', 'PUNCH', or 'XEQ'."

117

System Messages

Explanation: Missing 'ROUTE' parameter -must be 'PRINT', 'PUNCH', or 'XEQ'.

DSS20136 "'&1' is not a valid 'ROUTE' parameter; must be 'PRINT', 'PUNCH', or 'XEQ'."

Explanation: '&1' is not a valid 'ROUTE' parameter; must be 'PRINT', 'PUNCH', or 'XEQ'.

DSS20137 "Destination must be specified."

Explanation: This JES2 statement requires that a destination be specified.

DSS20138 "Unable to validate destination; DJ0YDEST return code &1."

Explanation: Unable to validate destination; DJ0YDEST return code &1.

DSS20139 "DD indicates LABEL &1 but dataset is cataloged as LABEL &2."

Explanation: DD indicates LABEL &1 but dataset is cataloged as LABEL &2.

DSS20140 "Sysout value of '&1' is not valid for a &2 environment."

Explanation: In a &2 environment, a sysout parameter of '&1' is not valid.

DSS20141 "Alias '&1' for dataset '&2' will be cataloged in '&3'."

Explanation: Alias '&1' for dataset '&2' will be cataloged in '&3'.

DSS20142 "Path '&1' for dataset '&2' will be cataloged in '&3'."

Explanation: Path '&1' for dataset '&2' will be cataloged in '&3'.

DSS20143 "Cannot add association &1:&2 for path '&3'."

Explanation: Cannot add association &1:&2 for path '&3', because it already has an association.

DSS20144 "Tape datasets cannot be renamed. Dataset '&1' will not be renamed."

Explanation: Tape dataset '&1' cannot be renamed. Renaming of tape datasets is not supported.

DSS20145 "The asterisk in the first node of &1 would require searching all datasets in all catalogs."

Explanation: The asterisk in the first node of &1would require searching all datasets in all catalogs. Theoverhead of searching all catalogs is too high for PRO/JCL.

DSS20146 "RECORDSIZE is coded but the average record size '&1' exceeds the maximum record size '&2'."

Explanation: You specified the RECORDSIZE parameter, but the first parameter '&1' is larger than the second'&2'. The function will terminate. Related IBM message: IDC3515I.

DSS20147 "Member '&1' already exists. Member '&2' will not be renamed."

Explanation: Member '&1' already exists. Member '&2' will not be renamed.

DSS20148 "Dataset for DD:'&1' is a tape dataset. No processing done."

Explanation: Dataset for DD:'&1' is a tape dataset. Any control cards will be presumed correct and will not beprocessed.

DSS20149 "Dataset for DD:'&1' is a temporary dataset. No processing done."

118


Explanation: Dataset for DD:'&1' is a temporary dataset. Any control cards will be presumed correct and willnot be processed.

DSS20150 "Cannot access the dataset allocated to DD:'&1'. No processing done."

Explanation: Cannot access the dataset allocated to DD:'&1'. Any control cards will be presumed correct andwill not be processed.

DSS20151 "VSAM association for Data component was not found. Cluster is Migrated."

Explanation: VSAM association for Data component was not found. PRO/JCL was unable to locate thecorrect Data component for this Migrated dataset.

DSS20152 "VSAM association for Index component was not found. Cluster is Migrated."

Explanation: VSAM association for Index component was not found. PRO/JCL was unable to locate thecorrect Data component for this Migrated dataset.

DSS20153 "Concatenation failure for subsystem '&1' dataset &2."

Explanation: Concatenation failure for subsystem '&1' dataset &2. Subsystem directory datasets may not bemixed with other subsystems or partitioned datasets.

DSS20154 "Unable to process subsystem &1 for dataset &2."

Explanation: PRO/JCL does not support subsystem &1 '&1' dataset &2.

DSS20155 "All directories in a concatenation must specify the same subsystem."

Explanation: If a subsystem is specified on any directory of a concatenation then all directories in theconcatenation must specify that subsystem.

DSS20156 "Dataset '&1' was not cataloged because it is a tape dataset that had not been opened."

Explanation: Dataset '&1' was not cataloged because it is a tape dataset that had not been opened. This willresult in IEF287I &1 NOT CATLGD 7.

DSS20157 "Record length '&1' does not exceed the key length '&2' bymore than 4 bytes."

Explanation: The record length, '&1', of a VSAM dataset must be 4 or more bytes larger than the key length'&2'. The function will terminate.

DSS20158 "Define of an Index component is not allowed for an ESDS or RRDS Cluster."

Explanation: An Index component is not part of a VSAM ESDS or RRDS cluster. This will result in an IEC3226I -INCONSISTENT PARAMETERS INVOLVING 'INDEX'. VSAM RC=12.

DSS20159 "All generations of dataset '&1' have been selected."

Explanation: Since no relative generation number was specified, all generations of dataset '&1' have beenselected.

DSS20160 "BLKSIZE '&1' cannot exceed 32760 bytes for a dataset on DASD."

Explanation: Themaximum BLKSIZE value for DASD datasets is 32760.

119

System Messages

DSS20161 "All files after a DDDUMMY will be ignored."

Explanation: All files following a DD DUMMY in a concatenation will be ignored by OS/390. When a read isissued for these files, an EOF indication is returned, and no data is read from the file.

DSS20162 "Unit name '&1' incompatible with volume serial '&2'."

Explanation: A UNIT= and VOLSER=mismatch was found. MVS will fail the step with a JCL error. Related IBMmessage: IEF245I.

DSS20163 "Volume '&1' cannot be mounted on Unit '&2'."

Explanation: Unit and VOL=SER were coded in the JCL however the UCB shows another volume is mountedand is PERMRES or RSRV. Related IBM message: IEF482I.

DSS20164 "Simulation of program '&1' executes itself."

Explanation: Simulation of program '&1' results in the execution of the same program.

Action: Possible reasons include erroneous User Utility processing or an RTS Alias Table entry forprogram '&1'.

DSS20165 "BLKSIZE '&1' cannot exceed 262144 bytes for a dataset on TAPE."

Explanation: Themaximum BLKSIZE value for TAPE datasets is 262144 bytes, or 256K bytes.

DSS20166 "Coded unit '&1' is not valid with coded volser '&2'."

Explanation: Unit and VOL=SER were coded in the JCL however the UCB is not valid. This may result in anallocation failure.

DSS20167 "Device address in UCB is not valid for VOL=SER='&1'."

Explanation: Unit and VOL=SER were coded in the JCL however the device address in the UCB is not valid forthe coded volser.

DSS20168 "Dataset '&1' will be in ROLLED-OFF status."

Explanation: Dataset '&1' will be in ROLLED-OFF status.

DSS20169 "SPACE cannot exceed 65535 tracks for DASDdataset '&1'."

Explanation: Themaximum SPACE value for DASD datasets is 65535 tracks. '&1' primary space allocationexceeds maximum and would fail allocation.

DSS20170 "Dataset '&1' not found, the entry was deleted from catalog '&2'."

Explanation: Dataset '&1' was not found. It was marked as deleted in this run, either in the current scannedjob or an earlier scanned job.

DSS20171 "Dataset '&1' not found on volume '&2', it was previously deleted."

Explanation: Dataset '&1' was not found. It was marked as deleted in this run, either in the current scannedjob or an earlier scanned job.

DSS20172 "Member '&1' not found in dataset '&2', it was previously deleted."

120


Explanation: Member '&1' not found in dataset '&2'. It was marked as deleted in this run, either in thecurrent scanned job or an earlier scanned job.

DSS20173 "Member '&1' of '&2' was specified as output earlier in this run. No processing done."

Explanation: Member '&1' of '&2' was specified as output either in the current scanned job or an earlierscanned job so the contents cannot be determined. Any control cards will be presumed correctand will not be processed.

DSS20174 "'&1' will not be searched for PROCs or INCLUDE members."

Explanation: The dataset '&1' could not be allocated. The search for PROCs or INCLUDEmembers willcontinue with the next dataset in the list.

DSS20175 "Path &1 cannot be created for &2 unless both are $IAM."

Explanation: Path &1 cannot be created for &2 unless both are $IAM.

DSS20176 "Dataset for DD:'&1' was created in this run. No processing done."

Explanation: Dataset for DD:'&1' was created in this run. Any control cards will be presumed correct and willnot be processed.

DSS20177 "'&1' is not a valid program name."

Explanation: '&1' in the DD referred is not a valid member name.

DSS20178 "DCB missing from REPROOUTFILE DD statement."

Explanation: DCB missing from REPRO OUTFILE DD statement.

DSS20179 "Required PARMDDvalue '&1' not found or can not be opened."

Explanation: The DDNAME '&1' specified on the EXEC PARMDD parameter either was not coded or the dataset specified can not be opened.

DSS20180 "Records retrieved from the PARMDDDD '&1' concatenated exceeds the maximum 32760 bytes."

Explanation: Records retrieved from the PARMDD DD '&1' concatenated exceeds themaximum 32760 bytes.

DSS20181 "The DSN '&1' can not be opened for '&2'. Code:&3 RC:&4. See JESMSGLOG for details."

Explanation: The DSN '&1' can not be opened for '&2'. Code:&3 RC:&4. See JESMSGLOG for details.

DSS20182 "DISP FIELD INCOMPATIBLE WITH&1 - It was PASS'ed in a previous step."

Explanation: NEW Disposition is INCOMPATIBLEWITH &1 - PASS'ed in a previous step.

DSS20183 "DISP FIELD INCOMPATIBLE WITHDSNAME &1. Relative generation does not exist."

Explanation: DISP FIELD INCOMPATIBLEWITH DSNAME &1. Relative generation does not exist.

DSS20200 "'&1' required DD '&2' cannot be used as INPUT and defined with DISP=NEW."

Action: Program '&1' has DD '&2' defined as INPUT in RTS DDNAMES Table. This DD cannot defined withDISP=NEW.

121

System Messages

DSS20201 "VOLSER '&1' is not allocated to DD '&2'."

Explanation: The VOLUME '&1' on the IDCAMS statement must be allocated to the DD '&2' coded with theFILE parm.

DSS20202 "VOL=SER= lists too few candidate volumes. Volumes requested is '&1'; candidate volumes is '&2'."

Explanation: The UNIT parameter on the DD statement indicates a request for '&1' volumes but theVOL=SER= parameter lists only '&2' candidate volumes.

DSS20203 "SMS managed PDS is not eligible for multi-volume allocation."

Explanation: SMS managed partitioned dataset is not eligible for multi-volume allocation. MVS will fail theallocation.

DSS20204 "DISP= not coded on DD&1. DISP=NEW is assumed."

Explanation: No disposition was coded on the DD statement. MVS and PRO/JCL assume a disposition of newand processing continues.

DSS20205 "SMSHONOR is valid only for SMS managed tape datasets."

Explanation: SMSHONOR is valid when coding a device number or device group for SMS managed tapedatasets.

DSS20206 "Unable to delete &1 because it is an alias."

Explanation: Unable to delete &1 because it is an alias.

DSS20669 "Programmer Namemissing on job '&1'."

Explanation: Programmer Name required on job '&1'.

DSS20770 "Step '&1' will be bypassed due to true evaluation of the JOB COND."

Explanation: The condition on the JOB COND was met. Therefore, step '&1' will be bypassed.

DSS20771 "IF stmt '&1' will be bypassed due to true evaluation of the JOB COND."

Explanation: The condition on the JOB COND was met. Therefore, IF stmt '&1' will be bypassed.

DSS20772 "Dataset &1 is not useable here because it will be created in this step."

Explanation: Dataset &1 is not useable here because it will be created in this step.

DSS20773 "User '&1' is not defined to the security system. DSNaccess checking suspended."

Explanation: User '&1' is not defined to the security system. DSN access checking suspended.

DSS20775 "User '&1' is not defined to group '&2'. DSNaccess checking suspended."

Explanation: User '&1' is not defined to group '&2'. DSN access checking suspended.

DSS20777 "User ID '&1' has been revoked or suspended by your security system. DSNaccess will not be checkedfor this job."

122


Explanation: User ID '&1' has been revoked or suspended by your security system. PRO/JCL or INFO/XE willnot check DSN access for this job.

DSS20778 "Dataset '&1' not found in catalog. DSN from EXPORTEDdataset will be used."

Explanation: Dataset '&1' not found in catalog. DSN from the EXPORTED dataset will be used which may bedifferent than the DSN on the DD. If the EXPORTED DSN is not in the catalog the step will fail.

DSS20779 "Access to group '&1' has been revoked. DSNaccess checking suspended."

Explanation: Access to group '&1' has been revoked. DSN access checking suspended.

DSS20780 "Access to this dataset denied by SAF interface return code: &1 &2 &3."

Explanation: Access to this dataset denied by SAF interface return code: &1&2&3.

DSS20782 "AMP cannot be coded for a non-VSAM dataset."

Explanation: AMP cannot be coded for a non-VSAM dataset.

DSS20783 "BLKSIZE &1 is not equal to LRECL &2 for this fixed dataset."

Explanation: BLKSIZE &1 is not equal to LRECL &2 for this fixed dataset.

DSS20784 "BLKSIZE &1 is not compatible with LRECL &2 for this Variable record length dataset."

Explanation: BLKSIZE &1 is not compatible with LRECL &2 for this Variable record length dataset.

DSS20785 "Missing volume list for VSAM dataset '&1'."

Explanation: A volumemust be specified to create a newVSAM dataset.

DSS20786 "Second disposition 'UNCATLG' ignored for SMS-managed dataset '&1'. '&2' substituted."

Explanation: Second disposition 'UNCATLG' ignored for SMS-managed dataset '&1'. '&2' substituted.

DSS20787 "In DD '&1', '&2' with RECFM '&3' is concatenated with a RECFM '&4' dataset."

Explanation: In DD '&1' a RECFM conflict was discovered between '&2' and the first dataset in theconcatenation. This may cause a problem in some JCL streams.

DSS20788 "Dataset '&1'; original dataset attributes could not be obtained."

Explanation: Due to the usage of dataset '&1' and the specification of 'AMORG', original dataset attributescould not be obtained. Attributes from the DD will be used. As a default, the dataset will beallocated using one track. If you are processing with SMS, the current SMS routines will beaccessed.

DSS20789 "GDG generation '&1' cannot be deleted using an IDCAMS DELETE."

Explanation: IDCAMS DELETE will not work to delete a generation of a GDG dataset.

DSS20790 "AMP was coded for NEW dataset without RECORG, which is required."

Explanation: Coding AMP on a DD indicates the dataset is VSAM which must have a RECORG. Related IBMMessage: IGD17432.

123

System Messages

DSS20791 "Dataset '&1' has an LRECL of &2 could not be opened because the coded LRECL was &3."

Explanation: Dataset '&1' has an LRECL of &2 could not be opened because the coded LRECL was &3. TheLRECL and the coded LRECL on the statement must be the same.

DSS20792 "Volume &1 is not valid for unit &2."

Explanation: Volume&1 is not valid for unit &2.

DSS20793 "Open error for nullfile on DD: '&1'."

Explanation: Open error for nullfile on DD: '&1'. See related IBM message IDC3300I.

DSS20794 "JES3may not start this job because &1 is deleted before it is used."

Explanation: JES3may not start this job because &1 is deleted before it is used.

DSS20795 "JES3may not start this job because &1 is not cataloged."

Explanation: JES3may not start this job because &1 is not cataloged.

DSS20796 "JES3may not start this job because &1 is allocated more than once."

Explanation: JES3may not start this job because &1 is allocated more than once.

DSS20797 "Internal error: unit for '&1' cannot be found. Please call ASG Technologies Customer Support."

Explanation: The VolumeManager was unable to locate the unit associated with the volume '&1'.


DSS20798 "Internal error: unit for '&1' cannot be deleted. Please call ASG Technologies Customer Support."

Explanation: The VolumeManager was unable to delete the unit associated with the volume '&1'.


DSS20799 "Internal error: unit for '&1' cannot be added. Please call ASG Technologies Customer Support."

Explanation: The VolumeManager was unable to add the unit associated with the volume '&1'.


DSS20800 "VOLSER coded '&1' is quoted but not a valid VOLSER; volume selection is unpredictable."

Explanation: A quoted VOL=SER will pass the converter/interpreter and may be overridden by SMS if thedataset is SMS managed. If the dataset is not SMS managed this may result in a volumemountrequest being issued.

DSS20801 "VOL=SER= '&1' is not a valid VOLSER. '&2' in coded VOLSER is not allowed."

Explanation: '&1' contains '&2' which is not valid for a VOLSER.

Action: Correct the character which is not allowed before submitting the JOB.

DSS20802 "VOL=SER= '&1' exceeds 6 characters which is not valid."

Explanation: VOL=SER= names may not be longer than 6 characters. The coded VOL=SER= exceeds 6characters in length.

124


Action: Correct the VOL=SER= value before submitting the JOB.

DSS20803 "Not authorized to catalog '&1' in the master catalog '&2'. An aliasmay bemissing from the mastercatalog."

Explanation: Not authorized to catalog '&1' in themaster catalog '&2'. An alias may bemissing from themaster catalog.

DSS20804 "No records found in '&1' '&2'. End of File mark detected."

Explanation: Dataset '&2' of DD '&1' has no records. End of File mark detected.

DSS20805 "Input file '&1' does not have BLKSIZE specified or BLKSIZE is zero."

Explanation: Input file '&1' does not have BLKSIZE specified or BLKSIZE is zero.

DSS20806 "DD statement missing for DDNAME '&1' which was specified in the IDCAMS FILE parameter."

Explanation: DD statement missing for DDNAME '&1' which was specified in the IDCAMS FILE parameter. TheFILE parameter was ignored.

DSS20807 "Input file '&1' does not have RECFM specified."

Explanation: Input file '&1' does not have RECFM specified.

DSS20808 "Inconsistent record formats '&1' and '&2'."

Explanation: Inconsistent record formats in concatenation '&1' and '&2'.

DSS20809 "Limit of 8 NOTIFY statements has been exceeded."

Explanation: The limit of 8 NOTIFY statements has been exceeded.

DSS20810 "Misplaced NOTIFY statement."

Explanation: NOTIFY must be before any EXEC statements.

DSS20811 "Duplicate NOTIFY statement."

Explanation: A NOTIFY statement with this name already exists in this JOB.

DSS20812 "DDNAME '&1', PATH '&2'expected &3."

Explanation: DDNAME '&1', PATH '&2'expected &3.

DSS20813 "Unable to substitute TWS &OADID in record &2 with &1. An error may be caused."

Explanation: This can occur when APPLID coded in PRO/JCL control cards make the continuation character inthe incorrect column.

DSS29900 "SMS data class '&1' not found."

Explanation: SMS data class '&1' was assigned to this dataset, but was not defined to SMS.

DSS29901 "SMS storage class '&1' not found."

Explanation: SMS storage class '&1' was assigned to this dataset, but was not defined to SMS.

125

System Messages

DSS29902 "SMS management class '&1' not found."

Explanation: SMS management class '&1' was assigned to this dataset, but was not defined to SMS.

DSS29903 "SMS storage group '&1' not found."

Explanation: SMS storage group '&1' was assigned to this dataset, but was not defined to SMS.

DSS29904 "&1."

Explanation: Your data center's SMS data class exit issued message: &1.

DSS29905 "&1."

Explanation: Your data center's SMS storage class exit issued message: &1.

DSS29906 "&1."

Explanation: Your data center's SMS management class exit issued message: &1.

DSS29907 "&1."

Explanation: Your data center's SMS data class ACS routine issued message: &1.

DSS29908 "&1."

Explanation: Your data center's SMS storage class ACS routine issued message: &1.

DSS29909 "&1."

Explanation: Your data center's SMS management class ACS routine issued message: &1.

DSS29910 "&1."

Explanation: Your data center's SMS storage group ACS routine issued message: &1.

DSS29911 "Your data center's SMS storage group ACS routine issued unexpected message: &1."

Explanation: If this message appears, please contact ASG Technologies.


DSS29912 "Dataset is not eligible for allocation on an SMS-managed volume."

Explanation: Dataset is not eligible for allocation on an SMS-managed volume.

DSS29913 "Incompatible storage class and volume."

Explanation: Incompatible storage class and volume.

DSS29914 "Error during SMS processing."

Explanation: Error during SMS processing.

DSS29915 "Error in an ACS routine exit."

Explanation: Error in an ACS routine exit.

DSS29916 "Storage/Management class not allowed for non-SMS dataset."

126


Explanation: Storage/Management class not allowed for non-SMS dataset.

DSS29917 "There are no volumes in storage group '&1'."

Explanation: There are no volumes in storage group '&1'.

DSS29918 "SMS dataset cannot be placed on non-SMS volume '&1'."

Explanation: An SMS-managed dataset cannot be placed on a non-SMS-managed volume (VOL=SER=&1). If aStorage Class with Guaranteed Space is selected and a VOLSER is coded, SMS will attempt toallocate the dataset on the coded VOLSER.

DSS29919 "Non-SMS dataset cannot be placed on SMS volume '&1'."

Explanation: A non-SMS-managed dataset cannot be placed on an SMS-managed volume (VOL=SER=&1).

DSS29920 "STORCLAS '&1' selected. The coded VOLSER '&2' will be ignored."

Explanation: STORCLAS '&1' selected. The coded VOLSER '&2' is ignored. SMS will override the VOLSER asspecified and will select an SMS-managed VOLSER.

DSS29921 "SMS ACS routine changed DATACLAS to '&1'."

Explanation: SMS ACS routine changed DATACLAS to '&1'.

DSS29922 "SMS ACS routine changed STORCLAS to '&1'."

Explanation: SMS ACS routine changed STORCLAS to '&1'.

DSS29923 "SMS ACS routine changedMGMTCLAS to '&1'."

Explanation: SMS ACS routine changed MGMTCLAS to '&1'.

DSS29924 "Quoted dataset name cannot be SMS-managed."

Explanation: An SMS storage class was selected, but is not allowed for a quoted dataset name. MVS will failthe allocation.

DSS29925 "Management class is ignored - dataset not SMS-managed."

Explanation: Management class is ignored - dataset not SMS-managed.

DSS29926 "SMS ACS routine selected no STORCLAS."

Explanation: SMS ACS routine selected no STORCLAS - the dataset will not be SMS-managed.

DSS29927 "'&1' is SMS-managed, but '&2' is not on an SMS-managed volume."

Explanation: '&1' is SMS-managed, but '&2' is not on an SMS-managed volume.

DSS29928 "Cannot allocate an SMS-managed dataset when a STEPCAT is in effect."

Explanation: Cannot allocate an SMS-managed dataset when a STEPCAT is in effect.

DSS29929 "Cannot allocate an SMS-managed dataset when a JOBCAT is in effect."

Explanation: Cannot allocate an SMS-managed dataset when a JOBCAT is in effect.

127

System Messages

DSS29930 "'&1' is not a valid year on the EXPDT parameter. It should be a number from 1900 to 2155."

Explanation: '&1' is not a valid year on the EXPDT parameter. It should be a number from 1900 to 2155.

DSS29931 "Incorrect Julian day following the '/' in 'EXPDT=&1'. It should be a number from 000 to 366."

Explanation: The Julian day following the '/' in 'EXPDT=&1' is not valid. It should be a three digit number from000 to 366.

DSS29932 "'&1' is not valid on the EXPDT parameter. It should be in the form YYDDDor YYYY/DDD."

Explanation: '&1' is not a valid date on the EXPDT parameter. It should be a number in the form YYDDD orYYYY/DDD.

DSS29933 "'EXPDT=&1' contains an incorrect Julian day. The day should be a number from 000 to 366."

Explanation: 'EXPDT=&1' contains an incorrect Julian day. EXPDT should be in the form YYDDD where DDD isa number from 000 to 366.

DSS29934 "Expiration date error: 366 is only valid in leap years."

Explanation: Expiration date error: Julian day 366 is only valid in leap years. The specified year is not a leapyear.

DSS29935 "The EXPDT parameter does not contain a valid date. '&1' will be used as the retention period."

Explanation: The EXPDT parameter does not contain a valid date. '&1' will be used as the retention period.

DSS29936 "DATACLAS selected by the SMS ACS routine is '&1'."

Explanation: DATACLAS selected by the SMS ACS routine is '&1'.

DSS29937 "STORCLAS selected by the SMS ACS routine is '&1'."

Explanation: STORCLAS selected by the SMS ACS routine is '&1'.

DSS29938 "MGMTCLAS selected by the SMS ACS routine is '&1'."

Explanation: MGMTCLAS selected by the SMS ACS routine is '&1'.

DSS29940 "SYSINDDwas generated."

Explanation: Control card(s) detected. SYSIN DD was generated.

DSS29941 "(OLD,NEW) combination for PASSWORDand PASSPHRASE must be of the same type"

Explanation: NEW PASSWORD can be specified only if an OLD PASSWORD was specified. This is the same forwhen the PASSPHRASE is specified.

DSS30001 "JOB not processed because of CA7 #NOX statement."

Explanation: This JOB was not processed because an active CA7 #NOX statement was encountered.

DSS30101 "Columns 69 - 71 should be blank on the first JOB card when running CA7."

Explanation: CA7 requires columns 69 - 71 to be blank on the first JOB card.

DSS30902 "Cannot load user program '&1'."

128


Explanation: Cannot load user program '&1'.

DSS31500 "LOGONID statement ignored because it is not within a job."

Explanation: LOGONID statement ignored because it is not within a job.

Action: The //*LOGONID must be placed after the JOB statement and before the first EXEC statement.

DSS31501 "LOGONID statement ignored because it is not placed before the first EXEC statement."

Explanation: LOGONID statement ignored because it is not placed before the first EXEC statement.

Action: The //*LOGONID must be placed after the JOB statement and before the first EXEC statement.

DSS31502 "LOGONID statement ignored because there is a USERparameter on the JOB statement."

Explanation: LOGONID statement ignored because there is a USER parameter on the JOB statement. TheUSER parameter on the JOB statement overrides the ACF2 //*LOGONID statement.

DSS31503 "LOGONID statement ignored because it follows another LOGONID statement."

Explanation: LOGONID statement ignored because it follows another LOGONID statement. The first//*LOGONID statement is the only one used by ACF2.

DSS31504 "ACF2 LOGONID not valid; longer than 8 characters."

Explanation: The LOGONID on the ACF2 //*LOGONID statement must be 8 characters or less in length.

DSS31505 "ACF2 LOGONIDmissing."

Explanation: The LOGONID on the ACF2 //*LOGONID statement must be 1 to 8 characters in length.

DSS31506 "ACF2 LOGONID not valid, contains non-alphanumeric characters."

Explanation: The LOGONID on the ACF2 //*LOGONID statement must be 1 to 8 alphanumeric characters.

DSS32500 "Required keyword &1 is missing."

Explanation: Keyword &1was not found. DSN and DISP are required for PANVALET.

DSS32501 "Disposition other than SHR is not valid for PANVALET."

Explanation: The only allowable disposition for PANVALET datasets is SHR.

DSS32502 "The length of member name '&1' is more than 10 characters."

Explanation: Themember name '&1' must not be longer than 10 characters.

DSS32503 "A recursive include of '&1' has already been detected processing halted."

Explanation: Member '&1' has already been included and further inclusion would cause an infinite loop. Nofurther processing will be done to this Job.

DSS32504 "Panvalet ++Include maximum nesting level has been exceeded."

Explanation: ++Include ofmember &1 caused the include nesting level to exceed 6.

DSS32505 "Unable to locate required Keyword DSN."

Explanation: Unable to locate required Keyword DSN.

129

System Messages

DSS32506 "Unable to locate member name for subsystem access."

Explanation: Unable to locatemember name for subsystem access.

DSS32507 "Librarian -INC nesting is not allowed."

Explanation: -INC &1 is not allowed in an included librarian member.

DSS32508 "&1 Unable to read library DD='&2' DSN='&3'. Find member was not done."

Explanation: &1 Unable to read library DD='&2' DSN='&3'. Find member was not done.

DSS32509 "Missing required parameter 'LIBRARYENTRY' or 'VOLUMEENTRY'."

Explanation: CREATE requires a parameter.

Action: Specify LIBRARYENTRY or VOLUMEENTRY to identify the type of entry.

DSS33000 "Writing to Librarian datasets is not yet supported."

Explanation: Writing to Librarian datasets is not yet supported.

DSS33001 "Disposition coded is not effective for LIBRARIAN. SHRwill be used."

Explanation: Librarian will use DISP=SHR regardless of what is coded.

DSS33400 "&1."

Explanation: &1.

DSS33401 "&1."

Explanation: &1.

DSS33500 "ZEKE variable &1 was not resolved."

Explanation: ZEKE variable &1was not resolved.

DSS33501 "ZEKE failed return code: &1. &2."

Explanation: ZEKE failed return code: &1. &2.

DSS33502 "Variable &1 is not defined to ZEKE."

Explanation: Variable &1 is not defined to ZEKE.

DSS33510 "OASIS failed return code: &1. &2."

Explanation: OASIS failed return code: &1. &2.

DSS33511 "Unable to load OASIVARmodule."

Explanation: Unable to load OASIVAR module.

DSS33512 "No valid qualifier was found for an OASIS variable."

Explanation: No valid qualifier was found for an OASIS variable in the following line.

DSS34000 "Unable to resolve CA-Jobtrac variable '&1'."

130


Explanation: Unable to resolve CA-Jobtrac variable '&1'.

DSS34001 "Unable to find alternate location '&1'."

Explanation: Unable to find alternate location '&1'.

DSS34002 "Unable to create value from '&1'."

Explanation: Unable to create value from '&1'.

DSS34003 "Unable to load dataset '&1' member '&2'."

Explanation: Unable to load dataset '&1' member '&2'.

DSS34004 "Unable to read SCL dataset '&1'."

Explanation: Unable to read SCL dataset '&1'.

DSS34501 "TapeManagement indicates next volume should be: &1, found: &2."

Explanation: TapeManagement System indicates next volume should be &1, but the JCL specified &2.

DSS34520 "TMS interface module 'TMSSVC' is missing."

Explanation: Module TMSSVC could not be loaded. Concatenate the library containing the TMS loadmodules with the ASG Technologies load libraries.

DSS34521 "TMS is not active."

Explanation: TMS is not currently running in the system.

DSS34522 "No TMS record for volume '&1' was found."

Explanation: A read of the TMS catalog was performed and no volume serial was found.

DSS34525 "TMS shows no slot number for volume '&1'."

Explanation: Since no slot number is recorded, it is possible that this volume is out-of-area, and therefore isnot available for mounting.

DSS34526 "TMS shows tape '&1' out of area '&2', slot '&3'."

Explanation: There is a non-null value in the area code of the tape TMC record.

DSS34527 "TMS shows vol '&1' is #&2 of a multi-volume set starting at '&3'."

Explanation: TMS shows vol '&1' is #&2 of a multi-volume set starting at '&3'.

DSS34600 "Unable to open or read TLMS VMF."

Explanation: Unable to open or read TLMS VMF.

DSS34601 "Volume is not within any TLMS range."

Explanation: Volume is not within any TLMS range.

DSS34602 "Unsupported version of TLMS VMF."

Explanation: PRO/JCL does not support this version of TLMS VMF.

131

System Messages

DSS34603 "Unexpected record found in TLMS VMF."

Explanation: A DSN record was expected but not found in TLMS VMF.

DSS34604 "DSN record found in the VMF does not match the volume specified."

Explanation: DSN record found in the VMF does not match the volume specified.

DSS34700 "Unable to initialize &1 interface."

Explanation: Unable to initialize &1 interface.

DSS34701 "&2 reports that &1 is not a managed volume."

Explanation: &2 reports that &1 is not a managed volume.

DSS34702 "Tape VOL=SER=&1 off-site location &2, slot &3."

Explanation: Tape VOL=SER=&1 off-site location &2, slot &3.

DSS34703 "&1 API Module is missing."

Explanation: PRO/JCL was unable to locate the &1 API Module.

DSS34704 "Bad return code from &1 init call: rc=&2."

Explanation: PRO/JCL received return code &2while attempting to initialize &1.

DSS34705 "Bad return code from ZARA VOL call: &1."

Explanation: Bad return code from ZARA VOL call: &1.

DSS34706 "Volume '&1' is not in any &2 range."

Explanation: Volume '&1' is not in any &2 range.

DSS34707 "File sequence error on volume '&1' for label &2."

Explanation: File sequence error on volume '&1' for label &2.

DSS34708 "Existing file at label &2 may be overwritten on volume &1."

Explanation: Existing file at label &2may be overwritten on volume&1.

DSS34709 "Tape '&1' is flagged as DELETEDby the tape management system."

Explanation: Tape '&1' is flagged as DELETED by the tapemanagement system.

DSS34710 "Tapemanagement system indicates volume '&1' is damaged."

Explanation: Tapemanagement system indicates volume '&1' is damaged.

DSS34711 "Tape '&1' is not defined to the tape management system."

Explanation: Tape '&1' is not defined to the tapemanagement system.

DSS34712 "Tapemanagement system reports that volume '&1' is not a scratch volume."

Explanation: Tapemanagement system reports that volume '&1' is not a scratch volume.

132


DSS34713 "&1 sequence error for volume &2. (&3)."

Explanation: &1 indicates volume&2 is number &3 of a multivolume set.

DSS34714 "Tapemanagement system reports that volume '&1' is scratched. No files exist on it."

Explanation: Tapemanagement system reports that volume '&1' is scratched. No files exist on it.

DSS34715 "Tapemanagement system reports that label '&1' is not on volume '&2'."

Explanation: Tapemanagement system reports that label '&1' is not on volume '&2'.

DSS34716 "Volume '&1' must be 6 characters for &2."

Explanation: &2 requires 6 character volume serial numbers for &1.

DSS34717 "Bad return code from CTLT OPEN call: rc=&1."

Explanation: PRO/JCL received return code &1while attempting to open the CTLT media database. Thereason code, if any, appears after the return code These return and reason codes aredocumented in control-t message CTT200S.

DSS34718 "TapeManager returned label &1 out of sequence on volume &2."

Explanation: Tapemanager returned label &1 out of sequence on volume&2. The dataset for this label is &3.

DSS34815 "RMMGET CALL PRIORTO INIT CALL."

Explanation: RMM GET CALL PRIOR TO INIT CALL.

DSS34816 "RMM LISTDS call failed &1."

Explanation: RMM LISTDS call failed &1.

DSS34817 "RMMSEARCHDS got bad RC-RS: &1."

Explanation: RMM SEARCH DS got bad RC-RS: &1.

DSS34818 "RMMSEARCHor LIST continue failed: &1."

Explanation: RMM SEARCH or LIST continue failed: &1.

DSS34819 "RMM LISTVOLUME got bad RC-RS: &1."

Explanation: RMM LISTVOLUME got bad RC-RS: &1.

DSS34820 "RMMAPI MODULE MISSING (EDGXAPI)."

Explanation: RMM API MODULEMISSING (EDGXAPI).

DSS34900 "This statement requires parentheses around the member list."

Explanation: This statement requires parentheses around themember list.

DSS34901 "'&1' requires one or more member names."

Explanation: '&1' requires one or moremember names.

DSS34902 "This statement '&1' is not allowed for &2."

133

System Messages

Explanation: This statement '&1' in not allowed for &2.

DSS34903 "Renamemembersmust be specified as oldname,newname pairs."

Explanation: Renamemembers must be specified as oldname,newname pairs.

DSS34904 "&1 requires a &2 to have been specified first."

Explanation: &1 requires a &2 to have been specified first.

DSS34905 "Move all from: '&1'."

Explanation: All themembers will bemoved from DDNAME '&1'.

DSS34906 "to: '&1'."

Explanation: to DDNAME '&1'.

DSS60000 "Database &1 for USERID&2 is not initialized properly. Missing IXTINFO row."

Explanation: Database &1 for USERID &2 is not initialized properly. Missing IXTINFO row.

DSS60001 "DB2 database name not specified; cannot perform SQL connect."

Explanation: DB2 database name not specified in Run Time Settings; cannot perform SQL connect.

DSS60002 "DB2 plan name not specified; cannot perform SQL connect."

Explanation: DB2 plan name not specified in Run Time Settings; cannot perform SQL connect.

DSS60003 "Unable to process filename '&1' because of invalid file type '&2'."

Explanation: Filename '&1' with invalid file type '&2' was found in the database. File '&1' will not beprocessed.

DSS60004 "Error: Found Executable statement with an unresolved name - Unable to add to database. File '&1',Member '&2', Record number '&3'."

Explanation: Error: Found Executable statement with an unresolved name - Unable to add to database. File'&1', Member '&2', Record number '&3'.

DSS60008 "Member '&1' was not found in the INFO/X repository."

Explanation: Member '&1' was not found in the INFO/X repository.

DSS60009 "A Job statement was included in a PROCor INCLUDE which is not allowed. Aborting processing ofmember '&1'."

Explanation: A Job statement was included in a PROC or INCLUDE which is not allowed. Aborting processingofmember '&1'.

DSS61001 "If statement does not have if clause."

Explanation: If statement does not have if clause.

DSS61002 "Then clause not specified for previous if statement."

Explanation: Then clause not specified for previous if statement.

134


DSS61003 "If or then clause does not have matching if statement."

Explanation: If or then clause does not havematching if statement.

DSS61005 "Case statement must be terminated with the reserved word esac."

Explanation: Case statement must be terminated with the reserved word esac.

DSS61006 "The previous compound list is not terminated with ;;"

Explanation: The previous compound list is not terminated with ;;

DSS61007 "Previous statement terminated with ;; does not have matching pattern list."

Explanation: Previous statement terminated with ;; does not have pattern to bematched.

DSS61008 "Multiple patterns '&1' with the same compound list shall be delimited by the | symbol."

Explanation: Multiple patterns '&1' with the same compound list shall be delimited by the | symbol.

DSS61010 "Unmatched do/done construct."

Explanation: Unmatched do/done construct.

DSS80001 "WIXX.RUNOPT.CHECKDSNACCESS"

Explanation: Use Check DSN Access for &1 to check if the user ID running the job has proper access authorityto the datasets in the JCL.

Action: Specify Y to turn on the checking. If user does not have sufficient authority, &1 issues amessage about each dataset that could not be accessed. Specify N to turn off the checking.

DSS80002 "WIXX.RUNOPT.CONDITIONALPROCESSING"

Explanation: Use COND Processing to specify whether &1 is to simulate COND CODE and 'IF' statementprocessing.

Action: Specify Y to turn on condition code processing, so that &1will simulate the 'COND' parameterand 'IF' statement clauses and simulate steps accordingly. Specify N to force &1 to ignore the'COND' parameter and 'IF' statement clauses and simulate every step.

&1 performs syntax validation on all steps in any case. This option controls run-timevalidation only, such as checking the existence of datasets.

DSS80003 "WIXX.RUNOPT.CUSTOMERPREFIX"

Explanation: Use Customer Prefix to specify the string you want to precedemessages issued by your JMPprogram.

Action: Specify an up-to-3-character string which is used as the prefix for your JMP program messages.

The default value is USR.

DSS80004 "WIXX.RUNOPT.GDGUPDATE"

135

System Messages

Explanation: Use the GDG Processing Run Option to control the external tracking of generation datasets.This option can be set so that &1 processes +n datasets as though the GDG Base RecordAssociation is updated at the end of a step or at the end of the job.

Action: ENDOFSTEP specifies that +n datasets should be processed as though the GDG Base RecordAssociation is updated at the end of a step. ENDOFJOB specifies that +n datasets should beprocessed as though the GDG Base Record Association is updated at the end of a job.

Before specifying ENDOFSTEP, verify with the system programmers at your site that theoperating system in use updates the GDG Base Record Association at the end of each step.

DSS80005 "WIXX.RUNOPT.ISPFSTATS"

Explanation: Use ISPF Stats to specify whether &1maintains the ISPF statistics associated with each dataset(member) as a result of changes that &1might perform on your JCL.

Action: Specify UPDATE when you want &1 to update these ISPF statistics: change date, user ID, andnumber of lines. Specify NOUPDATE to prevent &1 from updating the ISPF statistics.

DSS80006 "WIXX.RUNOPT.JESDESTINATIONCHECK"

Explanation: Use JES Dest Check to specify whether &1 validates the destination on these statements: JES2Route, JES2 Output, JES2 XMIT, JCL output, JCL DD, JES3 Format, JES3 Route, JES3 XMIT.

DSS80007 "WIXX.RUNOPT.MEMBERCHECKING"

Explanation: UseMember Checking to specify whether &1 checks to see whether members specified in theJCL exist.

Action: Specify Y to turn on member checking. &1will check the dataset specified in the JCL for themember. Specify N to turn offmember checking. &1will continue to ensure the dataset can befound, but will not check for themember.

DSS80008 "WIXX.RUNOPT.MIGRATEDEVICETYPE"

Explanation: UseMigrate Dev Type to specify the type of device used as themigration device. Use DISK tospecify that migration is to DASD type devices. Use TAPE to specify that migration is to tapetype devices.

DSS80009 "WIXX.RUNOPT.OSRELEASE"

Explanation: Specify theMVS operating system release for &1 to simulate.

DSS80010 "WIXX.RUNOPT.PROCESSDB2"

Explanation: Use Process DB2 to validate DB2 control statements.

Action: Specify Y when you want &1 to validate DB2 control statements. Specify Nwhen you want &1to ignore DB2 control statements.

DSS80011 "WIXX.RUNOPT.PROCESSIDCAMS"

Explanation: Use Process IDCAMS to validate IDCAMS control statements.

136


Action: Specify Y when you want &1 to validate IDCAMS control statements and track datasets createdor deleted by an IDCAMS step in the sameway JCL references are tracked. Specify Nwhen youwant &1 to ignore IDCAMS control statements.

DSS80012 "WIXX.RUNOPT.PROCESSIEBCOPY"

Explanation: Use Process IEBCOPY to validate IEBCOPY control statements.

Action: Specify Y when you want &1 to validate IEBCOPY control statements. Specify Nwhen you want&1 to ignore IEBCOPY control statements.

DSS80013 "WIXX.RUNOPT.PROCESSSORT"

Explanation: Use Process SORT to validate SORT control statements.

Action: Specify Y when you want &1 to validate SORT control statements. Specify Nwhen you want &1to ignore SORT control statements.

DSS80014 "WIXX.RUNOPT.PROCLIBDD"

Explanation: Use PROCLIBDD to specify the DDNAME your system uses to resolve PROC's and INCLUDE'S.This might be 'DYNAPROC' or 'EZPROC' if either product is used to resolve PROC's.

&1 processes PROC libraries in this order: 1. Instream PROCs. 2. Those specified in the &1Validation panel FIRSTPROCLIB option. 3.Those specified in the JCLLIB statement in the JCL.4. Those specified in this (PROCLIBDD) option. 5. Those specified in JES.

DSS80015 "WIXX.RUNOPT.PROGRAMCHECKING"

Explanation: Use Program Checking to specify whether &1 checks to see if programs exist.

Action: Specify Y to check if programs exist and report errors. Specify N to inhibit this checking.

DSS80016 "WIXX.RUNOPT.TSOSUBMIT"

Explanation: Use TSO Submit to control TSO simulation for JOB statement processing.

Action: Specify Y to generate a valid JOB statement for members that do not have a job statement.Does not affect processing ofmembers that have a JOB statement. Specify N for normalprocessing ofmembers. If no JOB statement is found, none is generated and &1 printsappropriate errors in the Structured JCL Listing.

DSS80017 "WIXX.RUNOPT.PROCESSADRDSSU"

Explanation: Use Process ADRDSSU to enable the DFSMSdss control statement interface.

Action: Specify Y when you want &1 to validate DFSMSdss control statements. Specify Nwhen youwant &1 to ignore DFSMSdss control statements.

DSS80018 "WIXX.RUNOPT.CALLMANAGEMENTCLASS"

Explanation: Use Call Management Class to determine if the SMS Management Class ACS routine should beinvoked.

137

System Messages

Action: Specify Y to invoke the SMS Management Class ACS routine. Specify N to not invoke the SMSManagement Class ACS routine.

DSS80019 "WIXX.RUNOPT.CALLSTORAGEGROUP"

Explanation: Use Call Storage Group to determine if the SMS Storage Group ACS routine should be invoked.

Action: Specify Y to invoke the SMS Storage Group ACS routine. Specify N to not invoke the SMSStorage Group ACS routine.

DSS80020 "WIXX.RUNOPT.PRESERVE7380"

Explanation: The Output 73-80 option determines what appears in columns 73-80 of the Output member.The RENUMBER option will renumber all the records in a changed member. The first record willbe numbered 100. Each following record will be incremented by 100. The numbers are incolumns 73-78. If ISPF statistics are on for this member, themodification number will be set onall changed records in columns 79 and 80. Otherwise, columns 79 and 80 are set to '00'. TheMAINTAIN option will keep 73-80 intact regardless of how the records change. This option isuseful if you keep data or special indicators in columns 73-80. The AUTO option automaticallyselects between ISPF and MAINTAIN. If the first record in themember has numerics in 73-80,then ISPF is selected. Otherwise, MAINTAIN is used. The ISPF option maintains sequencenumbers in 73-80 the sameway ISPF does.

DSS80021 "WIXX.RUNOPT.RESOLVESYSTEMSYMBOLS"

Explanation: Use Resolve System Symbols to resolve symbols in Started Task JCL.

Action: Specify Y when you want to scan Started Task jobs or procs and resolve any system symbols inthe source JCL. Specify Nwhen you want to bypass resolution of system symbols.

DSS80022 "WIXX.RUNOPT.CHECKTAPEDSNACCESS"

Explanation: Use Check TAPE DSNAccess for &1 to check if the user ID running the job has proper accessauthority to the tape datasets in the JCL.

Action: Specify Y to turn on the checking. If user does not have sufficient authority, &1 issues amessage about each tape dataset that could not be accessed. Specify N to turn off thechecking. This should be used if the RACF TAPEDSN option is not used.

DSS80023 "WIXX.RUNOPT.FIRSTPROCDD"

Explanation: Use Preferred Proclib DDNAME to specify a DDNAME to be searched ahead of the normalsearch order for cataloged procedures. The DD specified here, if allocated to the PRO/JCLstarted task or batch job, will be searched ahead of the normal search order when looking forcataloged procedures.

DSS80024 "WIXX.RUNOPT.FIRSTLOADDD"

Explanation: Use Preferred Loadlib DDNAME to specify a DDNAME to be searched for programs beforeSTEPLIB, JOBLIB or LPA. The DD specified here, if allocated to the PRO/JCL started task or batchjob, will be searched ahead of the normal search order to verify the existence of programs.

DSS80025 "WIXX.RUNOPT.CONTROLCARDDD"

138


Explanation: Use Preferred Control Card DDNAME to specify a DDNAME to be searched for control cardmembers before the dataset coded. The DD specified here, if allocated to the PRO/JCL startedtask or batch job, will be searched first for control card members.

DSS80026 "WIXX.RUNOPT.OUTPUTPDSENQ"

Explanation: Use Output PDS ENQ to specify how to allocate the OUTPUT libraries that are used for Reformator JMP. Specify EXCLUSIVE to allocate the Output libraries as DISP=OLD. Specify SHARED toallocate the Output libraries as DISP=SHR.

DSS80027 "WIXX.RUNOPT.PROCESSICEGENER"

Explanation: Use Process ICEGENER to enable validating ICEGENER control statements.

Action: Specify Y when you want &1 to validate ICEGENER control statements. Specify Nwhen youwant &1 to ignore ICEGENER control statements.

DSS80028 "WIXX.RUNOPT.PROCESSIEBGENER"

Explanation: Use Process IEBGENER to enable validating IEBGENER control statements.

Action: Specify Y when you want &1 to validate IEBGENER control statements. Specify Nwhen youwant &1 to ignore IEBGENER control statements.

DSS80029 "WIXX.RUNOPT.PROCESSIEHLIST"

Explanation: Use Process IEHLIST to enable validating IEHLIST control statements.

Action: Specify Y when you want &1 to validate IEHLIST control statements. Specify Nwhen you want&1 to ignore IEHLIST control statements.

DSS80030 "WIXX.RUNOPT.PROCESSIEHPROGM"

Explanation: Use Process IEHPROGM to enable validating IEHPROGM control statements.

Action: Specify Y when you want &1 to validate IEHPROGM control statements. Specify Nwhen youwant &1 to ignore IEHPROGM control statements.

DSS80031 "WIXX.INTERFACES.CAC"

Explanation: Use Catalog Access to check the system catalog.

Action: Specify Y to check the system catalogs for datasets coded in the JCL. Specify N to assume thatthe catalog matches the JCL without checking.

DSS80032 "WIXX.INTERFACES.CATALOGALIASCNT"

Explanation: Use Catalog Alias Cnt (count) to specify the number of nodes in a catalog alias at your site.

l Make changes to this value only if your site's Multi-Level Alias Facility (MLAF) node count haschanged.

l This valuemust not be greater than 4.

DSS80033 "WIXX.INTERFACES.CONTROLMRESOLVE"

139

System Messages

Explanation: Use CONTROL-M Resolve to indicate you want processing to stop when CONTROL-M cannotresolve a variable.

Action: Specify YES/MUST to tell &1 to stop processing when CONTROL-M cannot resolve a variable.Specify NO to tell &1 to continue processing even when CONTROL-M cannot resolve a variable.

DSS80034 "WIXX.INTERFACES.CVOL"

Explanation: Use CVOL to specify that your site uses CVOL catalogs.

Action: If your site has CVOL catalogs, set this option to Y. If your site does not have CVOL catalogs, setthis option to N.

DSS80035 "WIXX.INTERFACES.DAGLOBAL"

Explanation: Use DAGLOBAL to specify the location of the dataset CONTROL-M uses to resolve variables.

Action: Specify a fully-qualified dataset name.

DSS80036 "WIXX.INTERFACES.DB2DATABASENAME"

Explanation: The name of the repository.

Action: Specify any valid data base name. This namemust be bound to the plan name for INFO/X toaccess the repository.

DSS80037 "WIXX.INTERFACES.DB2PLANNAME"

Explanation: The name of the plan bound to the data base.

Action: Specify any valid plan name. The namemust be bound to the data base name for INFO/X toaccess the repository.

DSS80038 "WIXX.INTERFACES.DB2SUBSYSTEM"

Explanation: The name of the DB2 subsystem where the data base is located.

Action: Specify any valid subsystem name.

DSS80039 "WIXX.INTERFACES.DB2VERSION"

Explanation: Use DB2 Version to specify the DB2 version used when validating DB2 control statements.

DSS80040 "WIXX.INTERFACES.SQLBLOCKSIZE"

Explanation: Use SQL Block Size to specify the block size of result set data that is returned by the DB2database. This option applies only to INFO/X.

DSS80041 "WIXX.INTERFACES.DMSVOL"

Explanation: Use DMSVOL to specify the volume serial in theMVS catalog which represents datasetsarchived by Data Management System (DMS).

The DMSVOL VOLSER value must equal the volume serial coded in the RECATVOLVvvvvvparameter of DMS SYSPARMS.

DSS80042 "WIXX.INTERFACES.HMSVOL"

140


Explanation: Use HSMVOL to specify the volume serial in theMVS catalog which represents datasetsarchived by Hierarchical StorageManagement (HSM).

DSS80043 "WIXX.INTERFACES.IAM"

Explanation: Use IAM to enable simulation of IAM file support for VSAM files.

DSS80044 "WIXX.INTERFACES.IMS"

Explanation: Use IMS to specify whether &1 validates DFSRRC00 parameters.

Action: Specify Y to validate DFSRRC00 parameters. Specify N to ignore DFSRRC00 parameters.

DSS80045 "WIXX.INTERFACES.IMSVERSION"

Explanation: Use IMS Version to specify the IMS level &1 uses when validating IMS control statements.

Action: Specify a valid IMS release number (example, 3.4).

DSS80046 "WIXX.INTERFACES.JES"

Explanation: Use this option to tell &1which JES system it should simulate.

DSS80047 "WIXX.INTERFACES.JOBTRACSCL"

Explanation: Use CA-Jobtrac SCL to point to the dataset which holds CA-Jobtrac SCHEDULE CONTROLLANGUAGE (SCL).

Action: Specify a fully-qualified name for the SCL dataset.

DSS80048 "WIXX.INTERFACES.JOBTRACVARIABLES"

Explanation: Use CA-Jobtrac Variables to specify the name of the dataset where &1 looks for the JMFSYM01and PRODDATEmembers.

Action: Specify a fully-qualified dataset namewhere the JMFSYM01 and PRODDATEmembers arelocated.

DSS80049 "WIXX.INTERFACES.PANEXEC"

Explanation: Use PANEXEC to specify whether &1 allocates any PECNTL DD statements found in the jobbeing processed.

Action: Specify Y to allocate PECNTL DD statements so proper control information is available to thePANEXEC module for verifying program names in load libraries under control of PANEXEC.Specify N if your JCL does not have PECNTL DD statements.

DSS80050 "WIXX.INTERFACES.SECURITYSYSTEM"

Action: Specify the security interface &1 simulates. The default value is RACF.

DSS80051 "WIXX.INTERFACES.SMSACSROUTINES"

Explanation: Determines whether &1 accesses the Automatic Class Selection (ACS) routines and theConstruct Access Services (CAS) of theMVS DFSMS subsystem.

Action: Specify Y to access the ACS routines during validation of JCL. Specify N to prevent access to ACSroutines during validation.

141

System Messages

l The DFSMS subsystem provides information needed to validate and document JCL DD statementsused to allocate new datasets.

l The ACS routines provide selected constructs (DATACLAS, STORCLAS, and MGMTCLAS names) inthe sameway MVS allocations obtain them.

l The SMS ACS Routines Option is ignored if the SMS subsystem is not active during &1 execution. IfSMS is active on your system and you specify NO for this option, output to the SJL might beunpredictable when the input JCL contains SMS keywords or relies on SMS for implied requiredparameters.

DSS80052 "WIXX.INTERFACES.SMSACSSOURCE"

Explanation: Workstation option for ACS Routine processing.

Action: Specify USER to simulate ACS routines during validation of JCL. Specify SMS to call ACS routinesduring validation of JCL.

DSS80053 "WIXX.INTERFACES.SMSCLASS"

Explanation: Use SMS Class to validate SMS statements with the class specified in the SMS Class Source.

Action: Specify Y to validate SMS classes. (For this setting &1 validates classes regardless of whetherSMS ACS is Y or N.) Specify N to disable validation of SMS classes.

The SMS Class option verifies classes specified in JCL and selected by ACS routines (if SMSACS Routines is Y), and provides dataset attributes (such as SPACE and DCB information).

DSS80054 "WIXX.INTERFACES.SMSCLASSSOURCE"

Explanation: Workstation option for SMS so &1will knowwhere to get SMS information.

Action: Specify USER and &1will not query SMS. Specify SMS and &1will query SMS.

DSS80055 "WIXX.INTERFACES.SMSDEFAULTUNIT"

Explanation: Use SMS Default Unit to specify the unit name that SMS supplies when allocating new non-SMSmanaged datasets.

Action: Specify a unit name to be used for all non-SMS allocations that do not specify a unit name inthe JCL.

DSS80056 "WIXX.INTERFACES.TAPEMANAGER"

Explanation: Use TapeManager to specify the tapemanagement system &1 should use during JCLvalidation. Use TMS to specify the CA-TMS tapemanagement system is a release prior torelease 5. Use TMS5 to specify the CA-TMS tapemanagement system as release 5 or greater.Use ZARA to specify the ZARA tapemanagement system (any release).

DSS80057 "WIXX.RUNOPT.STOREDSNFORDUMMYDD"

142


Explanation: Use Unrecognized Statement Limit to limit the processing of unregocnized SYSIN statements. Ifthis limit is reached before finding a recognized control card then processing of the SYSINwill bestopped. If a recognized control card is found before this limit then processing will not bestopped. Specify 0 for no limit.

DSS80058 "WIXX.INTERFACES.VTOC"

Explanation: Use VTOC to specify whether the DASD VTOCs are accessed for dataset information.

Action: Specify Y to access the volume specified in the JCL to determine if the datasets are actuallylocated on that volume. Specify N to prevent VTOC access.

DSS80059 "WIXX.INTERFACES.ZEKESUBSYSTEM"

Explanation: Use ZEKE Subsystem option to specify the name of the ZEKE subsystem.

Action: Specify any valid ZEKE subsystem name. The default ZEKE subsystem name is SSSI.

DSS80060 "WIXX.INTERFACES.ZARASUBSYSTEM"

Explanation: Use ZARA Subsystem option to specify the name of the ZARA subsystem used at your site.

Action: Specify any valid ZARA subsystem name up to 4 characters, beginning with national oralphabetic character followed by up to 3 national or alphanumeric characters. The default ZARAsubsystem name is ZARA.

DSS80061 "WIXX.INTERFACES.TLMSVMF"

Explanation: Use TLMS VolumeMaster File to specify themaster file that contains the TLMS database.

Action: Specify Y to enable DASD volume checking. Specify N to disable DASD volume checking.

DSS80062 "WIXX.INTERFACES.DSSVERSION"

Explanation: Use DSS Version to specify the version used when validating DFSMSdss control statements.

DSS80063 "WIXX.INTERFACES.JOBTRACDATEFORMAT"

Explanation: Use CA-Jobtrac AJO Date to specify the form of the AJO datemasks used in CA-Jobtrac JCL.

DSS80064 "WIXX.INTERFACES.OPCADID"

Explanation: Enter the name of the Application Description for &1 to use for TWS simulations. This must bethe ADID created for &1 during the install process.

DSS80065 "WIXX.INTERFACES.IOPLUS"

Explanation: Use IOPLUS for &1 to simulate allocation of a DD used to invoke an IOPLUS VSAM Report.

DSS80066 "WIXX.INTERFACES.CA7DFLTSCHID"

Explanation: Use CA7 Default Schedule ID to specify which ID to use if none is specified.

Action: Specify an ID number from 1 through 255 or ALL or ONLY.

DSS80067 "WIXX.INTERFACES.JESEXIT"

Explanation: Use JES Submit Exit to specify the valid member name of the exit you want invoked.

143

System Messages

DSS80068 "WIXX.INTERFACES.JESEXITPARM"

Explanation: Use JES Exit Parm to specify the character string needed for the JES Submit Exit.

DSS80070 "WIXX.FORMATOPTION.DATEFORMAT"

Explanation: Use Dateformat to specify the format of the date on all the reports. MM Two digit month. DDTwo digit day. YYYY Four digit year. YY Two digit year.

DSS80071 "WIXX.FORMATOPTION.FLAGPAGE"

Explanation: Use Flagpage to print out a title page in the reports.

Action: Use Y to print a title page. Use N to suppress a title page.

DSS80072 "WIXX.FORMATOPTION.HEADINGS"

Explanation: Use Y to print headings. Use N to suppress headings.

DSS80073 "WIXX.FORMATOPTION.PAGELENGTH"

Explanation: Use Pagelength to specify howmany lines to print on each page.

Action: Specify a number from 24 to 80.

DSS80074 "WIXX.FORMATOPTION.REPORTFOOTING"

Explanation: Use Report Footing to specify whether &1 includes a footing on each page of the reports.

Action: Use Y to include a footing. Use N to exclude footing.

DSS80075 "WIXX.FORMATOPTION.REPORTWIDTH"

Explanation: Use Report Width to specify howwide the reports should be.

Action: Specify a number up to 132.

DSS80076 "WIXX.FORMATOPTION.UPPERCASEONLY"

Explanation: Use Uppercase Only to specify whether &1 prints the reports in all uppercase.

Action: Specify Y to force all uppercase printing. Specify N to print in mixed case.

DSS80077 "WIXX.INTERFACES.HSMVOL"

Explanation: Use HSMVOL to specify the VOLSER as the pseudo-VOLSER recorded in theMVS catalog thatrepresents datasets archived by Hierarchical StorageManagement.

DSS80078 "WIXX.INTERFACES.JOBTRACDFLTLOC"

Explanation: Use CA-Jobtrac Location to define a default location if one is not specified on the inputstatement.

DSS80079 "WIXX.INTERFACES.OASISDELIMITER"

Explanation: Use OASIS Delimiter to define what characters are coded on OASIS records. IF this option is notcoded, '$(' will be used.

DSS80080 "WIXX.INTERFACES.OASISSUBSYSTEM"

144


Explanation: Use OASIS Subsystem to define the name of the OASIS subsystem.

Action: If a value is coded and the ZEKE scheduler is selected, OASIS variables will be processed.

DSS80081 "WIXX.INTERFACES.TWSCOMPLETE"

Explanation: Use TWS Mark ADID Complete to indicate what PRO/JCL should do with the status of the ADIDused for simulation.

Action: If 'Y' is coded the ADID will bemarked complete after the first use. If 'N' is coded the status willnot be changed.

DSS80082 "WIXX.RUNOPT.SORTREQUIRESSYSOUT"

Explanation: Use SORT Requires SYSOUT to indicate if a SYSOUT DD statement is required.

Action: If 'Y' is coded, a SYSOUT DD is required when executing a SORT utility program. If 'N' is coded, aSYSOUT DD is not required.

DSS80083 "WIXX.INTERFACES.TWSTERMEQQYCOM"

Explanation: Terminate EQQYCOM.

Action: If 'Y' &1will terminate EQQYCOM after each JCLPREPA. Otherwise EQQYCOM will be terminatedwhen all processing is completed.

DSS80084 "WIXX.INTERFACES.TWSADID"

Explanation: Use TWS Default ADID to specify the name of the TWS ADID PRO/JCL uses for Not Foundprocessing. Not Found processing occurs when using the edit macro and the specified JOB is'not found' in the Application Database or the Current Plan. A temporary application will becreated/deleted in the AD to associate with that JOB. The temporary TWS default ADIDspecified heremust be unique to the Application Database.

DSS80085 "WIXX.INTERFACES.TWSDFLTWS"

Explanation: Use TWS Default WorkStation to specify the name of the TWS WorkStation PRO/JCL uses forNot Found processing. Not Found processing occurs when using the edit macro and thespecified JOB is 'not found' in the Application Database or the Current Plan. A temporaryapplication will be created/deleted in the AD to associate with that JOB. This value is used inconjunction with the TWS Default ADID RTS setting for creation of the temporary application.

DSS80086 "WIXX.INTERFACES.TWSDFLTOP"

Explanation: Use TWS Default Operation No to specify the number of the TWS Operation PRO/JCL uses forNot Found processing. Not Found processing occurs when using the edit macro and thespecified JOB is 'not found' in the Application Database or the Current Plan. A temporaryapplication will be created/deleted in the AD to associate with that JOB. This value is used inconjunction with the TWS Default ADID RTS setting for creation of the temporary application.

DSS80091 "WIXX.JCLLISTINGREPORT.CNTLCARDPRINT"

Explanation: Use Control Card Printing to: - print or not print control statements –

145

System Messages

Action: Specify a limit of howmany control statements are printed. Y turns on the values in the ControlCard Printing Table. N turns off the values in the Control Card Printing Table. LIMIT is an integerspecifying themaximum number of control statements printed. If the option is Y, the programand DD are checked to see if an entry exists. If the program and DD are not coded, then thedataset name is checked to see if it was coded in the options. The number of statements toprint is specified with the program or dataset options. The control statements can be printed inthe SJL. The IBM Utility programs' (IDCAMS, IEBCOPY etc.) control statements will always beprinted.

DSS80092 "WIXX.JCLLISTINGREPORT.ERRORLEVEL"

Explanation: Use Error Level to specify themessage levels included in the report. There are three types ofmessages: Error, Warning, and Informational.

Action: Use ALL to print all levels of error messages. Use E to print only the errors. Use EW to print onlythe errors and warnings. Use a number between 0 and 20 to print the specified level and higher.

DSS80093 "WIXX.JCLLISTINGREPORT.ERRORSUMMARY"

Explanation: Use Error Summary to specify if the Error Summary is printed and the location of the summaryin the report relative to the job.

Action: Use BYJOB to print the errors at the end of each job. Use BYRUN to print errors at the end ofthe entire SJL report. Use BYRUNFIRST to print Error Summary for the entire run before the SJLreport. Use BYJOBFIRST to print Error Summary for each JOB before the SJL Report. Use ONLYto print only the Error Summary. Use NONE to exclude the Error Summary in the SJL.

DSS80094 "WIXX.JCLLISTINGREPORT.JCLPRINTING"

Explanation: Use JCL Printing to specify if any JCL is printed and the content of the JCL section.

Action: Specify ALL to cause all the JCL, PROCS and errors to print out in the report. Specify EO (ErrorsOnly) to print the JCL only if themember has errors. Specify NOPROCS to prevent PROCs (withno errors) from printing in the SJL. Specify NONE to exclude the JCL section of the SJL (a NONEvalue will be ignored during a JJ).

DSS80095 "WIXX.JCLLISTINGREPORT.PRINTACCT"

Explanation: Use Print Accounting to specify whether the actual accounting data from the JOB statement isprinted in the SJL or * (asterisks).

Action: Specify Y to print actual accounting data. Specify N to print * (asterisks) in place of actualaccounting data.

DSS80096 "WIXX.JCLLISTINGREPORT.PRINTCHANGEDJOBS"

Explanation: Use Print Changed Job to specify whether PRO/JCL prints jobs that are changed.

Action: Specify Y to Print changed JOBs. Specify N to NOT print changed JOBs.

DSS80097 "WIXX.JCLLISTINGREPORT.PRINTPASSWORD"

Explanation: Use Print Password to specify whether the actual password data is printed in the SJL or whether* (asterisks) are substituted.

146


Action: Specify Y to print actual password data. Specify N to print * (asterisks) in place of actualpassword data.

DSS80098 "WIXX.JCLLISTINGREPORT.PRINTPDSMEMBERS"

Explanation: Use Print PDS Members to display all PDS members for control card datasets.

Action: Specify Y to display all PDS members for control card datasets. Specify N to NOT display all PDSmembers for control card datasets.

DSS80099 "WIXX.JCLLISTINGREPORT.ERRORSTATISTICS"

Explanation: Use Error Statistics to specify if Error Statistics are printed.

Action: Specify Y to include the Error Statistics section of the SJL. Specify N to exclude the ErrorStatistics section of the SJL.

DSS80100 "WIXX.JCLLISTINGREPORT.IOSTATISTICS"

Explanation: Use I/O Statistics to specify if I/O Statistics are printed.

Action: Specify Y to include the I/O Statistics section of the SJL. Specify N to exclude the I/O Statisticssection of the SJL.

DSS80101 "WIXX.RUNOPT.USEJES2PROCLIBDEFS"

Explanation: The PROCLIBS obtained from JES2will be concatenated after PROCLIBS specified in the RTSJesprocs table.

Action: Specify Y to search PROCLIBS from JES2 PROCLIB definitions. Specify N to disable this function.

DSS80110 "WIXX.RUNTIMESETTINGSREPORTFILES.OPTIONSINEFFECT"

Explanation: Use Options in Effect to print the current Run-Time settings.

Action: Specify Y to print the Options in Effect. Specify N to disable printing of Options in Effect.

DSS80111 "WIXX.RUNTIMESETTINGSREPORTFILES.TABLES"

Explanation: Use Tables to print all tables used in building the report.

Action: Use Y to print all tables. Use N to prevent printing of all tables.

DSS80112 "WIXX.RUNTIMESETTINGSREPORTFILES.TRACE"

Explanation: Use this option only with the direction of ASG Technologies Customer Support personnel.

DSS80113 "JCL.DD.LRECL"

Explanation: Use the LRECL parameter to specify the length of the records in a new dataset.

Action: Code the LRECL parameter when you want to Specify the logical record length for the dataset,or With SMS, override the record length defined in the data class of the dataset. LRECL appliesto datasets with the BPAM, BSAM, EXCP, QISAM, QSAM, and TCAM access methods, and withSMS, to VSAM datasets.

DSS80115 "WIXX.ENABLEDTABLES.ACS"

Explanation: Use this option to display ACS TABLE in the SJL when RTS REPORT option TABLES is set to Y.

147

System Messages

Action: Specify ON to display this table. Specify OFF to NOT display this table.

DSS80116 "WIXX.ENABLEDTABLES.ALIAS"

Explanation: Use this option to control the use of Utility Alias table entries.

Action: Specify ON to enable the use of the Utility Alias table entries. Specify OFF to disable the use ofthe Utility Alias table entries.

DSS80117 "WIXX.ENABLEDTABLES.CCDS"

Explanation: Use this option to control the use of Control Card DSN table entries.

Action: Specify ON to enable the use of the Control Card DSN table entries. Specify OFF to disable theuse of the Control Card DSN table entries.

DSS80118 "WIXX.ENABLEDTABLES.CONTROLCARD"

Explanation: Use this option to control the use of Control Card Print table entries.

Action: Specify ON to enable the use of the Control Card Print table entries. Specify OFF to disable theuse of the Control Card Print table entries.

DSS80119 "WIXX.ENABLEDTABLES.CSECTEXCLUDE"

Explanation: Use this option to display CSECT EXCLUSION TABLE in the SJL when RTS REPORT option TABLESis set to Y.


DSS80120 "WIXX.ENABLEDTABLES.DSPREF"

Explanation: Use this option to control the use of Dataset Preference table entries.

Action: Specify ON to enable the use of the Dataset Preference table entries. Specify OFF to disable theuse of the Dataset Preference table entries.

DSS80121 "WIXX.ENABLEDTABLES.DATELIBS"

Explanation: Use this option to control the use of CA-Jobtrac Alt LOC dataset table entries.

Action: Specify ON to enable the use of the CA-Jobtrac Alt LOC dataset table entries. Specify OFF todisable the use of the CA-Jobtrac Alt LOC dataset table entries.

DSS80122 "WIXX.ENABLEDTABLES.DDEXCLUDE"

Explanation: Use this option to control the use of DD Exclude table entries.

Action: Specify ON to enable the use of the DD Exclude table entries. Specify OFF to disable the use ofthe DD Exclude table entries.

DSS80123 "WIXX.ENABLEDTABLES.DDNAME"

Explanation: Use this option to control the use of Required DDNAMES table entries.

Action: Specify ON to enable the use of the Required DDNAMES table entries. Specify OFF to disable theuse of the Required DDNAMES table entries.

DSS80124 "WIXX.ENABLEDTABLES.DEVICES"

148


Explanation: Use this option to control the use of Device Types table entries.

Action: Specify ON to enable the use of the Device Types table entries. Specify OFF to disable the use ofthe Device Types table entries.

DSS80125 "WIXX.ENABLEDTABLES.EXITS"

Explanation: Use this option to display EXITS TABLE in the SJL when RTS REPORT option TABLES is set to Y.


DSS80126 "WIXX.ENABLEDTABLES.IMSACBDSNS"

Explanation: Use this option to control the use of IMS ACB Dataset table entries.

Action: Specify ON to enable the use of the IMS ACB Dataset table entries. Specify OFF to disable theuse of the IMS ACB Dataset table entries.

DSS80127 "WIXX.ENABLEDTABLES.JESPROCS"

Explanation: Use this option to control the use of JESPROC table entries.

Action: Specify ON to enable the use of the JESPROC table entries. Specify OFF to disable the use of theJESPROC table entries.

DSS80128 "WIXX.ENABLEDTABLES.DB2GROUPATTACH"

Explanation: Use this option to control the use of DB2 Group Attach table entries.

Action: Specify ON to enable the use of the DB2 Group Attach table entries. Specify OFF to disable theuse of the DB2 Group Attach table entries.

DSS80129 "WIXX.ENABLEDTABLES.MESSAGE"

Explanation: Use this option to control the use ofMessage table entries.

Action: Specify ON to enable the use of theMessage table entries. Specify OFF to disable the use of theMessage table entries.

DSS80130 "WIXX.ENABLEDTABLES.PROCS"

Explanation: Use this option to control the use of PROC Exclude table entries.

Action: Specify ON to enable the use of the PROC Exclude table entries. Specify OFF to disable the useof the PROC Exclude table entries.

DSS80131 "WIXX.ENABLEDTABLES.RETURNCODES"

Explanation: Use this option to control the use of Return Code table entries.

Action: Specify ON to enable the use of the Return Code table entries. Specify OFF to disable the use ofthe Return Code table entries.

DSS80132 "WIXX.ENABLEDTABLES.SMS"

Explanation: Use this option to display SMS TABLE in the SJL when RTS REPORT option TABLES is set to Y.


DSS80133 "WIXX.ENABLEDTABLES.SUBSYSTEMS"

149

System Messages

Explanation: Use this option to display SUBSYSTEMS TABLE in the SJL when RTS REPORT option TABLES is setto Y.


DSS80134 "WIXX.ENABLEDTABLES.TMSOUTOFAREACODES"

Explanation: Use this option to control the use of Tape Out of Area Code table entries.

Action: Specify ON to enable the use of the Tape Out of Area Code table entries. Specify OFF to disablethe use of the Tape Out of Area Code table entries.

DSS80135 "WIXX.ENABLEDTABLES.USERSPARMSCONTENTS"

Explanation: Use this option to display USER JMP PARMS TABLE in the SJL when RTS REPORT option TABLESis set to Y.


DSS80136 "WIXX.ENABLEDTABLES.USERUTIL"

Explanation: Use this option to control the use of User Utilities table entries.

Action: Specify ON to enable the use of the User Utilities table entries. Specify OFF to disable the use ofthe User Utilities table entries.

DSS80137 "WIXX.RUNOPT.PROGRAMMERNAMEREQUIRED"

Explanation: Use Programmer Name Required to require a programmer name on the JOBCARD of the JCLvalidated.

Action: Specify Y when the programmer name is required to be coded on the JOBCARD. Specify Nwhena programmer name is not required to be coded on the JOBCARD.

DSS80138 "WIXX.RUNOPT.REFORMATWERRORS"

Explanation: Use Reformat w/Errors to specify if changed or reformatted members with level errors less than8 are to be written.

Action: Specify Y when all changed or reformatted members are to be written. Specify Nwhen onlychanged or reformatted members with error levels less than 8 are to be written.

DSS80139 "WIXX.RUNOPT.REFORMATONCHANGE"

Explanation: Use Reformat On Change to specify if changed statements are to be automatically reformatted.

Action: Specify Y when statement changes are to cause reformatting. Specify Nwhen statementchanges are to not cause reformatting.

DSS80140 "WIXX.INTERFACES.SMFRECORDTYPE"

Explanation: Use this option to write SMF records.

Action: Specify a number from 128 to 255 if you want the product to write SMF records.

DSS80141 "WIXX.JCLLISTINGREPORT.PRINTOPESUMMARY"

Explanation: Use this option to specify if the Options In Effect Summary is to be printed.

150


Action: Specify Y to print the Options in Effect Summary in the SJL. Specify N to not print the Options inEffect Summary in the SJL. In Batch the OPE Summary will always be printed (this option will beignored).

DSS80142 "WIXX.ENABLEDTABLES.HSMMCDSN"

Explanation: Use this option to control the use of DFSMShsm MCDS table entries.

Action: Specify ON to enable the use of the DFSMShsm MCDS table entries. Specify OFF to disable theuse of the DFSMShsm MCDS table entries.

DSS80143 "WIXX.ENABLEDTABLES.LIBRARYTYPE"

Explanation: Use this option to control the use of Library Type table entries.

Action: Specify ON to enable the use of the Library Type table entries. Specify OFF to disable the use ofthe Library Type table entries.

DSS80144 "WIXX.RUNOPT.GLOBALEXIT"

Explanation: Specify a REXX exec that will be executed for each run.

Action: A valid REXX exec name only or the fully qualified dataset and member name of the REXX execor null valuemay be specified.

DSS80145 "WIXX.RUNOPT.GLOBALEXITPARM"

Explanation: Specify the parm that is to be passed to the Global Exit.

Action: Specify the parm that is to be passed to the Global Exit.

DSS80146 "WIXX.ENABLEDTABLES.CONTENTIONPERMITTEDDSNS"

Explanation: Use this option to control the use of Contention Permitted DSN table entries.

Action: Specify ON to enable the use of the Contention Permitted DSN table entries. Specify OFF todisable the use of the Contention Permitted DSN table entries.

DSS80147 "WIXX.RUNOPT.FOLTFILESIZE"

Explanation: Specify the allocation size of the FOLT file. The allocation sizes are in cylinders.

Action: Use these values to configure the FOLT file allocation: SMALL (8 primary, 32 secondary),MEDIUM (16 primary, 32 secondary), LARGE (32 primary, 32 secondary), XLARGE (64 primary, 32secondary).

DSS80148 "WIXX.RUNOPT.LOADJCLCOMMENTS"

Explanation: Use this option to specify whether or not JCL comments will be loaded into the INFO/Xrepository.

Action: Specify Y to load JCL comments. Specify N to prevent loading JCL comments.

DSS80149 "WIXX.RUNOPT.STATUSTHRESHOLD"

Explanation: Use Status Threshold setting to specify an interval (in records) between messages that indicatethe current total of records deleted. By default, a message is printed every 10000 deletedrecords.

151

System Messages

Action: This option applies only to INFO/X. Valid values are between 1 and 10000.

DSS80150 "WIXX.JCLLISTINGREPORT.ERRORSUMRETENTION"

Explanation: Use Error Summary Retention to specify the number of days to retain the Error Summary in thePCFILE.

Action: Specify 0 thru 31. The default is 4 days. If zero is specified, only themost recent Error Summarywill be kept in the PCFILE for the user requesting the validation.

DSS80151 "WIXX.RUNOPT.FREEUNUSEDFILEINTERVAL"

Explanation: Free Unused File Interval frees files that have been allocated but not used by the product forthe number of seconds specified.

Action: Specify 0 to keep files allocated for the duration of the run.

DSS80152 "WIXX.RUNOPT.PROCESSDB2UTILITIES"

Explanation: Use Process DB2 Utilities to validate DB2 utility control statements.

Action: Specify Y when you want &1 to validate DB2 utility control statements. Specify Nwhen youwant &1 to ignore DB2 utility control statements.

DSS80153 "WIXX.FORMATOPTION.REPORTDITTO"

Explanation: Use Report Ditto to display ditto marks when printing the INFO/X Reports from JCL or INFO/XReports from the Database.

Action: Specify Y to display ditto marks when column data is the same as the previous row's columndata. Specify N to suppress ditto marks. This will print the actual value of each column.

DSS80154 "WIXX.JCLLISTINGREPORT.PRINTSCHEDULERSTMTS"

Explanation: Print Scheduler Statements controls whether scheduler statements are to be printed in the SJL.

Action: If this option is Y, all scheduler statements will be printed along with codes that indicate thestatus of each record in an SJL. JJ will not display codes regardless of how this options is set. Ifthis option is N, only scheduler statements that have errors will be printed. JJ will displayscheduler statements that were originally coded in the edit work area. The default is Y.

DSS80155 "WIXX.RUNOPT.STOREDSNFORDUMMYDD"

Explanation: Use this option to specify if the DSN coded on a DD statement with 'DUMMY' coded will beloaded into the INFO/X repository. Specify Y to load the DSN coded. Specify N to not load theDSN coded. The default is N.

152


Return CodesThis topic contains PRO/JCL return codes that might appear in PRO/JCL execution messages.

Batch Execution of PRO/JCLWhen run in Batch, PRO/JCL issues one of these return codes when processing is completed:

Code Meaning

0 No error or warning messages were issued.

4 At least one warning message was issued, but no error messages were issued.

8 At least one error message was issued.

12 At least one severe error message was issued.

16 At least one critical error message was issued.

20 A fatal error message was issued. No scan was performed, at least for onemember.

153

Return Codes

Advanced Product Manager MessagesThis section will help you to identify and resolve problems that you may encounter while attempting to activate yourlicense or when the license is about to expire or when the license has expired.

ASGAPM011I "<pid> Product authorization will expire in <days> days"

The product authorization license key for the specified product identifier (pid) will expire in the specified number of days.You should contact ASG customer support to renew the product license key before the license expires. See ProductIdentifier Codes for a list of product identifier codes.

The specified PRO/JCL feature is licensed and enabled.

Contact ASG customer support to renew the product license.

ASGAPM012E "<pid> Product authorization has expired"

The Product authorization license key for the specified product identifier (pid) has expired and the product feature willnot be available. See Product Identifier Codes for a list of product identifier codes.

The specified PRO/JCL feature is not available.


ASGAPM013E "<pid> Product authorization invalid"

The product authorization license key for the specified product identifier (pid) is invalid and the product feature will notbe available. See Product Identifier Codes for a list of product identifier codes.


Contact ASG customer support to acquire the product license.

ASGAPM014E "<pid> Product authorization invalid for serial <serial>"

The product authorization license key for the specified product identifier (pid) is not valid for the specified processor serialnumber and the product feature will not be available. See Product Identifier Codes for a list of product identifier codes.



ASGAPM015E "<pid> Product authorization invalid for model <serial-model>"

The product authorization license key for the specified product identifier (pid) is not valid for the specified processorserial-model number and the product feature will not be available. See Product Identifier Codes for a list of productidentifier codes.


154



ASGAPM015E "Product authorization invalid MSU limit exceeded"

The product authorization license key MSU limit has been exceeded; the product license is no longer valid and theproduct feature will not be available.



ASGAPM016E "<pid> Product authorization not found"

The product authorization license key for the specified product identifier (pid) was not found and the product feature willnot be available. See Product Identifier Codes for a list of product identifier codes.



ASGAPM017E "<pid> Product authorization failure ASGPTBL not found"

The product authorization license table module ASGPTBL could not be located. The specified product identifier (pid)license key could not be verified and the product feature will not be available. See Product Identifier Codes for a list ofproduct identifier codes.


Verify that Step 2 - Installing PRO/JCL License Keys from the PRO/JCL Installation Guide has been completed.

ASGAPM021I "<pid> Product Evaluation period expires in <days> days"

The product evaluation license key for the specified product identifier (pid) will expire in the specified number of days.You should contact ASG customer support to extend the evaluation license before the license expires. See ProductIdentifier Codes for a list of product identifier codes.


Contact ASG customer support to extend the evaluation license.

ASGAPM022E "<pid> Product Evaluation Period has expired"

The product evaluation authorization license key for the specified product identifier (pid) has expired and the productfeature will not be available. See Product Identifier Codes for a list of product identifier codes.


Contact ASG customer support to renew the evaluation license.

ASGAPM031I "<pid> Temporary Product Auth expires in <days> days"

155

Advanced Product Manager Messages

The temporary product authorization license key for the specified product identifier (pid) will expire in the specifiednumber of days. You should contact ASG customer support to extend the temporary product license key before thelicense expires. See Product Identifier Codes for a list of product identifier codes.


Contact ASG customer support to extended the temporary product license.

ASGAPM032E "<pid> Temporary Product Authorization has expired"

The temporary product authorization license key for the specified product identifier (pid) has expired and the productfeature will not be available. See Product Identifier Codes for a list of product identifier codes.


Contact ASG customer support to renew the temporary product license.

ASGAPM033E "<pid> ASGAPMVer 2.1 is incompatible with this product"

ASG Advanced Product Manager version 2.1 product authorization routine was loaded from STEPLIB, JOBLIB or LINKLISTand is not compatible with PRO/JCL.



ASGAPM034E "<pid> install ASGAPM version <version> or higher"

ASG Advanced Product Manager product authorization routine was loaded from STEPLIB, JOBLIB or LINKLIST and is notcompatible with PRO/JCL.


Install the version of ASG Advanced Product Manager specified.

ASGAPM035I "<pid> ASGPTBL not properly assembled, ASGPRODE missing"

The product authorization license table module ASGPTBL contained structural errors. The specified product identifier(pid) license key could not be verified and the product feature will not be available. See Product Identifier Codes for a listof product identifier codes.



156


Product Identifier CodesThis topic contains the ASG-PRO/JCL Product Identifier(PID) Information.

The below table contains the list of Product Identifier codes that are used to identify a specific product.

Product Identifier (PID) Description

PIX INFO/X feature

PJM PRO/JCL feature

157

Product Identifier Codes

ASG-PRO/JCL Messages and Codes Guide

Documents

Transcript of ASG-PRO/JCL Messages and Codes Guide