CADD131E

CADDSPL Messages › › CADD131E

CADD131E

SPLx Date/Time U Exit Failed RC=00000010, Reason=000000xx

SPLx

is the CADDSPL ID

xx is the

reason code

Reason:

The Date/Time User Exit was automatically deactivated due to unexpected results.

Action:

See the CA Dispatch Systems Programmer Guide for explanation of the reason codes. Correct the Date/Time Exit and restart.

CADD134W

<SPLx> Captured Reports reached $$$% of MAXDS

<SPLx> is the CADDSPL ID.

Reason:

This warning message is sent when the number of captured reports has reached a specified warning threshold. Its core purpose is to alert the production team before the MAXDS (Maximum Data sets) is reached so some preventive action can be taken. This threshold can be modified through either the CADDUTIL ROOT statement or the Operator SET command, with the MDWarn parameter. It is expressed as a percentage of MAXDS.

Action:

Delete report entries from CA Dispatch that are no longer needed.

There are several options available to regain report entry (SPLHDR2) space. They include:

Manually delete report entries (SPLHDR2) from CA Dispatch Online Viewing.
Execute the Online View Purge utility to automatically delete Online Viewing reports that have exceeded their retention.
Perform an Online Viewing Unload DSEXULD/DSEXULDL, reinitialize the linear data sets specifying a larger MAXDS parameter value, and perform an Online Viewing Reload DSEXRLD. For specific information regarding the execution of these utilities, see the Systems Programmer Guide.
Execute DSEXOVUL to initialize the OV database, reinitialize the linear data sets specifying a larger MAXDS, and execute DSEXBDE/ DSEXBDEL to restore Online Viewing reports from Archive. For specific information regarding the execution of these utilities, see the Systems Programmer Guide.
Note: This option is only valid if all of the required reports for Online Viewing reload currently exist in the Archive database.

CADD135S <SPLx>

Error during DIV SAVE for <ENFSPLnn> (rc=<xxxx>-reas=<yyyy>)

SPLx is the CADDSPL ID

ENFSPLnn is the data space identification

xxxx is the return code of the IBM macro DIV

yyyy is the reason code of the IBM macro DIV

Reason

The DIV SAVE function terminates abnormally. This is mainly an internal error. The return and reason codes give more specific information.

Action

Contact Technical Support.

CADD140I

SPLx SNT1(address) SNT2(address) SPLT(address)

CADD141I

SPLx SPAI(address) SPOI(address) SPLM(address)

CADD142I

SPLx SPLZ(address) xSPL(address)

SPLx is the CADDSPL ID

address is the hexadecimal address of the indicated modules

Reason:

These messages are a response to the F SPLx,MAP command.

Action:

None. These messages are informational only.

CADD150I

SPLx Diag command - Dump of bbbb - Length nnnn

SPLx is the CADDSPL ID

bbbb is the control block (SNT, SNT2, SPLT, APND)

nnn is the length of the control block

Reason:

This message is part of the response to the DIAG command. It is followed by CADD151I messages.

Action:

None.

CADD151I

SPLx offs hhhhhhhh hhhhhhhh hhhhhhhh hhhhhhhh >cccccccccccccccc<

SPLx is the CADDSPL ID

offs is the line offset

hhhhhhhh is the hexadecimal representation

cccccccccccccccc is the character representation

Reason:

This message follows the CADD150I message.

Action:

None.

CADD152W

SPLx Diag command - SPLT missing

SPLx is the CADDSPL ID

Reason:

The CADDSPLT table is missing. This is an internal error.

Action:

Contact Technical Support.

CADD163I

SPLx Change in ORDER requires a recycle of CADDSPL

SPLx is the CADDSPL ID

Reason:

This informational message reminds you that the change you made to the order of the fields will be active after the next recycle of CADDSPL. When this message appears, the CADD063I message will be displayed twice, once for the current field order and again for the next order.

Action:

None.

CADD173E

<SPLx> Unformatted Append LDS <dsname>

SPLx is the CADDSPL ID

Reason:

During the start of CADDSPL, an unformatted Append LDS was found. The CADDSPL halts the starting process and ends with a return code. This situation usually appears following a user error when an Append LDS has been deleted and reallocated without formatting.

