ACC messages - syncsort_cobol_migration_manager - syncsort_clone_center - syncsort_space_recovery_system - syncsort_scc_monitor - syncsort_simulate_2000 - syncsort_allocation_control_center

ACC00320 DDNAME ddname VOLUME volser CHANGED TO DUMMY

Explanation: The ACCTRACE DD statement has been specified. This DD statement requested that rules tracing be used when scanning the rules language. This trace message gets issued when a DEFDMYV statement changes an allocation request to DUMMY for the specified ddname.

The DEFDMYV statement is used by ACC to convert the IDCAMS allocation to the volume into a DUMMY allocation. This is typically done for volumes specified in control cards that no longer exist. Converting to DUMMY will allow the ACCVSAM processing routines to pool the VSAM space request to the appropriate volume (volser). Note: Installations that have not enabled the ACCVSAM option should not use the DEFDMYV statement.

If the DEFDMYV statement does not specify a list of program names, the conversion to DUMMY DD statements can occur outside the IDCAMS processing environment. It is recommended to specify IDCAMS on the DEFDMYV statement definition.

Note: This trace message will only be issued if the ACCTRACE DD statement has been used to activate trace messages.

Message Level: None

Response: None

ACC00330 DDNAME ddname UNIT orgunit CHANGED TO UNIT newunit

Explanation: The ACCTRACE DD statement has been specified. This DD statement (ddname) requested that rules tracing be used when scanning the rules language. This trace message gets issued when a DEFDMYU statement changes an allocation request to use a newunit name.

Note: This trace message will only be issued if the ACCTRACE DD statement has been used to activate trace messages.

Message Level: None

Response: None

ACC00340 DATA SET type CHANGED TO NON-SPECIFIC

Explanation: ACC has determined that an allocation request specified an invalid volume. A previous message, ACC02310 or ACC02311, displayed information about the specified volume, pool definition, and data set name. Also, SPECIFIC(CHECKPOOL) was specified on the controlling pool definition or the DEFPROD statement.

For ACC controlled allocation requests, the unit specified on the allocation request was not found in the associated pool definition. The MODE parameter on the DEFPOOL statement determined whether the allocation was converted to nonspecific.

If the pool definition specified in ACC0231n was RESTNEW or RESTOLD, the current allocation request is for a non-ACC controlled allocation that has requested a restricted unit.

When RESTNEW is displayed, the specified device was restricted by a pool definition using RESTRICT(NEW). RESTOLD was restricted with RESTRICT(ALL).

If the pool definition specified in ACC0231n was RESTNEWD or RESTOLDD, the current allocation request is for a device reserved with the Dynapool facility.

The MODE operand on the DEFPOOL and DEFENV statements determine the type of ACC action. Non-ACC controlled allocations use the MODE from the DEFENV statement for the DD statement.

If MODE(WARN) was specified, the type field displays WOULD HAVE. Since ACC is working in warning mode, the product did not convert the specific allocation request to a nonspecific request. If MODE(ACTIVE) was specified, ACC will remove the specified unit(s), and display HAS in the message.

Message Level: A

Response: None

ACC00350 hdelete-message RC=(rc safrc safre)

Explanation: HDELETE=YES was requested by the ACC rules language in the DD or PRE-DD environment. The request failed. This message returns an error message and return codes. The rc displayed in the message can be related to a CAMLST, LOCATE, RACROUTE or ARCHDEL request -

see the related hdelete-message. The safrc and safre fields are obtained from the SAF parameter list used on the RACROUTE request (see SAFPRRET and SAFPRREA).

Message Level: E

Response: Please contact technical support.

ACC00351 MIGRATED DATASET DELETED WITHOUT RECALL : dsname

Explanation: HDELETE=YES was requested by the ACC rules language in the DD or PRE-DD environment. The request was successful. This message displays the dsname of the data set that was deleted.

Message Level: A

Response: None

ACC00400 FIELD DUMP FOR env-envs, dsname, ddname

Explanation: A symbolic field dump was requested by using a ddname that begins with ACCGETF, or a VSAM DEFINE with an HLQ that begins with ACCGETF. The ACCGETF interface is typically used for rule debugging. The facility has entered the trace environment displayed in env- envs. The dsname and ddname are also displayed.

Message Level: None

Response: None

Explanation: During SRS ADDVOL processing, the product attempted to create a JFCB extension. The request failed.

Message Level: E

Response: Please contact technical support.

ACC00430 POOL poolname DOES NOT EXIST

Explanation: The rules language has requested

poolname on a SET DISKPOOL, TAPEPOOL, DATAPOOL,

or INDXPOOL statement. ACC failed to locate the requested pool name.

Message Level: E

Response: This is an internal ACC or SRS error. Rule validation has ensured that the pool already exists. Please contact technical support.

ACC00440 POOL poolname DOES NOT EXIST

Explanation: The rules language has requested

poolname on a SET DISKPOOL, TAPEPOOL, DATAPOOL,

or INDXPOOL statement. ACC failed to locate the requested pool name.

Message Level: E

Response: This is an internal ACC or SRS error. Rule validation has ensured that the pool already exists. Please contact technical support.

ACC00510 STARTING TRACE FOR env-envs, DSN=dsname, VOL=volser, DD=dsname

Explanation: ACC - The ACCTRACE DD statement has been specified. This DD statement requested that ACCRULES tracing be used when scanning the rules table. Since ACC and SRS can intercept a DD request at several points during the allocation process, this message specifies the current tracing environment. The data set name and any specified volume are also displayed.

SMS/Debug- SMS/Debug has entered the trace environment displayed in env-envs. The data set name (dsname) and volume (volser) are also displayed. A ddname will also be displayed when available.

Message Level: None

Response: None

ACC00650 VALID OPTIONS ARE:

Explanation: An SRS recovery parameter has specified OPER. The operator will be prompted via WTOR for the recovery parameters. The valid parameters for the current recovery environment are listed with this message.

Message Level: None

Response: Please reply to the WTOR with one of the listed recovery parameters.

ACC00651 INVALID REPLY - parameter

Explanation: An SRS recovery parameter has specified OPER. The operator will be prompted via WTOR for the recovery parameters. The valid parameters for the current recovery environment are listed with the message ACC00650. Please select one of the valid options.

Message Level: None

Response: Please select one of the valid options listed on the message ACC00650.

Explanation: The DCC DLMALLOC component pooled a DLM tape request and used the load balancing algorithm to spread the allocation request between the VTEs in the DLm.

The ACC00730 messages display information about the ddname being pooled, and the condition of each VTE at allocation time - the totalnum of available units in the pool and the current number already allocated to jobs.

Note: This message is only displayed if rule tracing has been activated - a //DLMTRACE DD DUMMY statement has been allocated to the job.

Message Level: None

Response: None

ACC00731 VTE vtename - RC=rc / error-type)

Explanation: The DCC High Availability (HA) option targets large customer installations with multiple DLm configurations and offsite replicated tape libraries. This option allows installations to seamlessly redirect tape allocation requests away from a failed DLm, or more likely a failed internal DLm component. The HA option has been configured for your installation.

