The CA Dispatch agent produces the messages CADS0172E to CADS999E. They appear in the CADRAS log but may also be presented in the OM Document Viewer or OM Web Viewer. Other CA Dispatch error messages may appear in the CADRAS Region (DRAS Log, JESLOG). These messages may have been passed from CA Dispatch or CADDSPL. When an error or warning occurs, look in the logs of the CA Dispatch Region (CAILOG, DSLOG and JESLOG) for accompanying messages.
This section contains the following topics:
This chapter lists CADS messages.
Reason:
A request to initialize the SNT has been issued but it appears that the CADDSNT was already loaded.
Action:
Setup CAIRIM parameters for DSINIT initialization module with appropriate PARM parameters; see the Getting Started for details.
Reason:
The CA Dispatch initialization has failed.
Action:
Save the dump and contact Technical Support.
Reason:
The CA Dispatch initialization has failed.
Action:
Save the dump and contact Technical Support.
Reason:
The CA Dispatch SVC has been successfully initiated.
Action:
None.
Reason:
A request to refresh the SNT or to delete or reinitialize a module has been issued but it appears that the CADDSNT has not yet been initialized.
Action:
Setup CAIRIM parameters for DSINIT initialization module with PARM(CADDSNT,INIT) and restart the CAIRIM program; see the CA Dispatch Installation Guide for more information.
Reason:
CA Dispatch is initialized for running in a JES3 environment.
Action:
None.
Reason:
DS0INIT was unable to locate JES address space.
Action:
Check for JES2 or JES3 subsystem running and active; if the problem persists, contact Technical Support.
Reason:
The CADDSPL component was successfully initialized.
Action:
None.
Reason:
PARM value of DSINIT initialization module has unexpected values or the format is invalid.
Action:
Set up CAIRIM parameters for DSINIT initialization module with appropriate PARM parameters; see the Getting Started for details.
Reason:
DSINIT was unable to load module module.
Action:
Check that the module whose name appears in the message is accessible from either the STEPLIB or LINKLIST concatenation; if the problem persists, contact Technical Support.
Reason:
A request to delete or reinitialize module module has been issued; module is not supposed to be loaded using DSINIT initialization module.
Action:
Set up PARM value with a valid module name and restart CAIRIM program.
XXXXXXXX is DSINIT or CADDSPLI
YYY Is MVS or JES
Reason:
A valid JES2 or MVS environment could not be determined during either the DSINIT initialization routine or the CADDSPL startup process. Also, see accompanying message CADS014I.
Action:
Review the Z/OS UPGRADE FOR CA Dispatch (UPGRAD) solution that pertains to your operating system environment and verify that you have all of the appropriate compatibility code installed and in place. Verify that when CAIRIM (CAS9) is/was executed that it had access to, and loaded the appropriate operating system compatible code. Verify that the library CADDSPLx is executing from has had the appropriate updates.
Reason:
A request to refresh the SNT cannot be satisfied because system system is still active.
Action:
Stop system system and restart CAIRIM program.
Reason:
Accompanying error message CADS012E, this message displays the JES2 level currently active on your system.
Action:
None.
Reason:
Module module was successfully loaded or deleted.
Action:
None.
Reason:
Module module was requested to be refreshed or deleted but cannot be found in LPA.
Action:
Either primary initialization has never run since the last IPL or a previous request already deleted module module.
No action required.
Reason:
DSINIT was unable to locate active JES address space.
Action:
Check for JES2 or JES3 subsystem running and active; if the problem persists contact Technical Support.
Note: Insure that you have not invoked the CAIRIM proc with SUB=MSTR prior to activating JES.
Reason:
Security has denied access based on report name, job name or recipient name.
Action:
Check security definitions for this user.
Reason:
Security has denied access based on report name or job name.
Action:
Check security definitions for this user.
Reason:
There are currently no reports in CA Dispatch Online Viewing for the recipient ID requested.
Action:
Check in CA Dispatch OLV and in the User Sysgen definitions to make sure the correct user or recipient IDs has been defined. If necessary, add a report to OLV for this recipient.
Reason:
While trying to read a specific report, an error has occurred trying to access an Online Viewing database record (such as OV‑VIEW or OV‑BASE record). This error may also be received if a report has been logically deleted from the VOVMI310 screen.
Action:
Check the logs of the CA Dispatch task to get more information. Check the integrity of the CA Dispatch databases.
Reason:
The CA Dispatch agent encountered an error during signon of the specified user.
Action:
Determine if the user is already signed on to the CA Dispatch panels. If the user is already signed on, log off, and reattempt the signon request.
Reason:
The CA Dispatch address space is not active or cannot be located.
Action:
Make sure that the CA Dispatch region is active. Check the setup parameters to make sure they are addressing the correct CA Dispatch region.
Reason:
The entered user identifier is in the proper format but is not known to the system.
Action:
Make sure that a valid userid has been keyed in.
Reason:
The user has been disconnected from the CA Dispatch region.
Action:
Check the CA Dispatch logs or CA Dispatch OLV to determine if the user was disconnected due to a timeout parameter, deactivated by the CA Dispatch Administrator, or if an error occurred on the IDMS LINE, PTE, or LTE.
Reason:
The CA Dispatch region that this user is communicating with has been shut down.
Action:
Users should log off and after restarting CA Dispatch, they will be able to log on again.
Reason:
A user has been disconnected from CA Dispatch.
This is most probably due to a user timeout from either CA Dispatch, CA DRAS, or the Web Viewer.
Action:
Check the timeout values specified in all products involved. Also, check to see if CA Dispatch has been brought down or if it has abended. Check the CA DRAS and CA Dispatch logs for supporting information.
Reason:
Module CADSQXCV had a problem when trying to acquire storage needed for processing.
Action:
Check the logs for other storage related messages. If the problem persists, recycle the CA DRAS region. If the problem occurs again in a short period of time, contact Technical Support.
Reason:
Module CADSQXST had a problem when trying to attach the UCFAPI module.
Action:
Check the logs for related messages. Verify that module UCFAPI has been properly identified to the CA DRAS job.
Reason:
The correct map or dialog name is not being returned from CA Dispatch to the CA Dispatch agent running in the CA DRAS address space.
Action:
Check to make sure that all of the appropriate dialogs and maps associated with CA Dispatch Cooperative Processing have been installed correctly in the CA Dispatch main region.
Reason:
The CA Dispatch agent is attempting to load a program and it cannot be found.
Action:
Check the load libraries that are specified in the STEPLIB statement of the CA DRAS job and make sure that the proper load modules are included.
Reason:
Requested interface to CA Dispatch cannot be accomplished prior to user signon.
Action:
Check for other errors in the CA DRAS logs and CAILOG. This is likely an internal problem; contact Technical Support.
Reason:
An invalid SQL command was passed to the CA Dispatch agent.
Action:
Check for other errors in the CA DRAS logs. It is likely that this is an internal problem. Contact Technical Support.
Reason:
A working storage area was not correctly passed to module CADSQXCV.
Action:
If this problem persists, contact Technical Support.
Reason:
Requested interface to CA Dispatch cannot be accomplished.
Action:
Check for other errors in the CA DRAS logs and CAILOG. This is likely an internal problem; contact Technical Support.
Reason:
The entered password is in the proper format but is not known to the system.
Action:
Make sure that a valid password has been keyed in.
Reason:
The user has not been defined for CA Dispatch recipient‑based viewing.
Action:
Define the user using the VSGMU230 Sysgen User Screen in CA Dispatch.
Reason:
The user has not had recipients defined for the viewing of reports within CA Dispatch.
Action:
Define recipients for this user by using the VSGMU235 Sysgen User Recipient Screen within CA Dispatch. This will allow the user to view any reports designated for this Recipient ID.
Reason:
The CA Dispatch program CADSBINT had an error while trying to load a program necessary to read a report.
Action:
Make sure that the full Dispatch load library is included in the STEPLIB statement of the CA DRAS startup JCL. Check the CA DRAS JESMSGLG for the following message: DCD0102E Unable to Load Program: pgmname.
This message will identify the problem program.
Reason:
An invalid function request has been passed to the CA Dispatch agent running in CA DRAS.
Action:
Check for other accompanying error messages in the CA DRAS logs. Log off, then log in and try the request again. If the error persists, contact Technical Support.
Reason:
The CA Dispatch agent running within CA DRAS has encountered an error accessing the CADDSPL interface to read a report.
Action:
Check the CA DRAS logs, the CA Dispatch logs, and the CADDSPL logs for other indications of the error. Make sure that the LDS is not full and that it is functioning properly.
Reason:
An illogical condition has occurred while reading pages from the CADDSPL LDS.
Action:
Try browsing the same report when signing directly on to CA Dispatch. Contact Technical Support.
Reason:
An illogical condition has occurred while reading pages from the CADDSPL LDS.
Action:
Try browsing the same report when signing directly on to CA Dispatch. Contact Technical Support.
Reason:
An error occurred when accessing a record in the CA Dispatch Database.
Action:
Follow the same actions that would be taken upon encountering a database error from CA Dispatch directly. Check status of databases or possible errors in the CA Dispatch CAILOG.
|
Copyright © 2011 CA.
All rights reserved.
|
|