Action:

This is a severe error with a global impact to the whole environment due to the possibility of lost data. Contact Technical Support.

CADD184I

SPLx Token=token Job=jobname DDname=ddname Ord#=number

SPLx is the CADDSPL ID

Token is the token ID associated with the opened report

Job is the job name of the opened report

Ddname is the DDname for the opened report

Ord# is an internal ordinal report number

Reason:

This message is issued in response to a STAT X command or an intercept being stopped. CADD184I, CADD084I and CADD085I messages are written for each opened report.

Action:

None.

CADD226I

<SPLx> Task Class Dest Intercept SAPI Initial

SPLx is the CADDSPL ID

Reason:

This message is an informational response to the F SPLx,STATUS command and gives the columns header for the following CADD026I message(s).

Action:

None.

CADD235I

SPLx nnn Job(s) is(are) actively being intercepted

SPLx is the CADDSPL ID

Reason:

This message indicates the number of jobs currently intercepted during the intercept shutdown.

Action:

None.

CADD240I

<SPLx>Purge subtask is active

SPLx is the CADDSPL ID

Reason:

This message indicates the start of the purge subtask. It is part of the CADDSPLP debugging message set which is sent when the F SPLx,SET MSG=240 command is issued.

Action:

None.

CADD241I

<SPLx>Start of reports scanning

SPLx is the CADDSPL ID

Reason:

This message indicates the actual scanning of the report entries. It is part of the CADDSPLP debugging message set which is sent when the F SPLx,SET MSG=240 command is issued.

Action:

None.

CADD242I

<SPLx>Waiting for nnnn minutes

SPLx is the CADDSPL Identification

Reason:

This message indicates the purge subtask waits for some time before scanning again. It is part of the CADDSPLP debugging message set which is sent when the F SPLx,SET MSG=240 command is issued.

Action:

None.

CADD243I

<SPLx>Checking status

SPLx is the CADDSPL ID

Reason:

This message indicates the purge subtask is checking whether to scan the report entries, to stop scanning them, or to wait. It is part of the CADDSPLP debugging message set which is sent when the F SPLx,SET MSG=240 command is issued.

Action:

None.

CADD247I

<SPLx>Error in CADDSCAN (Code=xxxx)

SPLx is the CADDSPL ID

Reason:

This message indicates an error during the scanning of the report entries. The code specifies the kind of error.

Action:

Take a system dump, recycle CADDSPL and contact Technical Support.

CADD248I

<SPLx>End of reports scanning

SPLx is the CADDSPL ID

Reason:

This message indicates the successful completion of the report entries scanning. It is part of the CADDSPLP debugging message set which is sent when the F SPLx,SET MSG=240 command is issued.

Action:

None.

CADD249I

<SPLx>End of Purge subtask

SPLx is the CADDSPL ID

Reason:

This message indicates the completion of the purge subtask. It is part of the CADDSPLP debugging message set which is sent when the F SPLx,SET MSG=240 command is issued.

Action:

None.

CADD250I

JOBnnnnn <jobname> <DDname> Purged RC=nnnnn

nnnnn is the JES job number which created the report

Jobname is the job name that created the report

Ddname is the ddname DD statement used to create the report

Reason:

The indicated data set was deleted or purged from the linear data set (LDS) with the indicated return code. This message documents the deletions performed by CADDSPL and appears in the CADDSPL message log.

Action:

None.

CADD251I

File xxxxxxxx- Status yy - 1st Block zzzzzzzz

xxxxxxxx is the token of the control block defining the report

yy is the status information flag

zzzzzzzz is the token of the first data block for this report

Reason:

Informational. For technical support staff use in debugging possible chaining or corruption errors. This message appears for every data set that is deleted. This message may accompany the CADD250I message in the CADDSPL job log when deleting a data set.

Action:

None.

CADD252E

File xxxxxxxx - Invalid yyyyyyyy Block zzzzzzzz (Status yy)

xxxxxxxx is the token of the control block defining the report.

yyyyyyyy is First, Index, Indx2, Data, WritD, WritX, Hdr4, Hdr4W, Hdr4S.

yy is the status information flags

zzzzzzzz is the token of the first data block for this report

Reason:

Informational. To be used by technical support staff when they are debugging possible chaining errors. This message appears when RC=10 occurs for the CADD250I message. This message may accompany the CADD250I message in the ENFSPL job log when deleting a data set.

Action:

If excessive numbers of CADD250I messages occur with RC=10, obtain the complete log and contact Technical Support.

CADD253W

File xxxxxxxx still opened (yy) - unable to delete it

xxxxxxxx is the token of the control block defining the report.

yy is the status information flags

Reason:

This message displays for every data set open during a delete process.

Action:

None.

CADD254W

File xxxxxxxx - HDR4 yyyyyyyy corrupted at offset oooo ff/ee

xxxxxxxx is the token of the control block defining the report.

yyyyyyyy is the token of the bitmap block.

oooo is the offset of the byte in error in the bit map.

ff is the hexadecimal value found for the byte of the bitmap.

ee is the hexadecimal value expected for the byte of the bitmap.

Reason:

One or more bits weree reset in a bit map block. These bits specify free data block selection as part of the data block protection.

Action:

If this message appears frequently, contact Technical Support.

CADD255E

File nnnn - Invalid xxxxxxxx Block zzzzzzzz (Status yy)

nnnn is the report number.

xxxxxxxx is one of the following values: First, Index, Indx2, Data, WritD, WritX, Hdr4, Hdr4W, Hdr4S.

zzzzzzzz is the token of the invalid block for this report

yy is the status information flag

Reason:

The delete process received an invalid token for the control block defining the report and is unable to delete the report.

Action:

Contact Technical Support.

CADD258W

JOBnnnnn <jobname> <DDname> Error during purge (rc=xxxxxxxx)

nnnnn is the JES job number that created the report

Jobname is the jobname that created the report

DDname is the ddname DD card used to create the report

Reason:

An error occurred during the deletion of the indicated data set rom the linear data set (LDS). The return code gives additional information. This message documents the deletions performed by CADDSPL and appears in the CADDSPL message log.

Action:

Contact Technical Support.

CADD259I

SPLx CLOSE waiting for Purge task cessation

SPLx is the CADDSPL ID

Reason:

The Close process is waiting for the completion of the Purge task.

Action:

None.

CADD260E

File xxxxxxxx - Error retrieving Name/Token Jobid ddname (rc=xx)

xxxxxxxx is the token of the control block defining the report.

jobid is the JES job identification for the job creating the report.

ddname is the ddname used to create the report.

xx is the return code of the name/token function called.

Reason:

Name/token checking suppresses reports left in undefined status. During this check, the delete process received an unknown return code from the Name/token service. CADDSPL is unable to delete this report.

Action:

Contact Technical Support.

CADD261W

File xxxxxxxx - Broken HDR3 chain Current Given/Found

xxxxxxxx is the token of the control block defining the report.

Current is the token of the current data block.

Given is the token of the actual previous data block.

Found is the token found in the current block for the previous block.

Reason:

An invalid backward chain was found between the data blocks for this report. The delete process tries to delete all of the found blocks.

Action:

If this message appears frequently, contact Technical Support.

CADD262E

CADDSPLx JESLIT value is: xxxxxx

CADDSPLx is the CADDSPL ID

xxxxxx is the literal identification of the current JES primary subsystem

Reason:

This message follows the CADD062E message and specifies the JES level found.

Action:

Contact Technical Support.

CADD263E

HDR3 Chaining error during Specific process between Previous and Current

Specific is the current process

Previous is the token of the from data block

Current is the token of the current data block

Reason:

An invalid forward chain was found between data blocks when accessing a report. The Specific process can be:

Frst Index—The control block for this report (Previous) refers to that block as first index (Current) while this one is referring back to another report.
Idx to Idx—When walking down the index chain, an index block has been found that is either owned by another report or that has a different backward chain.
Idx to Dta—When accessing a data block from an index block, a data block has been found that is either owned by another report or refers to another index block.
Dta to Dta—When walking down the data chain, a data block has been found that is either owned by an other report or has a different backward chain.

Action:

All of these reasons are related to a broken chain. If these messages appear frequently, contact Technical Support.

CADD300E

Procedure name must be CADZSAPx - procname invalid