The ACC00731 messages display information about the VTE (vtename) being monitored, and information returned from each monitor request (rc and error-type).

Note: This message is only displayed if rule tracing has been activated - a //DLMTRACE DD DUMMY statement has been allocated to the job.

Message Level: None

Response: None

ACC00732 VTE vtename IS READ ONLY

Explanation: The DCC High Availability (HA) option targets large customer installations with multiple DLm configurations and offsite replicated tape libraries. This option allows installations to seamlessly redirect tape allocation requests away from a failed DLm, or more likely a failed internal DLm component. The HA option has been configured for your installation.

The High Availability (HA) option queried the requested library through the VTE (vtename) specified in the message and found that the back-end storage device is available, but mounted as read-only.

Note: This message is written as a WTO to the system console.

Message Level: None

Response: None

ACC00733 VTE vtename IS OFFLINE

Explanation: The DCC High Availability (HA) option targets large customer installations with multiple DLm configurations and offsite replicated tape libraries. This option allows installations to seamlessly redirect tape allocation requests away from a failed DLm, or more likely a failed internal DLm component. The HA option has been configured for your installation.

The High Availability (HA) option queried the requested library through the VTE (vtename) specified in the message and found that the back-end storage device has gone offline.

Note: This message is written as a WTO to the system console.

Message Level: None

Response: None

ACC00734 VTE vtename IS NOT BEING MONITORED - RC=rc

Explanation: The DCC High Availability (HA) option targets large customer installations with multiple DLm configurations and offsite replicated tape libraries. This option allows installations to seamlessly redirect tape allocation requests away from a failed DLm, or more likely a failed internal DLm component. The HA option has been configured for your installation.

The High Availability (HA) option queried the requested library through the VTE (vtename) specified in the message and received an unknown return code (rc). The HA option will no longer monitor the VTE until backend storage is made available, and a F DIF, REFRESH DLM console command is issued.

Note: This message is written as a WTO to the system console.

Message Level: None

Response: None

ACC00739 VTE vtename USED FOR DDNAME ddname

Explanation: The DCC DLMALLOC component pooled a DLM tape request and used the load balancing algorithm to spread the allocation request between the VTEs in the DLm. The ACC00739 message displays information about which VTE (vtename) was selected by the load balancing algorithm.

Message Level: A

Response: None

ACC00740 DD ddname UNIT SET TO newunit

Explanation: In a JES3 environment, the DCC DLMALLOC component pooled a DLM tape request and used the load balancing algorithm to spread the allocation request between the VTEs in the DLm by modifying the unit name. The ACC00740 message displays information about which esoteric unit (newunit) was selected by the DCC load balancing algorithm for JES3 processing.

Note: This message is only displayed if rule tracing has been activated - a //DLMTRACE DD DUMMY statement has been allocated to the job.

Message Level: None

Response: None

ACC00780 DD IGXMSGEX device BEFORE|AFTER MOUNT LOAD VALUE IS msg1 / msg2

Explanation: DCC can be used to dynamically assign scratch synonyms to jobs during job initiation. When the DLMSCR component is started, the product dynamically installs an IGXMSGEX exit. Once started, the DLMRULES member can be used to create policy rules to set the scratch synonym for scratch requests made by jobs.

Note: This message is only displayed if rule tracing has been activated - a //DLMTRACE DD DUMMY statement has been allocated to the job.

Two versions of the ACC00780 message can be produced. The BEFORE message displays the two message fields (msg1 / msg2) passed to the IGXMSGEX exit. If the DLMRULES set a scratch synonym, an AFTER message

displays the modified fields returned by the IGXMSGEX exit.

Message Level: None

Response: None

ACC01200 VOLUME TABLE TOO LARGE FOR ACC PROCESSING

Explanation: ACC intercepted a VSAM DEFINE request. The number of units specified in the DATA or INDEX component of the file exceeds twenty volumes. ACC does not have the internal resources to support more than twenty volumes for either component.

Message Level: E

Response: None

ACC01310 DATA SET type CHANGED TO NON-SPECIFIC

Explanation: ACC has determined that a VSAM allocation request specified an invalid volume. A previous message, ACC02310 or ACC02311, displayed information about the specified volume, pool definition, and data set name. Also, SPECIFIC(CHECKPOOL) was specified on the controlling pool definition.

For ACC controlled allocation requests, the volume specified on the define request was not found in the associated pool definition. The MODE parameter on the DEFPOOL statement determined whether the allocation was converted to nonspecific.

The MODE operand on the associated DEFPOOL statement determines the type of ACC action. If MODE(WARN) was specified, the type field displays WOULD HAVE. If ACC was working in warning mode, the product did not convert the specific allocation request to a nonspecific request. If MODE(ACTIVE) was specified, ACC removed the specified unit(s) and displayed HAS in this message.

Message Level: A

Response: None

ACC01320 VSAM DEFINE FAILED FOR volume- MOD=modid RC=(rtc-rsc)

Explanation: The ACCTRACE DD statement has been specified. This DD statement requested that ACCRULES tracing be used when ACC is attempting to perform nonspecific VSAM processing. An attempt was made using volume as the first unit in the data component. The attempt failed. The modid specifies the last two digits of the VSAM module that produced the return code (rtc) and reason code (rsc).

If the failure is considered recoverable, allocation with other volumes in the requested pool will be attempted. Once the units in the primary pool have been attempted, ACC will then attempt to use units in any alternate pool definitions. If no volumes work for the allocation attempt, ACC returns an error MOD=AC (68-20) to the program issuing the CATLG SVC.

Message Level: None

Response: None

ACC01321 VSAM DEFINE FAILED FOR dsname- MAXSPACE FAILED

Explanation: ACC attempted to allocate the VSAM file using the MAXSPACE algorithm as requested by the rules language. The pool did not have a volume with enough space to handle the DEFINE request. Since MAXSPACE was specified, and ACC already selected the volume with the most space, only one attempt was made to obtain the space. ACC returns an error MOD=AC (68-20) to the program issuing the CATLG SVC.

Message Level: E

Response: By adding an ACCTRACE DD statement to the step allocating the VSAM file, additional information can be obtained about the allocation attempt. ACC01320 will contain the return codes detailing why the attempt failed.

ACC01340 VSAM DEFINE FAILED FOR dsname - poolname LACKS SPACE

Explanation: ACC attempted to allocate the VSAM file in the poolname specified in the DISKPOOL operand. Neither the primary pool or any alternate pool(s) could handle the DEFINE request for dsname. ACC returns an error MOD=AC (68-20) to the program issuing the CATLG SVC.

You can also get this error when the pool definitions do not contain enough devices to satisfy the allocation request. For example, not enough volumes are available when VSAMSEP=YES is specified.

Message Level: E

Response: By adding an ACCTRACE DD statement to the step allocating the VSAM file, additional information can be obtained about each ACC allocation attempt.

ACC01320 will contain the return codes detailing why each attempt failed. Also, ensure that there are enough volumes in the device pool(s) to satisfy the allocation request.

ACC01380 DYNAMIC ALLOCATION FAILED FOR volume - RC=(r15-ec-ic)

