SPLx is the CADDSPL ID
Reason:
ICSF has returned an error code. The return and reason codes are described in Appendix A of the IBM publication ICSF Application Programmers Guide (SA22-7522).
xxxxxxxx is the name of the ICSF service that failed.
Action:
Contact CA Technical Support.
xxxxxxxx is the name of the ICSF service that failed.
ICSF has returned an error code. The return and reason codes are described in Appendix A of the IBM publication ICSF Application Programmers Guide (SA22-7522).
Action:
Ensure that ICSF is running on the machine where the error occurred.
xxxxxxxx is the name of the ICSF service that failed, CA Dispatch failed to load the above ICSF service.
Action:
Contact CA Technical Support.
Reason:
xxxxxxxx is the name of the missing key
CA Dispatch has requested the above key from the ICSF key store (CKDS) and it was not found. This type of error occurs when the CKDS has been restored to an old version or multiple CKDS data sets are used for the same CA Dispatch database.
Action:
Contact CA Technical Support to determine if the key can be recovered and the extent of the data loss.
An internal error has occurred within CA Dispatch.
Action:
Contact CA Technical Support.
Reason:
The CADDUTIL utility is starting.
Action:
None.
Reason:
The CADDUTIL is on the parsing phase.
Action:
None.
Reason:
The CADDUTIL is displaying the command line to analyze.
Action:
None.
Reason:
The CADDUTIL utility completed the parsing phase.
Action:
None.
Reason:
The CADDUTIL utility is unable to process this command.
Action:
Verify that this is a valid command for CADDUTIL.
Reason:
The CADDUTIL utility is formatting the root or append LDS referenced by the ddname.
Action:
None.
Reason:
The CADDUTIL utility is formatting the root LDS referenced by the ddname.
Action:
None.
Reason:
This message indicates the exact number of 4 KB blocks initialized during the last format command.
Action:
None.
Reason:
The SplHdr0 control block was successfully rewritten on the root LDS referenced by the ddname.
Action:
None.
Reason:
The CADDUTIL utility ended. The hexadecimal return code (hhhh) indicates the highest error code encountered during its run.
Action:
None.
Reason:
The CADDUTIL utility cannot open the root or append LDS referenced by the ddname. The hexadecimal return code hhhh indicates the error code.
Action:
Verify that the DD statement referencing this file corresponds to a valid LDS.
Reason:
The CADDUTIL utility cannot complete the requested function for the LDS referenced by the ddname. The hexadecimal return code hhhh indicates the error code of the function.
Action:
Verify that the DD statement referencing this file corresponds to a valid LDS.
Reason:
The CADDUTIL utility received an error code for a storage obtain or a storage release for a given control block. The hexadecimal return code hhhh indicates the error code of the function.
Action:
If the error appears for a storage obtain, verify the region specified for the CADDUTIL is high enough. If needed, contact Technical Support.
Reason:
The CADDUTIL utility received an error code for the given operation when processing the LDS named ddname. The hexadecimal return code hhhh indicates the error code of the function.
Action:
Verify the DD statement named ddname is related to a LDS file. If needed, contact Technical Support.
Reason:
The CADDUTIL utility received a feedback code for the given operation when processing the LDS named ddname. The hexadecimal return code hhhhhhhh specifies the feedback code of the function.
Action:
None.
Reason:
The CADDUTIL utility received an error, logical or physical, for the given operation when processing the LDS named ddname. The hexadecimal code hhhhhhhh specifies the feedback code of the function.
Action:
Verify that the DD statement named ddname is related to a LDS file. If needed, contact Technical Support.
Reason:
The CADDUTIL utility received a RPL error during a Get or Put operation.
Action:
Verify the DD statement named ddname is related to a LDS file. If needed, contact Technical Support.
Reason:
The CADDUTIL utility received an error during a Get or Put operation, indicating the VSAM component of the SMS is not active.
Action:
Verify the SMS management on your site is correct. If needed, contact Technical Support.
Reason:
The space specified in the Root LDS Define command is not large enough to contain the needed 4 KB blocks.
Action:
Use the suggested formulas to calculate the required space on the root LDS. See the Getting Started for information about computing the optimum root LDS size.
Reason:
This is the first of nine messages giving characteristics about the LDS referenced by the DD statement ddname.
Action:
None.
Reason:
This is the second of nine messages giving characteristics about the LDS referenced by the DD statement ddname. This message specifies the dsname of the LDS.
Action:
None.
Reason:
This is the third of nine messages giving characteristics about the LDS referenced by the DD statement ddname. This message specifies the relative block address of the highest allocated byte in the LDS.
Action:
None.
Reason:
This is the fourth of nine messages giving characteristics about the LDS referenced by the DD statement ddname. This message specifies the relative block address of the highest used byte in the LDS.
Action:
None.
Reason:
This the fifth of nine messages giving characteristics about the LDS referenced by the DD statement ddname. This message specifies the number of extents used by the LDS file.
Action:
None.
Reason:
This is the sixth of nine messages giving characteristics about the LDS referenced by the DD statement ddname. This message specifies the number of EXCPs for the LDS file.
Action:
None.
Reason:
This is the seventh of nine messages giving characteristics about the LDS referenced by the DD statement ddname. This message specifies the timestamp of the LDS.
Action:
None.
Reason:
This is the eighth of nine messages giving characteristics about the LDS referenced by the DD statement ddname. This message specifies the DFP signature for the LDS.
Action:
None.
Reason:
This is the ninth of nine messages giving characteristics about the LDS referenced by the DD statement ddname. This message specifies the wasted space in the LDS. The value is represented in hexadecimal format.
Action:
None.
Reason:
In a CADDUTIL step, no CADDSPLx address space was found initialized in the CADDSNT table.
Action:
Check your environment. This is a normal situation when no CADDSPL environment has been started after CA Dispatch initialization by CAS9.
Reason:
This message contains the first line of a dump for a 4 KB block in an LDS. hhhhhhhh indicates the Relative Block Address of the block.
Action:
None.
CADD631I
Reason:
The message displays 32 bytes of a control block or a 4 KB page.
oooo is the relative offset of the first dumped byte in hexadecimal format.
hhhhhhhh is the hexadecimal value of the bytes.
cc..cc is the displayable representation of the bytes.
Action:
None.
Reason:
Multiple bytes contain binary zeroes. xxxx is the hexadecimal offset of the first byte, yyyy is the hexadecimal offset of the last byte. This message is received when more than 63 consecutive bytes are binary zeros.
Action:
None.
Reason:
One or multiple 4 KB blocks to be dumped contain binary zero values.
Action:
None.
Reason:
Some 4 KB blocks that were requested to be dumped are not contained in the LDS.
Action:
None.
Reason:
A dump was requested for a ddname,which is not a VSAMLDS-formatted file.
Action:
Check your DD statement.
Reason:
Module CADDSNT can not be located in the LPA.
Action:
Be sure that the CAS9 proc was run with the CA Dispatch DSINIT initialization module. If the problem persists, contact Technical Support.
Reason:
The SPLSNT2 entry for CADDSPLx cannot be found in the CADDSNT table.
Action:
This is a normal situation if the CADDSPLx environment has not been started or if the entry was reused for another environment. If the problem persists, contact Technical Support.
Reason:
During the format process, CADDUTIL detected the ddname DD statement does not refer to a valid new LDS file.
Action:
Check your DD statement and verify it addresses a newly initialized LDS file.
Reason:
During the Open process, CADDUTIL detected the ddname DD statement does not refer to a valid LDS file.
Action:
Check your DD statement.
Reason:
The previous ROOT command is missing (Missing VSArea) or it addresses an invalid file (not a Root LDS).
Action:
Check the previous ROOT command.
Reason:
An error was discovered in the LDS control block, SplHdr0.
Action:
Verify your ROOT LDS successfully initialized and you are using a DD statement when addressing it.
Reason:
The CADDUTIL switched on a new extent to format or to initialize a block.
Action:
None.
Reason:
The process to remove, freeze, or reset an Append LDS was started.
Action:
None.
Reason:
A request to remove an Append LDS has been issued. This LDS still contains report data. This condition prevents the removal of the Append LDS.
ddname is the DD name the LDS is allocated to
Token is the token of the HDR2 for this report
Jobname is the JOB name that produced the report
JobId is the JES id of the JOB that produced the report
stepname is the name of the step in the JOB that produced the report
ddreport is the DD name of the sysout from which the report was produced
nnnn is the number of blocks of data in use for this report in the LDS allocated to ddname
One CADD644W message is issued for each report owning data in this Append LDS.
Action:
Verify that this report is still active and take the appropriate action to archive or delete it.
Reason:
This message indicates the successful execution of the Delete, Freeze or Reset function.
Action:
None.
Reason:
The removal of an Append LDS failed. The preceding CADD644W messages indicate the names of the reports with pages allocated to this Append LDS.
Action:
See CADD644W message for appropriate actions.
Reason:
A request to specify the management mode of the bitmap was rejected because this mode is already active.
Action:
None.
Reason:
A request to increase a specific Append LDS was rejected because this LDS is already at its highest limit.
Action:
None.
Reason:
This informational message indicates the update of the LDS entry number nn in the ROOT LDS for the Append LDS ddname.
Action:
None.
Reason:
This message indicates the update of the task information (RPI1, RPI2, RPI3, MSG or ARCH) in the ROOT LDS.
Action:
None.
Reason:
The new characteristics for the task referenced in the previous CADD650I message are stored in the ROOT LDS ddname.
Action:
None.
Reason:
This message indicates the removal of the task information (RPI1, RPI2, RPI3, MSG or ARCH) in the ROOT LDS.
Action:
None.
Reason:
The information for the task referenced in the previous CADD652I message is removed from the ROOT LDS ddname.
Action:
None.
SPLx is the CADDSPL ID
taskid is the intercept or SAPI task (RPI1, RPI2, RPI3, MSG or ARCH)
class and destination are the characteristics of the intercepting selection
taskid2 is the intercept or SAPI task (RPI1, RPI2, RPI3, MSG or ARCH)
Reason:
The Class and Destination selection criteria for the task taskid in the CADDSPL SPLx environment is already used by the task taskid2. This checking is made internally in the CADDSPL environment during the ADD command or the ADD statement of the CADDUTIL batch utility. Only one task can use a specific Class/Destination selection criteria.
Action:
Verify that the class/destination selection criteria specified for a given task is not already in use by another task.
Reason:
The freeze or reset function of an Append LDS failed because it was already in the requested state.
Action:
None.
Reason:
This is the first message after a MAP command. It displays the addresses of the global CADDSNT, CADDSPAU and CADDSPOI modules.
Action:
None.
Reason:
This is the second message after a MAP command. It displays the addresses of the global CADDMSG, CADDMSGT modules.
Action:
None.
Reason:
This is the first message after a MAP command for the specific SPLx environment. It displays the addresses of the SPLSNT2 entry and the specific CADDSPLZ and CADxSPL modules.
Action:
None.
Reason:
This is the second message after a MAP command for the specific SPLx environment. It displays the addresses of the SPLTABL, ITASK and LDS table control blocks.
Action:
None.
Reason:
The ddname referencing the ROOT LDS was used in a command requesting an Append LDS. The command is rejected.
Action:
None.
Reason:
A request to add a new Append LDS was rejected because this one is already in the Append list.
Action:
None.
Reason:
A request to remove an Append LDS was rejected because this one is already out of the Append list.
Action:
None.
Reason:
A request to add a new Append LDS was rejected because there is no more space in the Append list.
Action:
None.
Reason:
While formatting an LDS, the utility has detected that it is larger than 2 gigabytes. CADDSPL imposes a 2 gigabyte limit per LDS.
Action:
Rerun the DDEXLDSI job using a smaller size in the IDCAMS allocation. If the IDCAMS allocation is under 2 gigabytes, check to see if your site uses a software package or storage class that is allowing the original allocation to be extended.
SPLx is the CADDSPL ID
xxxxxx is either VSArea or SPLHDRD
Reason:
During the initialization or the update of a ROOT LDS by CADDUTIL, a control block (xxxxxx) is no longer accessible. This problem prevents sending the messages CADD670I to CADD679I.
This message indicates an internal problem during the initialization or the update process itself, although this process itself has been finished.
Action:
Contact your Technical Support.
SPLx is the CADDSPL ID
ddname is the ROOT LDS ddname
Reason:
This message is part of the initialization update of the ROOT LDS.
This is the header message for a group of messages that give the ROOT LDS parameters.
Action:
None.
SPLx is the CADDSPL ID
Reason:
This message is part of the initialization update of the ROOT LDS.
Total Blocks is the number of 4 KB blocks useable in the ROOT LDS.
1st HDR4 gives the token of the first 4 KB SPLHDR4 Block. These blocks contain the full bit map to address all of the future Append LDS.
1st HDR2 gives the token of the first 4 KB SPLHDR2 Block. These blocks contain the characteristics of the reports that are saved in the Append LDS. Each 4 KB SPLHDR2 block contains the characteristics for 16 reports.
Action:
None.
SPLx is the CADDSPL ID
Reason:
This message is part of the initialization update of the ROOT LDS.
Interval is the maximum wait time between two consecutive DIV Save operations and expressed in hundredths of a second.
Max Update is the maximum number of page updates between two consecutive DIV Save operations.
Checking is set to Yes or No. The use of checking causes more CPU consumption. CA recommends that you set Checking to No.
The DIV Save operation is the process that copies the updated content of a data space to its related Linear Data Set. As soon as one of the limits is reached, the operation is processed.
Action:
None.
SPLx is the CADDSPL ID
Reason:
This message is part of the initialization update of the ROOT LDS.
Pre-fetch count is the number of consecutive pages loaded in the data space when a page-fault occurs.
Prnt Limit determines the number of days a given report can stay in the LDS before it is automatically purged, if not processed.
Purge determines the manner in which purges are managed. The first value can be either Asynch or Synch. Asynch is defined as purges performed by CADDSPL task control. Synch is defined as purges performed by the requestor's task control. The second parameter can be Quick or Clean. Quick is the default and Clean physically erases all data from the LDS.
Action:
None.
SPLx is the CADDSPL ID
Reason:
This message is part of the initialization update of the ROOT LDS.
Lock Number is the number of attempts made before going into a wait state.
Wait time is the amount of time in a wait state before a restart is attempted and expressed in hundredths of a second.
Util Limits defines the warning thresholds for a full data space condition and are expressed in a percentage of the whole data spaces group.
Action:
None.
SPLx is the CADDSPL ID
Reason:
This message is part of the initialization update of the ROOT LDS.
The values are used to determine the total number of HDR4 blocks (bitmap 4 KB blocks) needed to estimate the optimum size of this CADDSPL environment.
Max Nbr of Appends gives the maximum number of appends that a LDS can associate with the Root LDS.
Nbr HDR4/Append gives the maximum number of HDR4 blocks we can associate with a given Append LDS. One HDR4 block is able to address up to 30,848 4 KB Blocks of Appended LDS.
Action:
None.
SPLx is the CADDSPL ID
Reason:
This message is issued during the ROOT LDS initialization process.
Bit Map is either SEQUENTIAL or INTERLEAVED.
The Updated Bit Map is set to On or Off. The Updated Bit Map is a 4 KB bit map per data space backed by the LDS. Its purpose is to increase the performance of saving virtual storage pages back to the LDS files.
MAXDS is the maximum number of output data sets or report entries that can be contained within the LDS. It is defined at Root LDS initialization through the ROOT command of the CADDUTIL utility.
Action:
None.
SPLx is the CADDSPL ID
Reason:
This message is part of the initialization update of the ROOT LDS.
Index defines the number of Indexed entries in the sort data space.
Fields give the sort criteria and up to six fields can be defined
Action:
None.
SPLx is the CADDSPL ID
Reason:
This message is part of the initialization update of the ROOT LDS.
It indicates the optional debugging messages currently active on the system.
Notice, this message is omitted when no optional messages are active.
Action:
None.
xxxx
Key Interval= nnn PAGEOut= nnnn
|
Copyright © 2011 CA.
All rights reserved.
|
|