x is the SAPI STC name suffix required

procname is the current STC name

Reason:

The name of the SAPI procedure requires a special format. You specified an invalid procname. The SAPI function stops immediately.

Action:

Change the procname as specified by the message.

CADD301E

SAPx is not APF authorized

x is the SAPI suffix

Reason:

The SAPI address space must be APF authorized. This can be due to an unauthorized library in the STEPLIB concatenation. The SAPI function stops immediately.

Action:

Define all of the libraries in the STEPLIB concatenation as APF-authorized.

CADD302E

SAPx unsupported release/level of mvs

x is the SAPI suffix

Reason:

The SAPI address space is not supported on a system version older than z/OS V1R3. The SAPI function stops immediately.

Action:

Contact Technical Support.

CADD303I

SAPx will not start collect sysout until CADDSPLi is initialized

x is the SAPI suffix

Reason:

Informational. The SAPI address space is waiting for the CADDSPL main address space. In normal production, the SAPI address space is started by the CADDSPL address space and this message should not be sent. This message can appear when the SAPI address space is started manually.

Action:

None.

CADD308I

SAPx initialization in progress

x is the SAPI suffix

Reason:

The main task of the SAPI function is in the initialization phase.

Action:

None.

CADD309I

SAPx initialization complete

x is the SAPI suffix.

Reason:

The main task of the SAPI function finished its initialization.

Action:

None.

CADD310W

SAPx taskid Attach error (rc=nnn)

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

nnn is the decimal return code.

Reason:

The main task failed to start this function. This is an internal error.

Action:

Contact Technical Support.

CADD311I

SAPx taskid already started/stopped

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

This message is sent in response to a task start or stop command. The task is already in the requested status.

Action:

None.

CADD312I

SAPx taskid not started - reason

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

reason can be "Not a SAPI task" or "Shutdown in progress"

Reason:

The task start command is rejected due to the reason indicated in the message text.

Action:

None.

CADD313I

SAPx taskid ended (rc=000)

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The task is successfully finished.

Action:

None.

CADD314W

SAPx taskid ended (rc=nnn)

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

nnn is the decimal return code

Reason:

The task is unsuccessfully finished. The return code specified in the message text indicates the reason.

Action:

None.

CADD315E

SAPx taskid abended Sxxxx

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

xxxx is the hexadecimal abend code

Reason:

The task is unsuccessfully finished. The return code specified the reason. This is an internal error.

Action:

Contact Technical Support.

CADD316I

SAPx taskid cancelled

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The task was cancelled by the SAPI main task due to a task cancel command.

Action:

None.

CADD317I

SAPx no current active SAPI task

x is the SAPI suffix

Reason:

All the SAPI tasks are stopped.

Action:

None.

CADD318I

SAPx shutdown in progress

x is the SAPI suffix

Reason:

The SAPI main task is shutting down.

Action:

None.

CADD319I

SAPx shutdown complete

x is the SAPI suffix

Reason:

The SAPI main task completed its shutdown phase.

Action:

None.

CADD320I

SAPx undefined task id nn

x is the SAPI suffix

nn is the decimal ID number

Reason:

An internal start command was issued for an invalid task ID. This is an internal error.

Action:

Contact Technical Support.

CADD321I

SAPx taskid initialization in progress

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI task started its initialization phase.

Action:

None.

CADD322S

SAPx taskid getmain error for area (rc=nnn)

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

area is SSOB, SSS2 or DCB

nnn is the decimal return code

Reason:

The getmain for the required control block failed.

Action:

Check the return code in the message text for the associated reason and contact Technical Support.

CADD323E

SAPx taskid initialization failed

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI task initialization failed. The task is stopped. The previous messages give the reasons of the failure.

Action:

Check the previous messages for the reasons of this failure and correct them.

CADD324I

SAPx taskid initialization complete

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI task finished its initialization phase.

Action:

None.

CADD325E

SAPx taskid SAPI call error (rc=nnn)

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

nnn is the decimal return code

Reason:

The SAPI request for a new SYSOUT failed. This is an internal error.

Action:

Contact Technical Support.

CADD326E

SAPx taskid SAPI interface error (rc=nn,rtrn=xxx,reas=yyy)

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