Explanation: ACC was attempting to dynamically allocate to the volumes that were to be used in a DEFINE request. The dynamic allocation attempt failed. The RC field contains the decimal value of register 15 (r15), and the hexadecimal values for the error code (ec) and the information code (ic).

ACC will delete the volume from the list of eligible units, and attempt allocation on another volume in the pool.

Message Level: E

Response: Examine the Authorized Assembler Language Programs manual to obtain the return, error, and information codes specified in this message (GC28-1645). If the information does not help you solve the problem, contact technical support.

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. This message is issued if an I/O error occurs reading a directory or data track. The contents of the Event Control Block (ecb), the sense data from the IOB (sense), and the channel status word (csw) are displayed. Result: SRS does not add a directory block to the data set.

Message Level: E

Response: Please contact technical support.

ACC01607 I/O ERROR, SEEK= mbbcchhr

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. This message is issued if an I/O error occurs reading a directory or data track. The 8- byte seek address (mbbcchhr) in the IOB is displayed. Result: SRS does not add a directory block to the data set.

Message Level: E

Response: Please contact technical support.

ACC01608 MEM=memname ALIAS=y/n TTR=ttr CCHHR=cchhr

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. The message is issued for each directory member as the directory is read. The member name (memname), the alias indicator (y/n), the relative track and record number of the member (ttr), and the absolute cylinder and track number (cchhr) for the member are displayed.

This message is only produced when the ACCLOG DD DUMMY statement was specified in a test job. For product debugging, the ACCLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Message Level: None

Response: None

ACC01609 TTRNS=udttrns UDHWDS=udhwds

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. The message is issued for each directory member immediately after ACC10608 as the directory is read. For each member, it displays information from the user data fields in the directory entry - the number of user data TTRNs (udttrns) and user data halfwords (udhwds).

This message is only produced when the ACCLOG DD DUMMY statement was specified in a test job. For product debugging, the ACCLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Message Level: None

Response: None

ACC0160A DIRECTORY BLOCK NO. num PROCESSED

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. The message is issued after each directory block has been read and processed. This message will be issued once for each directory block in the data set.

This message is only produced when the ACCLOG DD DUMMY statement was specified in a test job. For product debugging, the ACCLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Message Level: None

Response: None

ACC0160B DIRBLKADD BYPASSED, RSN=text

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. This message is issued when SRS cannot add a directory block to a data set with a full directory. The reason is displayed in the message. The reason is displayed in the text field:

DATASET IS UNMOVABLE - SRS cannot add directory blocks to data sets with DSORG=POU.

DATASET HAS UNDEFINED RECFM - SRS cannot add

directory blocks to data sets with RECFM=U

EXCESSIVE DIR BLKS ON TRK - SRS has detected that there are more than 45 directory blocks on a track. While the data set may still be readable, this is an invalid condition and SRS will not add directory blocks to the data set. This can also occur if there is no space to add a directory EOF mark to the data set without extending the directory into an additional extent.

STOW MEMBER IS ON DIR TRK - If SRS is adding a

directory block due to a STOW failure, and the data blocks for the member for which STOW failed reside on the same track as the directory EOF mark, SRS cannot add a directory block (since it does not move the new member data).

LARGE BLOCK INTERFACE IN USE - SRS cannot add

directory blocks to an open PDS where the Large Block Interface (LBI, blocks larger than 32K) is in use.

DATASET ENQD BY OTHER JOB/DD - The data set is enqueued by another job or is referenced by another DD statement in the current job. This nogo condition may be overridden by specifying SET SKIP_ENQ or SKIP_STEPDSN in the SRS policy rules.

DATASET HAS USER DATA TTRNS - SRS cannot add

directory blocks to a PDS where any member has user data TTRNs. This error might occur when copying a data set with user data TTRNs. Directory blocks can be added to the target data set only until a member is copied which has user data TTRNs.

MEMBER HAS USER DATA TTRNS - SRS cannot add

directory blocks to a PDS where any member has user data TTRNs.

DATASET IS USING EXCP - SRS does not add directory blocks to a data set that is accessed with EXCP unless the SRS policy rules override this restriction by SETting the SRS SKIP_EXCP variable to YES.

DATASET HAS ALIAS MEMBERS - SRS cannot add

directory blocks to a data set in which any members have aliases.

MEMBER IS AN ALIAS - SRS cannot add directory blocks to a data set in which any members have aliases.

DIRECTORY FILLS FIRST EXTENT - SRS cannot add

directory blocks to a PDS where the existing directory fills the first extent of the data set. (PDS directories must be entirely contained within the first extent).

DATASET IS A PDSE - SRS cannot add directory blocks to a PDSE (library).

NO MEMBERS, DS1LSTAR = 0 - SRS will not add

directory blocks to a PDS with no members in it, or where the last block pointer (DS1LSTAR) is zero.

DATASET IS CONCATENATED - SRS will not add

directory blocks to a PDS which is a member of a concatenation.

EMPTY OR INVALID TRACK - SRS has discovered an empty or invalidly formatted track within the directory.

Although the data set may still be readable, SRS will not add directory blocks to the data set.

INVALID DIRECTORY - SRS has encountered a directory block with a length other than 256 bytes. SRS will not add directory blocks to the data set.

NO DIRECTORY EOF - SRS did not find an EOF mark in the directory. SRS will not add directory blocks to the data set.

INVALID USER DATA FIELD - SRS found a user data field in a directory entry with a length of more than 62 bytes. SRS will not add directory blocks to the data set.

INVALID VIRTUAL STORAGE - SRS attempted to obtain approximately 60K of virtual storage (GETMAIN or STORAGE OBTAIN) from subpool 230. The attempt to obtain storage failed. SRS will not add directory blocks to the data set.

Result: SRS does not add a directory block to the data set.

Message Level: E

Response: If you have questions, please contact technical support.

ACC0160C RE-READ DIRBLK TTR=ttr

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. The message indicates that a directory block has been successfully read during a second pass over the directory. The relative track and record number (ttr) of the directory block is shown.

This message is only produced when the ACCLOG DD DUMMY statement was specified in a test job. For product debugging, the ACCLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Message Level: None

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. SRS is about to move a member to make room on the last track of the directory for additional directory blocks. The cylinder and track number (cchhrkdd) and the first 20 bytes of the data being moved (dumpdata) are shown.

This message is only produced when the ACCLOG DD DUMMY statement was specified in a test job. For product debugging, the ACCLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Message Level: None

Response: None

ACC01634 DIRBLKADD LSTAR UPDATE TTR=ttr MBB=mbbcchhr

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. SRS has moved one or more members to make room for an additional directory block in the directory. The last-track pointer in the data set (DS1LSTAR) has been updated to point to the new end of the data set. The new relative track and record (ttr) and actual cylinder and track (mbbcchhr) are shown.

This message is only produced when the ACCLOG DD DUMMY statement was specified in a test job. For product debugging, the ACCLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Message Level: None

Response: None