nn is the decimal request return code

xxx is the decimal result return code

yyy is the decimal result reason code

Reason:

A new SYSOUT cannot be serviced by the SAPI subsystem request. This is a SAPI error. Details regarding the return and reason codes can be found in the most current MVS release of the IBM manual "Using the Subsystem Interface".

Action:

See the IBM documentation for return codes for the IEFSSREQ macro, correct the error and rerun the job.

CADD328I

SAPx taskid shutdown in progress

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI task started its final phase.

Action:

None.

CADD329I

SAPx taskid shutdown complete

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI task finished its final phase.

Action:

None.

CADD330I

SAPx taskid processing ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI task is processing a given JES data set. This is an informational message completed by CADD360I, CADD361I, and CADD362I to give the JES data set characteristics.

Action:

None.

CADD331E

SAPx taskid allocation error (rc=nnn,err=xxxx,info=yyyy)

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

nnn is the decimal return code

xxxx is the hexadecimal error code

yyyy is the hexadecimal information code

Reason:

The SAPI task received an error during the JES data set allocation process. The return code, error code and information code indicate the cause of the error message. The JES data set file is not processed. See Dynamic allocation return code for more information.

Action:

Take appropriate action depending on the return code. Contact Technical Support if the error persists.

CADD332E

SAPx taskid deallocation error (rc=nnn,err=xxxx,info=yyyy)

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

nnn is the decimal return code

xxxx is the hexadecimal error code

yyyy is the hexadecimal information code

Reason:

The SAPI task received an error during the JES data set deallocation process. The return code, error code and information code indicate the cause of the error message. The JES data set file is not processed. See Dynamic allocation return code for more information.

Action:

Take appropriate action depending on the return code. Contact Technical Support if the error persists.

CADD333W

SAPx taskid EOD detected on incorrectly closed sysout

X is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

While reading a JES data set, the SAPI task found a discrepancy between the number of records processed when EOD was reached and the number in the internal control blocks. Messages CADD330I, CADD360I, CADD361I and CADD362I provide useful information to identify the JES data set.

Note: This message is written in the JOBLOG of the SAPI address space and as the last record of the user report.

Action:

CADD333W indicates that an unusual condition occurred while the application program was writing the SYSOUT; the most common reason is that MVS was not shutdown properly; you should make sure that the report data is complete.

CADD339I

SAPx taskid end of process for ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

This is an informational message. The SAPI task finished processing a JES data set. Messages CADD360I, CADD361I and CADD362I, associated with previous message CADD330I, give the JES data set characteristics.

Action:

None.

CADD340E

SAPx taskid Read JFCB Error (rc=nnnn) ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

nnnn is the decimal return code

Reason:

The SAPI task received an error during the read JFCB process for a given JES data set. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the JES data set. This is an internal error.

Action:

Contact Technical Support.

CADD341E

SAPx taskid Open Error (rc=nnnn) for ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

nnnn is the decimal return code

Reason:

The SAPI task received an error during the open process for a given JES data set. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the JES data set. This is an internal error.

Action:

Contact Technical Support.

CADD342S

SAPx taskid I/O Error diagnosis-information

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

diagnosis-information is the information given by the access method

Reason:

The SAPI task encountered an error while reading a JES data set; the diagnosis-information field displays the error message as it was returned by the access method. Messages CADD330I, CADD360I, CADD361I and CADD362I provide useful information to identify the JES data set.

Action:

If this message persists, contact Technical Support.

CADD343E

SAPx taskid Unable to obtain SPLHDR2 slot for ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI task received an error when accessing internal data space control block for a given JES data set. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the JES data set. This is an internal error.

Action:

Contact Technical Support

CADD344S

SAPx taskid Unable to access type Block for GetBL-S

x is the SAPI suffix

type is Data or Index

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI task received an error when accessing or updating an internal data space control block for a given JES data set. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the JES data set.

A dump is taken and the task is interrupted. This is an internal error.

Action:

Contact Technical Support.

CADD345I

SAPx taskid LDS full - Process in Stand by for...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI task detected an LDS full condition when writing a block in the data space for a given JES data set. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the JES data set. The process is placed on standby.

Action:

The LDS full condition can be reset either by cleaning the LDS or adding a new append LDS.

Daily process, manual deletes and/or archiving can be used to clean the LDS. These operations can be run with the SAPI task on standby. When the LDS full condition is reset, the SAPI task will automatically resume the process.

In the event that a new append must be added, the CADDSPL must be stopped. Either the Stop,IMMED command for the SAPI task followed by a Close command or a direct Close,IMMED command can be used. When CADDSPL is down, run the CADDUTIL utility to add the new append LDS and restart the CADDSPL. The SAPI task will resume the interrupted process.

CADD346S

SAPx taskid CADZSPLi not available - Process interrupted ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI task that detected the CADZSPLi address space stopped or abended. The task is interrupted.

Action:

Restart CADDSPLi and restart the SAPI task.

CADD347S

SAPx taskid Get Blocks Error (rc=nnnn) for ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

nnnn is the decimal return code

Reason:

The SAPI task received an error when accessing the data space control block for a given JES data set. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the JES data set. This is an internal error.

Action:

Contact Technical Support.

CADD348S

SAPx taskid Getmain Error for Compressed Buffer (rc=nnn)

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

nnn is the decimal return code

Reason:

The SAPI task received an error during a getmain process for a given JES data set. The return code indicates the source of the error. The processing of the current file is interrupted. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the JES data set.

Action:

Review messages CADD360I, CADD361I and CADD362I to determine where the error occurred and contact Technical Support.

CADD349S

SAPx taskid Freemain Error for Compressed Buffer (rc=nnn)

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

nnn is the decimal return code

Reason:

The SAPI task received an error during the freemain process for a given JES data set. The return code indicates the source of the error. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the JES data set. This is an internal error.

Action:

Contact Technical Support.

CADD350E

SAPx taskid I/O Error on LDS for ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI task received an error when writing the data space on to the LDS for a given JES data set. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the JES data set. This is an internal error.

Action:

Contact Technical Support.

CADD351W

SAPx taskid File pending recovery for another JES Data Set ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

Informational. The SAPI MSG task received a JES data set to process and detected the last processed JES data set for this job was interrupted. The process for the current JES data set is deferred until the interrupted JES data set is successfully recovered. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the current JES data set.

Action:

None.

CADD352S

SAPx taskid File should not be in recovery for ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

Informational. The SAPI MSG task received a JES data set for the recovery process and detected the last processed JES data set marked for recovery does not correspond to this one. The process for the current JES data set is deferred until the interrupted JES data set is successfully recovered. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the current JES data set.

Action:

None.

CADD353W

SAPx taskid Original token already deallocated ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

Informational. The SAPI task received a JES data set for the recovery process and detected the current file in the data space was deallocated. The recovery for the current JES data set is done in a new file in the data space. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the current JES data set.

Action:

If this error persists, contact Technical Support.

CADD354W

SAPx taskid Token found addresses another file than ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

Informational. The SAPI task received a JES data set for the recovery process and detected the related token addresses a file in the data space that defines another JES data set. The recovery for the current JES data set is done in a new file in the data space. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the current JES data set.

Action:

If this error persists, contact Technical Support

CADD355S

SAPx taskid Loss of HDR2 token when getting blocs for ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI task received a JES data set for the recovery process and lost the related token, which addresses the file in the data space. The recovery for the current JES data set is done in a new file in the data space. Messages CADD360I, CADD361I, and CADD362I, which follow the current message or the previous CADD330I message, give more information about the current JES data set. This is an internal error.

Action:

Contact Technical Support.

CADD356S

SAPx taskid RBA of Separator (xxxxxxxx) out of file yyyyyyyy

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

xxxxxxxx is the hexadecimal RBA value

yyyyyyyy is the hexadecimal token which addresses the file in the data space

Reason:

The SAPI MSG task received a JES data set for the recovery process and detected the RBA (relative byte address) of the JES data set separator higher than the high RBA of the file in the data space. The recovery for the current JES data set is done in a new file in the data space. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the current JES data set. This is an internal error.

Action:

Contact Technical Support.

CADD357S

SAPx taskid Bad file structure type nnn for token yyyyyyyy

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

nnn is a number used for debugging purposes to specify the internal error. Valid is between 001 and 007.