ACC01635 MEMBER memname MOVED FROM TTR=ttr TO TTR=ttr

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. This is an informational message. SRS has moved the member (memname) indicated to make room for additional directory blocks in the directory. The original and new relative track and record (ttr) of the member that was moved are shown. Result: SRS has added a directory block to the data set.

Message Level: A

Response: None

ACC01636 I/O ERROR, ECB=ecb SENSE=sense CSW=csw

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. This message is issued if an I/O error occurs while writing a data block or EOF mark while moving a member. The contents of the Event Control Block (ecb), the sense data from the IOB (sense), and the channel status word (csw) are displayed. Result: SRS does not add a directory block to the data set.

Message Level: E

Response: Please contact technical support.

ACC01637 I/O ERROR, SEEK=mbbcchhr

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. This message is issued if an I/O error occurs while writing a data block or EOF mark while moving a member. The 8-byte seek address (mbbcchhr) in the IOB is displayed. Result: SRS does not add a directory block to the data set.

Message Level: E

Response: Please contact technical support.

ACC01639 DIRBLKADD WRITE CCHHRKDD=cchhrkdd DATA=dumpdata

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. SRS is moving a member to make room on the last track of the directory for additional directory blocks. The cylinder and track number (cchhrkdd) and the first 20 bytes of the data being moved (dumpdata) are shown.

This message is only produced when the ACCLOG DD DUMMY statement was specified in a test job. For product debugging, the ACCLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Message Level: None

Response: None

ACC0163A text

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. SRS is unable to add a directory block because of one of the following conditions:

INSUFFICIENT SPACE TO ADD A DIRECTORY

BLOCK - SRS could not add a directory block because there is not sufficient space at the end of the data set to hold the members that must be moved to make room for the new directory block. SRS requires some free space at the end of the data set if members must be moved (i.e., if the last track of the directory is full).

INSUFFICIENT SPACE TO BUILD CHANNEL

PROGRAM - SRS could not add a directory block because the member(s) that must be moved required a channel program of more than 100 channel commands.

INSUFFICIENT VIRTUAL STORAGE - SRS could not

add a directory block because it could not obtain sufficient virtual storage for an input or output data buffer (about 60K each from subpool 230).

Result: SRS does not add a directory block to the data set.

Message Level: E

Response: Please contact technical support.

ACC0163B DSCB UPDATE LSTAR=ttr

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. SRS is updating the last- track pointer (DS1LSTAR) field in the DSCB to point to the new last track and record in the data set. The new TTR is shown.

This message is only produced when the ACCLOG DD DUMMY statement was specified in a test job. For product debugging, the ACCLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Message Level: None

Response: None

ACC0163D MEMBER memname NEWTTRX=ttr

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. The NEWTTRX field indicates the new value for DS1LSTAR (ttr) that will be set when the member (memname) has been moved to the end of the data set.

This message is only produced when the ACCLOG DD DUMMY statement was specified in a test job. For product debugging, the ACCLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Message Level: None

Response: None

ACC0163E MEMBER memname NEWMBBC=mbbcchhr

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. The NEWMBBC field (mbbcchhr) indicates the new end of the data set in MBBCCHHR format that will be set when the member (memname) has been moved to the end of the data set.

This message is only produced when the ACCLOG DD DUMMY statement was specified in a test job. For product debugging, the ACCLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Message Level: None

Message Level: W

Response: None

ACC02311 POOL poolname DOES NOT ALLOW ACCESS TO VOLUME volume FOR dsname

Explanation: If an ACC controlled request specified a volume that does not reside the associated pool definition, and the SPECIFIC(NOFLOAT) parameter was requested on poolname, ACC will deny the allocation request.

If ACC has encountered a condition where a non-ACC controlled allocation has requested a restricted volume, the poolname will be RESTNEW or RESTALL. The pool definitions build these restricted lists via the RESTRICT(NEW) and RESTRICT(ALL) parameters.

If the pool definition specified in ACC02311 was RESTNEWD or RESTOLDD, the current allocation request is for a device reserved with the Dynapool facility.

Message Level: A

Response: None

ACC03350 KEEPAWAY VALUE FOR volume IS num

Explanation: The ACCMSG DD statement has been specified. This DD statement requested that all messages be displayed -- regardless of the message level. This message displays information about the KEEPAWAY selection algorithm used in the request. The volume name and the

Message Level: None

Response: None

ACC03752 SMS SELECTED VOLUME volser

Explanation: SMS/Debug has entered the SMS volume trace environment. This message displays the volume (volume) selected by SMS.

Message Level: None

Response: None

ACC03910 UCB DEVN devname ASSIGNED CODE: USER-%(8) IBM-%(8)

Explanation: xxxxxxxxx. Message Level: None Response: None

ACC05200 environment:DSN=dsname VOL=volser SIZE=tracks RC=rc

Explanation: xxxxxxxxx. Message Level: None Response: None

ACC05201 ALLOCATE FOR num units EXTENT

ext_num RC=rc - description

ACC20202 FAIL FLAG WAS SET

Explanation: SRS is capable of recovering the data set, but the ACC rules language has requested that EOV deny adding additional extents to the data set. The symbolic field JCLFAIL was set to “YES”.

Message Level: I

Response: None

ACC20210 type FOR DD=ddname DSN=dsname VOL=volser POOL=poolname EXT=num

Explanation: The ACC rules language is attempting a recovery. The type of recovery is specified in the message: ADDVOL, REDUCES, REDUCEP, SETSEC, or

ACC20500 SECONDARY SPACE REDUCED FROM old_value TO new_value units

Explanation: A data set required more space, and the secondary space request failed. The volume containing the data set could not provide the space, but the volume was only fragmented and not actually full. The REDUCES parameter on the pool definition allowed SRS to reduce the secondary space (old_value) requested for the data set. The new secondary value (new_value) is based on available space for the current volume.

Message Level: A

Response: None

ACC20501 CURRENT SECONDARY SPACE AMOUNT ALREADY TRIED

Explanation: A data set required more space, and the secondary space request failed. The volume containing the data set could not provide the space, but the volume was only fragmented and not actually full. The REDUCES parameter on the pool definition allowed SRS to reduce the secondary space request for the data set. The new secondary value is based on available space for the current volume, but the new value was to be greater than the original secondary request. Since another job has just freed the required space, SRS will retry the space request to obtain the original secondary.

Message Level: None

Response: None

ACC20502 VOLUME HAS NO FREE SPACE

Explanation: A data set required more space, and the secondary space request failed. The volume containing the data set could not provide the space, but the volume was only fragmented and not actually full. The REDUCES parameter on the pool definition allowed SRS to reduce the secondary space request for the data set. The attempt for the reduced secondary request also failed, and the volume no longer had any free space.

Note: VSAM allocates space based on the CA size. If SRS gets control to increase or decrease the space request, it must calculate the request as a multiple of the CA size.

Message Level: E

Response: If ADDVOL has been specified on the pool definition, SRS can obtain the required space by adding a volume.

ACC20503 SECONDARY SPACE WENT TO LIMIT

Explanation: A data set required more space, and the secondary space request failed. The volume containing the data set could not provide the space, but the volume was only fragmented and not actually full. The REDUCES parameter on the pool definition allowed SRS to reduce the secondary space request for the data set. The attempt for the reduced secondary request fell below the limit specified on REDUCES.