yyyyyyyy is the hexadecimal token which addresses the file in the data space

Reason:

The SAPI MSG task received a JES data set for the recovery process and detected an internal error in the blocks of the data space's file. The recovery for the current JES data set is done in a new file in the data space. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the current JES data set.

Action:

Contact Technical Support.

CADD358S

SAPx taskid Restart RBA does not address separator

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The SAPI MSG task received a JES data set for the recovery process and detected the recovery RBA does not address a JES data set separator in the data space's file. The recovery for the current JES data set is done in a new file in the data space. Messages CADD360I, CADD361I and CADD362I, which follow the current message or the previous CADD330I message, give more information about the current JES data set. This is an internal error.

Action:

Contact Technical Support.

CADD359S

SAPx taskid Restart ddn=ddname,step=stepname when processing ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

ddname is the ddname of the current JES data set to recover

stepname is the stepname of the current JES data set to recover

Reason:

This is an internal error. The SAPI MSG task received a JES data set for the recovery process and detected the recovery RBA addresses a JES data set separator in the data space's file, which is for another JES data set of the current job. The recovery for the current JES data set is deferred until later. Messages CADD360I, CADD361I, and CADD362I, which follow the current message or the previous CADD330I message, give more information about the current JES data set.

Action:

Contact Technical Support.

CADD360I

SAPx taskid job=jobname(jobid),step=stepname

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

jobname is the job name of the current JES data set

jobid is the Job ID given by JES

stepname is the stepname of the current JES data set

Reason:

This is an informational message associated to the CADD330I message or any error message associated with this current JES data set.

Action:

None.

CADD361I

SAPx taskid ddn=ddname(Dsid),proc=procstepname

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

ddname is the ddname of the current JES data set

dsid is the data set ID as given by JES

stepname is stepname of the current JES data set

Reason:

This is an informational message associated with the CADD330I message or any error message associated with this current JES data set.

Action:

None.

CADD362I

SAPx taskid dsn=dsname

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

dsname is internal dsname of the current JES data set

Reason:

This is an informational message associated to the CADD330I message or any error message with this current JES data set.

Action:

None.

CADD365I

SAPx taskid LDS full relieved - Process resuming

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

The LDS full condition is gone and the SAPI task is resuming its process.

Action:

None.

CADD366W

SAPx taskid Report in error relating to token hhhhhhhh ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

hhhhhhhh is the hexadecimal value of the token for the report

Reason:

When a SAPI task starts, it looks for reports routed to destination $$Extaskid. Reports are sent to this destination when CADDSPL encounters an unrecoverable error while processing a JES data set.

The token identifies the report which is also displayed on the VOPMI205 screen (RIDF) in RCVY mode. Message CADD330I which precedes this message, or messages CADD360I, CADD361I and CADD362I which follow this message, provide more information about the JES data set.

Action:

CADD366W messages indicate reports that cannot be processed by CADDSPL and CA Dispatch. Review these reports to determine appropriate actions for report recreation or recovery. When finished, delete the related JES data sets and RIDF entries to remove any incomplete report data stored in the LDS.

CADD367W

SAPx taskid Stop,Immed. required to interrupt report ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

A Stop, Quiesce or Close command has been requested without the Immed option when a SAPI task is in standby for a given JES data set. Messages CADD360I, CADD361I and CADD362I, which follow the current message, or the previous CADD330I message, give more information about the JES data set. When a SAPI task is in stand by, the Immed option is required to stop it.

Action:

If you wish to stop this SAPI task, resend the command with the Immed option.

CADD368I

SAPx taskid Process interrupted for report ...

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

Reason:

A Stop, Quiesce or Close command has been requested with the Immed option; this requests that the SAPI task be stopped while processing a JES data set. The required information will be saved to be able to resume the processing of this JES data set when the SAPI task is restarted.

Action:

None.

CADD369W

SAPx taskid set/cancel of timer error (rc=hhhh)

x is the SAPI suffix

taskid is the SAPI task ID (RPI1, RPI2, RPI3, MSG or ARCH)

hhhh is the return code of the timer function.

Reason:

A Timer function got an unexpected error during the standby of a SAPI task.

Action:

This is an internal error. Contact Technical Support.