Message Level: E

Response: If ADDVOL has been specified on the pool definition, SRS can obtain the required space by adding a volume.

ACC20520 POOL DEFINITION DOES NOT ALLOW SECONDARY REDUCTION

Explanation: A data set required more space, and the secondary space request failed. The volume containing the data set could not provide the space, but the volume was only fragmented and not actually full. The device pool associated with the data set does not allow SRS to dynamically reduce a secondary value -- no REDUCES was specified on the DEFPOOL statement.

Message Level: I

Response: The associated ACC20210 message displays the name of the pool definition associated with the data set. To allow recovery, specify REDUCES on the DEFPOOL statement in the ACC rules language.

ACC20560 SPACE COULD NOT BE OBTAINED FOR DATA SET

Explanation: A data set required more space, and the space request failed. The rules language has enabled the SPACEFAIL environment to allow operator intervention. This SRS recovery option might be called the option of last resort. When neither the operating system nor SRS can provide space for a data set during EOV processing, the SPACEFAIL option can request that the operator get involved in finding or creating space for the data set.

Message Level: A

Response: The valid operator responses are CANCEL or RETRY. Since space problems are often caused by timing situations, many allocations can succeed by waiting for other jobs to complete before issuing RETRY. The operator can also make space available on a volume, or add another volume to the storage group or pool definition used by the data set. When RETRY is requested, the operating system will retry the space request, and if necessary SRS will attempt recovery on subsequent space problems. If the operator replies CANCEL, the job will terminate with a space failure.

ACC20600 VOLUME volser WAS ADDED TO DATA SET

Explanation: The data set used the maximum number of extents allowed on a volume, or no space is available on the current volume. The ADDVOL parameter on the pool definition allowed SRS to add another volume to the data set.

Message Level: A

Response: None

ACC20620 POOL DEFINITION DOES NOT ALLOW VOLUME ADDITION

Explanation: The data set used the maximum number of extents allowed on a volume, or no space is available on the current volume. The device pool associated with the data set does not allow SRS to dynamically add another volume -- no ADDVOL was specified on the DEFPOOL statement.

Message Level: I

Response: The associated ACC20210 message displays the name of the pool definition associated with the data set. To allow recovery, specify ADDVOL on the DEFPOOL statement in the ACC rules language.

ACC20621 DATA SET IS AT MAX VOLUMES

Explanation: The data set used the maximum number of extents allowed on a volume, or no space is available on the current volume. The ADDVOL parameter on the pool definition allowed SRS to add another volume to the data set, but the data set already existed on more volumes than allowed by ADDVOL. By default, SRS will not add additional volumes once the data set resides on two volumes.

Message Level: E

Response: The associated ACC20210 message displays the name of the pool definition associated with the data set. To allow recovery, use the MAXVOL subparameter on the ADDVOL parameter to raise the maximum volume limit.

For a VSAM KSDS, a single TIOT entry is used for both the data and index components. SRS will not perform ADDVOL if the TIOT is full, even if some of the slots in the TIOT contain SMS dummy volume entries.

Initially, there are at least as many SMS 'dummy' volume entries in the TIOT as there are entries for candidate volumes in the catalog for both components, subject to the limitation that the TIOT can accommodate a maximum of 59 volumes.

For example, if a cluster is defined with VOL(* * * * *) either in the DEFINE CLUSTER statement or in the dataclass, then there will be NINE volume entries in the TIOT; one 'real' volume for the data and index components, which are by default placed on the same volume, plus four dummy volume entries for each component. There are corresponding candidate volume entries in the catalog for component.

Note that the VOL parameter can be defined on the DATA component as VOL(V1 * * * *) and the INDEX component as VOL(V2 * * * *). In this example, this will result in TEN volume entries rather than nine, since specifying a different volser for the data and index components results in the two components being placed on separate volumes at the initial creation of the dataset.

If the VOL parameter is defined at the component level rather than the cluster level, then there will be enough dummy volumes in the TIOT to meet total number of volumes defined, e.g., if DATA VOL(* * *) and INDEX VOL(* * *) then there are a total of FIVE volumes in the TIOT, one 'real' volume for the data and index components and four dummies, two per component. If the VOL parameter is defined only at the DATA component level, e.g., DATA VOL(* * * * *) then there will be as many TIOT slots as volumes specified, in this example one real and 4 dummy. The same applies if the VOL parameter is specified only on the INDEX component.

SRS ADDVOL processing adds dummy volume entries to the END of the TIOT and adds candidate volumes to the catalog entry for a component. This occurs when a component has no more candidate volumes left in the catalog entry and IDAEOVXT is called. SRS ADDVOL processing will add a new dummy TIOT entry at the end of the TIOT (and add a candidate volume to the catalog) even though there may still be dummy entries present in the TIOT. This insures that dummy volumes are still available in the TIOT for the other component, which may not yet have exhausted it's candidate volumes in the catalog.

If a KSDS is initially DEFINEd with enough volumes to fill up all 59 available TIOT slots (e.g, 59 volumes specified in the cluster define, or say, 39 volumes on the data component and 20 on the index component, then SRS cannot ever perform ADDVOL processing because the TIOT is full. The data component in this case cannot extend to a 40th volume even though the index component may actually reside on only one volume. This can ALSO occur if SRS EXTENDS a component to additional volumes. As SRS adds dummy volume entries to the TIOT for a component (and candidate volumes to the catalog for the component), it uses up TIOT slots. Eventually, the TIOT may become full, even though some of the slots in the TIOT are dummy entries for candidate volumes that have not yet been used by the other component.

When this happens, this message is issued. Thus, a situation like the following could occur:

KSDS is defined with 10 candidate volumes at the cluster level. This results in 19 TIOT slots used (1 'real' entry for the first volume of the data and index components and 9 dummy entries for each component. There are also 9 candidate volumes in the catalog for each component in addition to the first 'real' volume.
As data is written to the dataset, the candidate volumes in the catalog (and their corresponding TIOT entries) are used. Usually, the data component extends to new volumes much more frequently than the index component. Eventually, when the 10th data volume is full, the candidate volumes in the catalog for the data component are exhausted. IDAEOVXT is then called and SRS gets control. SRS adds a candidate volume to the catalog entry for the data component and a new dummy volume entry at the end of the TIOT. This will occur multiple times as the data component extends.
If the data component extends to enough new volumes, eventually all the TIOT slots are filled. At this point, the data component may have extended to a total of 50 volumes. The index component, however, may never have extended to a new volume. There are at least 9 dummy volumes still left in the TIOT for it. So the dataset never gets to use the maximum 59 volumes it could extend to. It stopped at 50 volumes. SRS cannot perform further ADDVOLs because the TIOT is full, even though the last 9 volumes in the TIOT are dummy volumes.

Perhaps counterintuitively, REMOVING the dummy volumes from the DEFINE will allow SRS to add both catalog candidate volumes and dummy TIOT entries only as needed.

If the TIOT is completely full (59 volumes), and the last volume is an SMS dummy volume, then SRS need not add a volume to the TIOT at ADDVOL time in the usual way. SRS can simply return control to IDAEOVXT and indicate to retry the EOV. There is no danger that there will not be a dummy TIOT entry available for the other component when needed, since the TIOT is already full and if there are no more dummy slots available the extend must fail anyway. In all cases where the TIOT contains less than 59 volumes, ordinary ADDVOL processing can go ahead.

ACC20622 DATA SET IS PART OF A CONCATENATION

Explanation: The data set used the maximum number of extents allowed on a volume, or no space is available on the current volume. The ADDVOL parameter on the pool definition allowed SRS to add another volume to the data set, but the data set is part of a concatenated file. SRS cannot add another volume to this file. Note: This is a very unusual condition. Data set concatenation on output files would violate standards enforcement at most installations.

Message Level: E

Response: None

ACC20623 CURRENT VOLUME IS NOT PERMANENTLY MOUNTED

Explanation: The data set used the maximum number of extents allowed on a volume, or no space is available on the current volume. The ADDVOL parameter on the pool definition allowed SRS to add another volume to the data set, but the data set currently on a volume that is not permanently mounted by the operating system. SRS cannot add another volume to this file.

Message Level: E

Response: This may be an internal SRS error. Please contact SRS technical support.

ACC20624 DCB WAS NOT OPENED USING PS

Explanation: The data set used the maximum number of extents allowed on a volume, or no space is available on the current volume. The ADDVOL parameter on the pool definition allowed SRS to add another volume to the data set, but the data set was being accessed in a non-sequential manner. Since SRS cannot assume the application has random access multivolume support, SRS cannot add another volume to this file.

Message Level: E

Response: None

ACC20625 DCB IS USING EXCP

Explanation: The data set used the maximum number of extents allowed on a volume, or no space is available on the current volume. The ADDVOL parameter on the pool definition allowed SRS to add another volume to the data set, but the data set was being accessed directly from the application with channel programs -- EXCP processing. Since SRS cannot assume the application has random access multivolume support, SRS cannot add another volume to this file.

Message Level: E

Response: For applications that can handle EXCP processing on multivolume files, the SKIP_EXCP symbolic field can be used to bypass the SRS check for EXCP processing. For more information, examine “SRS Symbolic Fields to Bypass ADDVOL Checks” on page 5-3.

ACC20626 DCB IS USING NOTE/POINT

Explanation: The data set used the maximum number of extents allowed on a volume, or no space is available on the current volume. The ADDVOL parameter on the pool definition allowed SRS to add another volume to the data set, but the data set was being accessed using NOTE/POINT logic. Since SRS cannot assume the application has random access multivolume support, SRS cannot add another volume to this file.

Message Level: E

Response: For applications that can handle NOTE/ POINT processing on multivolume files, the SKIP_NOTE and SKIP_POINT symbolic fields can be used to bypass the related SRS checks. For more information, examine “SRS Symbolic Fields to Bypass ADDVOL Checks” on page 5-3.

WARNING: Applications that actually perform NOTE/ POINT processing to randomly position the current record pointer using POINT should NOT bypass this integrity check unless you have access to the application source code and understand how the application works. It’s extremely difficult to write software to reposition to a record found on a previous volume.

ACC20627 DATA SET DISPOSITION DOES NOT ALLOW RECOVERY

Explanation: The data set used the maximum number of extents allowed on a volume, or no space is available on the current volume. The ADDVOL parameter on the pool definition allowed SRS to add another volume to the data set, but the data set was being accessed without the use of the catalog. Since the JCL specifically allocated to the current device, any SRS recovery would cause data integrity problems for another job or step that accessed the data in the same manner. SRS cannot add another volume to this file.

Message Level: E

Response: While not recommended, the SKIP_CATLG symbolic field can be used to bypass the catalog check. For more information, examine “SRS Symbolic Fields to Bypass ADDVOL Checks” on page 5-3.

ACC20628 DATA SET IS PARTITIONED

Explanation: The data set used the maximum number of extents allowed on a volume, or no space is available on the current volume. The ADDVOL parameter on the pool definition allowed SRS to add another volume to the data set, but the data set is a PDS or PDSE, and neither format allows multi-volume files. This is a limitation of the OS/390 and z/ OS architecture.

Message Level: E

Response: None

ACC20629 DATASET IS SINGLE STRIPED/ TEMP

Explanation: A striped temporary data set ran out of space or extents on the current volume and needed to extend to a new volume. Sequential extended-format temporary data sets cannot be extended to additional volumes because SRS cannot create an NVR for these data sets.

Message Level: E

Response: Change the data set to be

non-extended-format (non-striped) or non-temporary and rerun the job.

Explanation: The ADDVOL parameter on the pool definition allowed SRS to add another volume (volser) to the data set. The ALGORITHM specified on the pool definition was used to select a device, but an allocation service routine failed to obtain the selected volume.

The RC field contains the decimal value of register 15 (r15), and the hexadecimal values for the error code (ec) and the information code (ic).

Message Level: E

Response: Please contact technical support.

ACC20810 VOLUME COULD NOT BE RELEASED

Explanation: The ADDVOL parameter on the pool definition allowed SRS to add another volume to the data set. The ALGORITHM specified on the pool definition was used to select a device, and SRS allocated to the new volume.

Unfortunately, an internal error prevented the new volume from being added to the data set. SRS attempted recovery, but the unallocate request for the new volume also failed. SRS cannot add a volume to this data set.

Message Level: E

Response: Please contact technical support.

ACC20820 TIOT UPDATE FAILED FOR ddname - RC=(rc-ec)

Explanation: The ADDVOL parameter on the pool definition allowed SRS to add another volume to the data set. The ALGORITHM specified on the pool definition was used to select a device, but an allocation service routine failed to update the TIOT entry for the file. SRS cannot add a volume to this data set.

The RC field contains the decimal value of register 15, and a hexadecimal value for the error code (ec).

Message Level: E

Response: Please contact technical support.

ACC20910 CATALOG FAILED FOR dsname volser RC=(r15-fb1-fb2)

Explanation: The ADDVOL parameter on the pool definition allowed SRS to add another volume (volser) to the data set. SRS was attempting recovery on a non-VSAM file. The ALGORITHM specified on the pool definition was used to select a device, but the RECATALOG request failed to add the new volume to the catalog.

The RC field contains the decimal values of register 15 (r15) and the feedback codes (fb1-fb2).

Message Level: E

Response: Please contact technical support.

ACC20920 CATALOG FAILED FOR dsname volser RC=(r15-fb1-fb2)

Explanation: The ADDVOL parameter on the pool definition allowed SRS to add another volume (volser) to the data set. SRS was attempting recovery on a VSAM file. The ALGORITHM specified on the pool definition was used to select a device, but the RECATALOG request failed to add the new volume to the catalog.

Explanation: When the operating system catalogs a new data set and a catalog entry already exists for the data set, the new catalog request fails. RECAT intercepted the failure and attempted to recataloged the data set. During RECAT processing, an uncatalog request failed.

Message Level: E

Response: Please contact technical support.

ACC26220 POOL DEFINITION DOES NOT ALLOW RECATALOG VOLUME volser

Explanation: When the operating system catalogs a new data set and a catalog entry already exists for the data set, the new catalog request fails. RECAT intercepted the failure and recataloged the data set. Since RECAT(SCRATCH) was requested on the pool definition, the data set was also scratched. Note: SMS controlled data sets are always scratched by RECAT

Message Level: A

Response: None

ACC26220 POOL DEFINITION DOES NOT ALLOW RECATALOG

Explanation: When the operating system catalogs a new data set and a catalog entry already exists for the data set, the new catalog request fails. RECAT can recatalog the data set, but the device pool associated with the data set does not allow RECAT to dynamically recatalog the new data set -- no RECAT was specified on the DEFPOOL statement.

Message Level: I

Response: The associated ACC20210 message displays the name of the pool definition associated with the data set. To allow recovery, specify the RECAT(YES) or RECAT(SCRATCH) option on the DEFPOOL statement in the ACC rules language.

ACC26221 POOL DEFINITION DOES NOT USE RECAT DUP OPTION

Explanation: While not technically a RECAT condition, the RECAT parameter can be used to recover from the “DUPLICATE NAME ON DIRECT ACCESS VOLUME”

situation by automatically scratching the original data set and letting the new allocation complete. However, the associated pool definition has not requested recovery for the duplicate data set problem.

Message Level: I

Response: The associated ACC20210 message displays the name of the pool definition associated with the data set. To allow recovery, specify RECAT(YES DUP) on the DEFPOOL statement in the ACC rules language.

ACC26300 CATALOG LOCATE FAILED - RC=rc

Explanation: When the operating system catalogs a new data set and a catalog entry already exists for the data set, the new catalog request fails. RECAT intercepted the failure and attempted to recataloged the data set. Unfortunately, the catalog request to locate the old volume list failed. RECAT cannot perform recovery.

Message Level: E

Response: Please contact technical support.

ACC26320 DADSM RENAME FAILED - RC=rc

(X’diag’) (volser-rs)

Explanation: The ACCRULES member has the EOFMARK environment set to active. When a non-SMS data set is created, the EOFMARK environment is used to write an End-Of-File marker. The EOF marker will ensure an EOF condition occurs if a subsequent job or step attempts to read from the data set before the data set has been opened for output. For more information, examine “EOFMARK” on page 4-26 in the ACC/SRS User’s Guide.

When ACC attempted to write the end of file marker, the channel program failed. This message displays the ecb, sense, and csw information.

Message Level: E

Response: Please contact technical support.

ACC29202 EOF MARK WRITTEN FOR DATA SET

Explanation: The ACCRULES member has the EOFMARK environment set to active. When a non-SMS data set is created, the EOFMARK environment is used to write an End-Of-File marker. The EOF marker will ensure an EOF condition occurs if a subsequent job or step attempts to read from the data set before the data set has been opened for output. For more information, examine “EOFMARK” on page 4-26 in the ACC/SRS User’s Guide.

The End of File marker was successfully written using EXCP.

Message Level: A

Response: None

ACC29203 DATA SET INITIALIZED

Explanation: The ACCRULES member has the EOFMARK environment set to active. When a non-SMS data set is created, the EOFMARK environment is used to write an End-Of-File marker. The EOF marker will ensure an EOF condition occurs if a subsequent job or step attempts to read from the data set before the data set has been opened for output. For more information, examine “EOFMARK” on page 4-26 in the ACC/SRS User’s Guide.

The End of File marker was successfully written using OPEN/ CLOSE.

Message Level: A

Response: None

ACC29600 DIRBLKADD MEM=memname FUNC=function RC=rc RSN=rn

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. This debugging message can be used to display the name of the PDS member processed (memname), the STOW function being requested, and the return code (rc) and reason code (rs).

This message is only produced when the DDLOG DD DUMMY statement was specified in a test job. For product debugging, the DDLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Message Level: None

Response: None

ACC29606 POOL DEFINITION DOES NOT ALLOW DIR BLOCK ADD FOR memname

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request, but the DEFPOOL definition used by the rules language did not allow DIRBLKADD recovery.

Message Level: I

Response: The associated ACC20210 message displays the name of the pool definition associated with the data set. To allow recovery, specify DIRBLKADD(YES) on the DEFPOOL statement in the ACC rules language.

ACC29607 IECPCNVT ERROR CONVERTING ttrn RC=rc

Explanation: The SRS DIRBLKADD function intercepted a PDS directory failure when creating a new member. During the recovery process, DIRBLKADD called the IECPCNVT system routine to convert a TTRN to a MBBCCHR. The request failed with return code (rc).

Message Level: None

Response: Please contact technical support.

ACC29608 DIRBLKADD DCBFDAD= mbbcchhr

Explanation: The SRS DIRBLKADD function intercepted a PDS STOW request. This debugging message can be used to display the last record (mbbcchhr) read or written by the DCB.

This message is only produced when the ACCLOG DD DUMMY statement was specified in a test job. For product debugging, the ACCLOG statement can be used to produce trace messages that are written to the JES message log. For example, when using an ACC/SRS debug job, the following DD statement can be used to produce debug messages that have a log level less than or equal to 8.

//ACCLOG DD DUMMY,DCB=LRECL=8

Log Level: 8

Message Level: None

Response: None

ACC29609 DIRBLKADD MEMBER memname IECPRLTV ERROR RC=rc mbbcchhr

Explanation: The SRS DIRBLKADD function intercepted a PDS directory failure when creating a new member (memname). During the recovery process, DIRBLKADD called the IECPRLTV system routine to convert an MBBCCHHR (mbbcchhr) to a TTRN. The request failed with return code (rc).

NO CDS SPECIFIED - Neither the data set name of a Source Control Data Set, nor 'ACTIVE' was specified in the CDS1= or CDS2= parameter of the SELECT statement. At least one CDS or 'ACTIVE' must be specified.

TESTLIB DATASET NOT SPECIFIED - No value was

This message follows message ACC80111 and shows the date, time, userid, source data set (dsname), and member name for the ACS routines for each CDS (cdsno).

Message Level: I

Response: None

ACC80120 errtxt IN MEMBER memname

Explanation: An error was found in a record in a testcase member (memname). This message is followed by the message ACC80121 which shows the record in error. errtxt indicates the type of error and will be one of the following values:

UNEXPECTED TESTCASE EOF - The end of the testcase data was reached but not all the testcase variables were found in the member.

UNRECOGNIZED TESTCASE DATA - Data was

encountered in the testcase member which is not in the correct format.

Message Level: E

Response: The testcase is malformed and should be rebuilt.

ACC80121 ** CARD IMAGE: cardimage

Explanation: This message is preceded by the message ACC80120. The card image (cardimage) shown is the testcase record in error.

Message Level: E

Response: Determine why the record is malformed. This may occur if the testcase was edited outside of ISMF or ACSQA. The testcase may need to be deleted and rebuilt.

ACC80130 ** errtxt

Explanation: ACSQA has encountered an error while invoking SMS Configuration Services. This message is followed by the message ACC80131. errtxt will be one of the following values:

UNABLE TO ALLOCATE CDS UNABLE TO DEALLOCATE CDS

UNABLE TO RETRIEVE ACS ROUTINE OBJECT

Message Level: E

Response: Contact Customer Support.

ACC00330 DDNAME ddname UNIT orgunit CHANGED TO UNIT newunit

ACC00340 DATA SET type CHANGED TO NON-SPECIFIC

ACC00350 hdelete-message RC=(rc safrc safre)

ACC00351 MIGRATED DATASET DELETED WITHOUT RECALL : dsname

ACC00400 FIELD DUMP FOR env-envs, dsname, ddname

ACC00430 POOL poolname DOES NOT EXIST

ACC00440 POOL poolname DOES NOT EXIST

ACC00510 STARTING TRACE FOR env-envs, DSN=dsname, VOL=volser, DD=dsname

ACC00650 VALID OPTIONS ARE:

ACC00651 INVALID REPLY - parameter

ACC00652 REPLY: parameter

ACC00710 UNIT AFFINITY BROKEN FOR ddname - oldpool/newpool

ACC00720 DD old-dd RECHAINED TO new-dd

ACC00730 DD ddname POOL vtename UCB COUNT totalnum/allocated

ACC00731 VTE vtename - RC=rc / error-type)

ACC00732 VTE vtename IS READ ONLY

ACC00733 VTE vtename IS OFFLINE

ACC00734 VTE vtename IS NOT BEING MONITORED - RC=rc

ACC00739 VTE vtename USED FOR DDNAME ddname

ACC00740 DD ddname UNIT SET TO newunit

ACC00780 DD IGXMSGEX device BEFORE|AFTER MOUNT LOAD VALUE IS msg1 / msg2

ACC01200 VOLUME TABLE TOO LARGE FOR ACC PROCESSING

ACC01310 DATA SET type CHANGED TO NON-SPECIFIC

ACC01320 VSAM DEFINE FAILED FOR volume- MOD=modid RC=(rtc-rsc)

ACC01321 VSAM DEFINE FAILED FOR dsname- MAXSPACE FAILED

ACC01340 VSAM DEFINE FAILED FOR dsname - poolname LACKS SPACE

ACC01380 DYNAMIC ALLOCATION FAILED FOR volume - RC=(r15-ec-ic)

ACC01390 dsname USED IN CONCATENATION - REALLOCATE FAILED

ACC01391 alloctype FAILED FOR ddname - RC=(r15-ec-ic)

ACC01600 DIRBLKADD LSTAR=ds1lstar NOBDB=ldb-bytes TRBAL=trbal

ACC01601 DIRBLKADD EXTENT1 START=cchh END=cchh

ACC01602 DIRBLKADD READ TT=tt DATA=dumpdata

ACC01603 DIRBLKADD DIR=dnum NONDIR=nddum UNUSEDDIR=unum EOF=enum

ACC01604 DIRBLKADD LASTDIR=ttr DIREOF=ttr DATA=ttr

ACC01605 DIRBLKADD DIR BLK AT TTR=ttr KEY=dbkey dumpdata

ACC01606 I/O ERROR, ECB= ecb SENSE=sense CSW= csw

ACC01607 I/O ERROR, SEEK= mbbcchhr

ACC01608 MEM=memname ALIAS=y/n TTR=ttr CCHHR=cchhr

ACC01609 TTRNS=udttrns UDHWDS=udhwds

ACC0160A DIRECTORY BLOCK NO. num PROCESSED

ACC0160B DIRBLKADD BYPASSED, RSN=text

ACC0160C RE-READ DIRBLK TTR=ttr

ACC0160D MEMBER memname IECPCNVT ERROR RC=rc

ACC0160E DIRBLKADD LSTAR=mbbcchhr

ACC0160F IECPRLTV ERROR CONVERTING mbbcchhr RC=rc

ACC0160G INVALID DIRBLK CCHHRKDD=mbbcchhr

ACC01622 DIRBLKADD WRITE DIRBLK=mbbcchhr

ACC01623 DIRBLKADD WRITE DIREOF=mbbcchhr

ACC01626 I/O ERROR, ECB=ecb SENSE=sense CSW=csw

ACC01627 I/O ERROR, SEEK=mbbcchhr

ACC01630 MOVING MEMBER=memname TTRX=mbbcchhr

ACC01631 MEMBER memname IECPCNVT ERROR RC=rc

ACC01632 MEMBER memname IECPRLTV ERROR RC=rc mbbcchhr

ACC01633 DIRBLKADD MOVE CCHHRKDD=cchhrkdd DATA=dumpdata

ACC01634 DIRBLKADD LSTAR UPDATE TTR=ttr MBB=mbbcchhr

ACC01635 MEMBER memname MOVED FROM TTR=ttr TO TTR=ttr

ACC01636 I/O ERROR, ECB=ecb SENSE=sense CSW=csw

ACC01637 I/O ERROR, SEEK=mbbcchhr

ACC01639 DIRBLKADD WRITE CCHHRKDD=cchhrkdd DATA=dumpdata

ACC0163A text

ACC0163B DSCB UPDATE LSTAR=ttr

ACC0163D MEMBER memname NEWTTRX=ttr

ACC0163E MEMBER memname NEWMBBC=mbbcchhr

ACC0163F I/O TRKCALC ERROR RC=rc

ACC0163G DIRBLKADD TRKBAL UPDATE BAL=num

ACC01641 I/O ERROR, ECB=ecb SENSE=sense CSW=csw

ACC01642 I/O ERROR, SEEK=mbbcchhr

ACC01643 DIRBLKADD REW DBLK CCHHRKDD=cchhrkdd DATA=dumpdata

ACC01643 DIRBLKADD REW DBLK CCHHRKDD=cchhrkdd DATA=dumpdata

ACC02300 flag - UCB DEVN device VOLSER volser

ACC02310 ** WARNING ** POOL poolname WOULD NOT ALLOW ACCESS TO VOLUME volume FOR dsname

ACC02311 POOL poolname DOES NOT ALLOW ACCESS TO VOLUME volume FOR dsname

ACC03350 KEEPAWAY VALUE FOR volume IS num

ACC03360 KEEPAWAY req-dsn FROM group- dsn (rulename) - COUNT=num

ACC03361 KEEPAWAY FOUND DSN dsname ON VOLUME volser

ACC03400 ALGORITHM algname VALUE FOR volume IS num

ACC03500 UNIT ucb-volser SELECTED POOL BY poolname ALGORITHM algname FOR DD ddname

ACC03710 CHANGED VOLUME FROM smsvola TO smsvolb FOR DSN=dsname DD= ddname

ACC03750 VOLSER STORGRP FLAGS LIST FREE CAP THRESH

ACC02310 WARNING POOL poolname WOULD NOT ALLOW ACCESS TO VOLUME volume FOR dsname

ACC08111 ...COMPARE field(charvalue) operator field(charvalue)

ACC08112 ...COMPARE field(numvalue) operator field(numvalue)