|
|
|
The following messages are produced by the CAICCI, CAIRIM, CAIENF, CAIENF/CICS, CAIENF/DB2, and CAIENF/SNMP components.
Reason:
Informational. Title for the CAISMFU-installed SMF program display.
Action:
No action is required.
Reason:
Informational. Blank display for spacing of CAIRIMU and CAISMFU output.
Action:
No action is required.
Reason:
Informational. Heading for the CAISMFU-installed SMF program display.
Action:
No action is required.
Reason:
The message displays information about a CAISMFU-installed SMF program.
Displays the load module name of the installed program.
Identifies the product, version, and level of the installed program in the format ppvl, where pp is the product code, v is the version level, and l is the release level.
Indicates the status of the installed module:
Action:
No action is required.
Reason:
The message displays the following information in the CAISMFU utility output:
Displays the total number of interfaces that have been installed, including active interfaces made inactive due to abends.
Displays the total number of SMF programs called for processing. This number is roughly the number of active interfaces multiplied by the number of SMF calls.
Action:
No action is required.
Reason:
Informational. Title from the CAIRIMU-initialized product and component display.
Action:
No action is required.
Reason:
Informational. Heading for the CAIRIMU-initialized product and component display.
Action:
No action is required.
Reason:
Entries in the CAIRIMU-installed initialized product and component display. Fields defined as follows:
Displays the name of the product or component initialized.
Identifies the version of the product or component initialized.
Identifies the product module name that performed the initialization.
Note: These modules are delivered with the products and not with CAIRIM.
Displays the date on which the product or component was initialized.
Displays the time at which the product or component was initialized.
Action:
No action is required.
Reason:
Indicator in the CAIRIMU-initialized product and component display that defines the load library from which the product or component was initialized. This is only present if an alternate load library was specified in the CAIRIM parameter library, as defined through the PARMLIB DD statement.
Action:
No action is required.
Reason:
Output from CAIRIMU. Displays the total number of product and component interfaces that have been initialized through CAIRIM.
Action:
No action is required.
Reason:
If executing CAIRIMU, the CAIRIM Resource Initialization Manager has not been run or has abended prior to creating the in-storage initialization index.
If executing CAISMFU, the CAISMFI dynamic SMF interceptor program has not been run or has abended prior to creating the in-storage module index.
Action:
If executing CAIRIMU, make sure that a valid file (as defined through the PARMLIB DD statement) exists and that it contains one or more initialization parameters. Then rerun CAIRIMU by executing the CAIRIM procedure supplied as CAS9. For assistance, contact CA Support at http://ca.com/support.
If executing CAISMFU, check the CAIRIM System Requirements section of your product Installation Guide for information on the use of CAISMFI by the product. If there are no products installed that use CAISMFI, this is a normal condition. If your installation contains one or more products using CAISMFI, then rerun CAIRIM. For assistance, contact CA Support at http://ca.com/support.
Reason:
The indicated number of warnings and violations have occurred for all software solutions using CA LMP on the specified CPU's serial number.
Action:
If you have contacted CA LMP support and your software solution licensing agreement has been updated for the solution in warning or violation, or both, this message is informational.
If you have not contacted CA LMP support or your software solution licensing agreement has not been updated for the solution in warning or violation, see message CAS9013A for further details on the solutions in warning or violation.
Reason:
CAIRIM has initialized product xx and that product is running (xx is your CA solution's product code). However, your CA LMP agreement for this product is about to expire or has expired and CA LMP execution software may deactivate the product in the near future if the situation is not corrected.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The CA LMP execution key is required to run the CA solution.
Action:
Contact CA LMP support. Report the seed value displayed in this message to obtain the execution key.
Reason:
An access code is required to extend operation of a CA solution for which the licensing agreement has expired.
Action:
Enter the access code obtained from CA LMP support.
Reason:
The access code entered is invalid according to CA LMP execution software.
Action:
Verify that you entered the correct access code as given to you by CA LMP support. If the access code was entered correctly, contact CA LMP support.
Reason:
The access code you entered to obtain a licensing extension has been accepted and the extension is in effect.
Action:
No action is required.
Reason:
An invalid parameter has been detected on input to S910INIT.
Action:
Review the PARM() identified in the message. Valid parameters are REINIT, REFRESH, and DELETE. Correct the parameter field and resubmit the job. For more information on valid operands, refer to the Administration Guide.
Reason:
No valid security system exists within the environment. RACF or a RACF-compatible security product is required.
Action:
Remove the product initialization control card from the CARIMPRM file until a valid security environment is installed (like CA Top Secret, CA ACF2, RACF, or a RACF-compatible product).
Reason:
Informational message pertaining to the execution of S910INIT.
Action:
No action is required.
Reason:
An error was encountered during CAISSF initialization.
Action:
Ensure routines CAS9SEC and the external security translator are available through the CAS9 STEPLIB or linklisted data set:
|
Security System |
Translator |
|---|---|
|
CA Top Secret |
CAS9TS42 |
|
CA ACF2 |
CAS9ACF2 |
|
RACF or RACF compatible |
CAS9SAFC |
If the routines are already present on the system and you wish to update CAISSF through maintenance, use the PARM(REFRESH(SSF)) parameter. For more information, see the Administration Guide.
Reason:
No valid security system exists within this environment.
Action:
Reply with a security system to continue or N to cancel. If you reply N, message 'CAS9021E ENVIRONMENT ERROR DETECTED. UNABLE TO ADD CAISSF ROUTINES' will be displayed, indicating there is no security system available.
Reason:
No valid security system exists within this environment.
Action:
Reply with a security system to continue or N to cancel. If you reply N, message 'CAS9021E ENVIRONMENT ERROR DETECTED. UNABLE TO ADD CAISSF ROUTINES' will be displayed, indicating there is no security system available.
Reason:
Informational.
Action:
No action is required.
Reason:
An internal error has been detected.
Action:
An IPL is required to refresh the given routine. If running CAIRIM for the first time, ignore this message.
Reason:
The caller of external security interface has passed a function code that is not supported.
Action:
Gather all relevant documentation for analysis. For assistance, contact CA Support at http://ca.com/support.
Reason:
An error has been detected during SIGNON processing. SIGNON processing initiates a RACF RACINIT request. This message is passed back to the caller and action is taken as needed. All RACF messages are handled on behalf of the application product.
Action:
See the following chart. Then consult your IBM System Programming Library: Application Development Macro Reference for further information on the RACF return codes, if needed.
Possible messages issued for SIGNON processing are:
|
Return Code |
Message |
|---|---|
|
RC=04 (04) |
User profile is not defined |
|
RC=08 (08) |
Password given is not authorized |
|
RC=12 (0C) |
Password given has expired |
|
RC=16 (10) |
New password given is invalid |
|
RC=20 (14) |
User is not defined to group |
|
RC=24 (18) |
RCINIT filed installation exit |
|
RC=32 (20) |
RACF is not active |
|
RC=36 (24) |
User access has been revoked |
|
RC=40 (28) |
OIDCARD is required |
|
RC=44 (2C) |
OIDCARD is invalid |
|
RC=48 (30) REASON=04 |
No access to terminal on this day or time |
|
RC=48 (30) REASON=08 |
Not authorized for terminal |
|
RC=52 (34) |
Not authorized for application |
|
N/A |
Caller not APF authorized for function |
|
RC=12 (0C) |
Option (USER= ) is missing |
|
RC=12 (0C) |
Option (PW= ) is missing |
Note: The numbers in parentheses in the Return Code column are HEX values.
Reason:
An error has been detected during SIGNOFF processing. This message is passed back to the caller and action is taken as needed.
Action:
Refer to the indicated message and take the required action.
Possible messages issued for SIGNOFF processing are:
|
Return Code |
Message |
|---|---|
|
(08) |
Caller not APF authorized for function |
|
(08) |
ACEE not found, SIGNOFF ignored |
Reason:
An error has been detected during EXTRACT processing. This message is passed back to the caller and action is taken as needed.
Action:
Refer to the indicated message and take action as required. For example, if the message reads SECURITY RECORD NOT FOUND, it may indicate that the userid you are logged onto is not defined to RACF. Or, if you are attempting to invoke a transaction under CICS that uses external security, you may not have signed onto the terminal through CSSN or CESN.
Reason:
An error has been detected during RESOURCE ACCESS processing. RESOURCE ACCESS processing initiates a RACF RACSTAT, RACDEF, RACLIST, or RACHECK request. This message is passed back to the caller and action is taken as needed.
Action:
See the following chart. Then consult your IBM System Programming Library: Application Development Macro Reference for further information on the RACF return codes, if needed.
Possible messages issued for RESOURCE ACCESS processing are:
|
Return Code |
RACF Function |
Message |
|---|---|---|
|
RC=12 (0C) |
N/A |
Option (CLASS= ) is missing |
|
RC=12 (0C) |
N/A |
Option (CLASS= ) is invalid |
|
RC=12 (0C) |
N/A |
Option (ENTITY= ) is missing |
|
RC=12 (0C) |
N/A |
Option (RESLEN= ) is missing |
|
RC=12 (0C) |
N/A |
Unable to obtain ACEE for resource check |
|
RC=12 (0C) |
N/A |
Caller not APF authorized for function |
|
RC=04 (04) |
RACSTAT |
Class specified is inactive |
|
RC=08 (08) |
RACSTAT |
Class specified is not defined |
|
RC=12 (0C) |
RACSTAT |
RACF is inactive, class is inactive |
|
RC=16 (10) |
RACSTAT |
RACF active, class is inactive |
|
RC=20 (14) |
RACSTAT |
RACF inactive, class is not defined |
|
RC=24 (18) |
RACSTAT |
Unable to locate RACF CVT |
|
RC=04 (04) |
RACHECK |
Resource is not protected |
|
RC=08 (08) |
RACHECK |
Access to resource is denied |
Reason:
The caller of the external security interface passed an invalid function code.
Action:
Gather all relevant documentation for analysis. For assistance, contact CA Support at http://ca.com/support.
Reason:
OS GETMAIN for RACROUTE work area has failed.
Action:
Increase region size for the task that external security is running under and retry.
Reason:
The CAS9RACL program issued a z/OS GETMAIN to obtain storage for its work area, but the system was unable to satisfy its request.
Action:
Increase the amount of available OSCORE in the CICS region and retry.
Reason:
The CAS9RACL program has issued a RACROUTE REQUEST=LIST,ENVIR=CREATE for the specified class name (cccccccc). The return and reason codes indicate whether the operation was successful or not.
Action:
If the request ended with RCs and REASON = 0000, no action is necessary and the message is informational. If the request ended with a nonzero return or reason code, see z/OS Security Server RACROUTE Macro Reference (sections REQUEST=LIST, Return codes and reason codes).
Reason:
Informational. Title for the CAISUBU installed subsystem display.
Action:
No action is required.
Reason:
Informational. Heading for the CAISUBU-installed subsystem display.
Action:
No action is required.
Reason:
The message displays information about a CAISUBU-installed subsystem.
Displays the four-character name of the subsystem installed by CAIRIM.
Displays the hexadecimal address of the SSCT.
Indicates the status of the installed subsystem:
Displays the name of the subsystem initialization program, if any.
Action:
No action is required.
Reason:
Informational. Displays current version, and genlevel for the CA Common Service indicated in the message.
Action:
No action is required.
Reason:
Product pp could not be found on a specific product display request, for example, PROD(pp).
Action:
Reenter the command with a valid product code.
Reason:
Header for displaying LPAR-mode CPU statistics in the multiline LMP report.
Action:
See message CAS9078I.
Reason:
CPU statistics of the multiline LMP report when the processor is running in LPAR mode.
Identifies the current number of dedicated CPUs.
Identifies the current number of shared CPUs.
Identifies the number of dedicated CPUs observed 90% of the time during the LMP collection cycle.
Identifies the number of shared CPUs observed 90% of the time during the LMP collection cycle.
Identifies the dedicated CPU high-water mark.
Identifies the shared CPU high-water mark.
Action
This message is informational only.
Reason:
Output of the multiline LMP report when the processor is running in LPAR mode.
Identifies the LPAR name.
Identifies the LPAR number.
Action:
This message is informational only.
Reason:
The first output line of a PROD request.
The product code.
The number of times the product has issued a violation warning message (CAS9182) or violation expiration message (CAS9180).
The current violation status is one of the following:
The product is currently at or past its expiration date.
The product is within the expiration warning period.
Neither Y nor W.
The date violation warning messages will commence 30 days before the initial expiration date.
Action:
This message is informational only.
Reason:
The second output line of a PROD request.
Indicates the initial product expiration date.
Identifies the final expiration date (generally a grace period of 30 days beyond the initial product expiration date). This is the last date that the LMP key will be accepted and the last date the CAS9181A message will be displayed for the product.
Action:
Informational.
Reason:
The first line of the multiline LMP report.
The hardware CPU ID.
The processor mode:
Machine (native) mode
LPAR mode
VM hypervisor mode
Action:
Informational.
Reason:
Output of the multiline LMP report when the processor is running in z/VM mode.
The name of the z/VM hypervisor.
The z/VM control program ID.
The number of active virtual machines running under the z/VM hypervisor.
Action:
Informational.
Reason:
Output of the multiline LMP report showing the processor manufacturer and model.
Action:
Informational.
Reason:
Output of the multiline LMP report showing the start time and date of the LMP collector.
Action
Informational.
Reason:
Output of the multiline LMP report showing the number of LMP collection cycles.
Action:
Informational.
Reason:
Title line for CPU statistics reporting in the multiline LMP request.
Action:
Informational.
Reason:
Header for displaying CPU statistics in the multiline LMP report.
Action:
See message CAS9097I.
Reason:
CPU statistics report of the multiline LMP request.
The current total number of CPUs.
The current number of configured CPUs.
The number of total CPUs observed 90% of the time during the LMP collection cycle.
The number of configured CPUs observed 90% of the time during the LMP collection cycle.
The total CPU high-water mark.
The configured CPU high-water mark.
Action:
Informational.
Reason:
Header for displaying CPU statistics in the multiline LMP report.
Action:
See message CAS9099I.
Reason:
CPU statistics report of the multiline LMP request.
The current number of standby CPUs.
The current number of reserved CPUs.
The number of standby CPUs observed 90% of the time during the LMP collection cycle.
The number of reserved CPUs observed 90% of the time during the LMP collection cycle.
The standby CPU high-water mark.
The reserved CPU high-water mark.
Action:
Informational.
Reason:
Multiple CAIRIM tasks have been started. Due to serialization requirements, only one CAIRIM task can be active at a time. Processing terminates.
Action:
If executing CAIRIM concurrently to install LMP Keys, wait for CAIRIM to complete and then retry.
Reason:
Third output line of a PROD request that is displayed only if the product is within, or has gone beyond, its initial product expiration date, or if an unlicensed product was started.
The date and time of the first and last usage violations.
Action:
This message is informational only.
Reason:
An LPA manager request (#LPA) failed.
Either ADD or DEL.
Identifies the object name.
Identifies the return code.
Identifies the reason code in the format rrrrf1f2, where:
Identifies the actual CSVDYLPA reason code
The CSVDYLPA LMPEA output flags that report the status of the request.
Action:
This is a serious error. The #LPA issuer (for example, CAIRIM) will likely issue its own error message, take corrective action, or terminate in error. Report this error to CA Support. Information on CSVDYLPA error and diagnostic codes can be found in IBM document z/OS MVS Programming Authorized Assembler Reference and member CSVLPRET in SYS1.MACLIB. Depending on the type of error received, message CAS9103E may also be posted to qualify the error.
Reason:
The LPMEA output flags in message CAS9102E indicated an unexpected abend or return code that required further clarification.
Identifies the return and reason codes for the unexpected condition.
or
An error was received from a supporting z/OS service (for example, DYNALLOC) invoked by CSVDYLPA, which produced its own set of reason codes. diag1 and diag2 are the codes returned by the supporting z/OS service.
Action:
See message CAS9102E Action.
Reason:
A request to load the specified module failed. The return code is in R15.
Action:
Make sure the module name is available in a STEPLIB or Link List data set. Check for other error messages preceding this one. For assistance, contact CA Support at http://ca.com/support.
Reason:
An internal error has occurred within the CAIRIM module. No products are initialized.
Action:
Obtain documentation for analysis. For assistance, contact CA Support at http://ca.com/support.
Reason:
A noncritical resource was unavailable. CPU observance information will be omitted. Message CAS9113E precedes this message. CAIRIM continues.
Action:
No action is required.
Reason:
You have not coded a PARMLIB DD statement and an attempt to allocate SYS1.PARMLIB member CAISYS00 has failed. Processing terminates.
Action:
Review the parameter file for invalid data. See the Installation Guide for information regarding CAIRIM parameters.
Reason:
This message is intended to help CA Support. It identifies the in-storage location of an LMP control area.
Action:
No action is required.
Reason:
A call to the z/OS service to obtain LMP licensing data failed with return code (rc). LMP licensing collection impossible.
Action:
Report this message to CA Support.
Reason:
A call to the z/OS service to obtain central storage failed with return code (rc). This may or may not be critical, depending on the component (ccccc) making the request.
Action:
Increase the CAIRIM region size. For assistance, contact CA Support at http://ca.com/support.
Reason:
This message follows a previous message that tells why this function is being disabled.
Action:
See the previous message.
Reason:
Provides a listing of control statements as read from the CAIRIM parameter file. When this message is invoked by CA LMP, one of the following variable substitutes can be displayed:
Action:
Verify keyword, product code, or CPU ID as indicated and reenter. If the message recurs, contact CA LMP support.
Reason:
Informational message issued when a valid EKG device code has been entered:
Displays the month the device was activated.
Displays the day the device was activated.
Displays the year the device was activated.
Action:
No action is required.
Reason:
Issued in response to starting CAIRIM coding PARM=EKGP in the JCL EXEC statement.
Action:
Enter the eight-byte character code from the activated EKG device, or CANCEL to continue processing.
Note: The eight-byte character code in the action above is not case-sensitive.
Reason:
Certification of a critical CAS9 control block failed.
Action:
Report this message to CA Support.
Reason:
The OPAISTAT call to update the OPS/MVS STATEMAN table has encountered an error. The return code (RC) and reason code from the error are displayed in the message.
Action:
Contact CA Support for all errors.
Reason:
A prompt resulting from a CONSOLE control statement in the parameter file. Enter statements from the console exactly as they would appear in the parameter file. To terminate input, reply END to this prompt.
Action:
No action is required.
Reason 1:
Invalid data has been encountered in the input parameter file. Processing continues with the next input record.
Action 1:
Review the CAIRIM parameter file for invalid data.
Reason 2:
Missing keyword, where one of the following is listed:
Action 2:
Verify the indicated field on the control card.
Reason 3:
One of the keywords is a duplicate, and was found more than once on the control card.
Action 3:
Verify the indicated field on the control card and remove the duplication.
Reason 4:
Product code keyword word is not two characters.
Action 4:
Verify the product code for your CA solution and confirm it is correctly defined on the control card.
Reason 5:
CPU keyword is too long.
Action 5:
Verify the correct definitions for the CPU and confirm it is correctly defined to the control card.
Reason 6:
CPU operand is too long.
Action 6:
Ensure the CPU keyword is in the proper format of mmmm-tttt.
Reason 7:
CPU serial number is not six characters.
Action 7:
Confirm that the correct serial number of six characters is defined to the CPU keyword of the control card.
Reason 8:
DATE keyword is not seven characters.
Action 8:
Confirm that the DATE keyword defined to the control card is in the format ddmmmyy.
Reason 9:
LMPcode keyword is invalid.
Action 9:
Ensure that the LMPcode on the control card has been defined correctly.
Reason 10:
Key tampering detected or transcription error.
Action 10:
Call LMP support. The LMPcode defined to the control card is now invalid.
Reason 11:
LMPcode listed ID for another CPU.
Action 11:
Verify that the LMPcode defined to the control card is correct and that you are attempting to start your CA solution on the correct CPU.
Reason 12:
The EKG control card must be the first control card (comments are ignored) in the KEYS DD.
Action 12:
Ensure that the EKG control card is first in the KEYS DD.
Reason 13:
The length of the data within the () of the EKG control card is not eight bytes long.
Action 13:
Verify that the length of the data within the () of the EKG control card is eight bytes long.
Reason 14:
More than one EKG control card was found in the KEYS DD. Only the first one is used and all others are ignored.
Note: If EKGP was entered and there is an EKG control card in the KEYS data set, then the one entered at startup is used.
Action 14:
No action is required.
Reason 15:
The EKG data entered was not correct. The control card will be ignored.
Action 15:
Reenter the data into EKG correctly and check for transcription errors.
Reason 16:
The EKG device was activated more than ten days ago. The system date must be within ten days of the date the EKG device was activated.
Action 16:
If you need to execute with dates that do not fall in this range, you must contact CA LMP support to get temporary execution keys.
Reason:
A product initialization routine has successfully completed.
Action:
No action is required.
Reason:
A nonzero return code was returned by z/OS dynamic allocation. 'dsn' is the data set name in question and 'error' is the error and reason codes returned by SVC 99. Processing continues with the next product, unless the error is for the control statement library (SYS1.PARMLIB), in which case dynamic installation is aborted.
Action:
Ensure that the data set indicated by 'dsn' exists and is available on this processor.
Reason:
An error has occurred while attempting to initialize the named product. 'err' contains one of the following as the error description:
Action:
Any of these errors cause CAIRIM to terminate processing for the current product and continue with any remaining control statements. See the error descriptions for indication of probable error cause.
Reason:
Function F($$$) encountered an error during an attempt to install a service. RC($$$) is the non-zero return code from the function.
Action:
Contact CA Support.
Reason:
An error has occurred that cannot be isolated to a specific product. Processing terminates.
Action:
Contact your support personnel.
Reason:
An error has occurred while attempting to open the AUTOCMDS file. Automatic command processing terminates.
Action:
Ensure that the file defined by the AUTOCMDS DD statement in the CAS9 procedure exists, is available on this processor, and is readable.
Reason:
Provides a listing of automatic commands as read from the AUTOCMDS file.
Action:
No action is required.
Reason:
Automatic command processing has detected an invalid statement.
Action:
Enter any character to continue. To correct the error, verify the control card on which the message was issued. If it occurred on a control card that had WAIT coded, ensure that the WAIT parameter is coded as WAIT(nnn), where nnn is a number of seconds from 0 to 999.
Reason:
A WAIT(nnn) command is being processed.
Action:
No action is required.
Reason:
An invalid WAIT time has been specified. The WAIT time must be in the format WAIT(nnn), where nnn is a number of seconds from 0 to 999.
Action:
Correct the WAIT time and reexecute CAS9.
Reason:
The LMP KEYS DD statement cannot be found.
Action:
The CA LMP KEYS for running CA solutions cannot be found. Contact the appropriate CA office for CA LMP support if you have not received your CA solution LMP KEYS. If you have your CA LMP KEYS properly stored into a library, then place the appropriate KEYS DD statement into the CAS9 procedure, and re-execute the current Job Step.
Reason:
CAIRIM detected a missing CA LMP module during initialization.
Action:
Ensure that the indicated module is present in the CAS9 (CAIRIM) STEPLIB or system LNKLST concatenation and reexecute CAS9.
Reason:
CAIRIM detected errors during CA LMP initialization.
Action:
See accompanying messages for a more detailed description of this error. Save all dumps and other diagnostics for CA Support assistance, if needed.
Reason:
An LMP SiteID control card was read and accepted, where xxxxxxxx is the site number from the SiteID statement.
Action:
Informational, the indicated solution will be allowed to run.
Reason:
An LMP SiteID control card was read and accepted, where xxxxxxxx is the client name from the SiteID statement.
Action:
Informational, the indicated solution will be allowed to run.
Reason:
An LMP SiteID control card was read and accepted, where xxxxxxxx is the location from the SiteID statement.
Action:
Informational, the indicated solution will be allowed to run.
Reason:
Where @@@@@@ is the CPU ID, xx is the product code, and xxxxxxxx... is the product name of the software solution CAIRIM has tried to initialize. The CA LMP execution software does not possess the key to the given product on this CPU.
Action:
Contact CA LMP support.
Reason:
Although your license agreement for this software solution has expired, deactivation has been postponed for the reason indicated by xxxxxxxx... (for example, this value could be 'WEEKEND').
Action:
Contact CA LMP support as soon as possible to avoid potential expiration of the CA solution licensing agreement and discontinuance of the CA solution initialization.
Reason:
Your CA LMP licensing agreement for this product is about to expire, where xx is the CA solution licensed to run on this CPU and $$$ is the number of days remaining in the license agreement.
Action:
Contact CA LMP support as soon as possible to avoid potential expiration of the CA solution licensing agreement and discontinuance of the CA solution initialization.
Reason:
Product (xx) will expire in one day.
Action:
Contact CA LMP support.
Reason:
An LMP control card was read and accepted, where xx is the product code for a particular CA solution.
Action:
Informational, the indicated solution will be allowed to run.
Reason:
An LMP control statement was read and accepted, and it contained the DELETE keyword to remove this LMP key.
Action:
Informational, the indicated solution will be allowed to run.
Reason:
You are attempting to start a new release of ENF on a system that has already had an older release started and the EVT control block has a format that is incompatible with the new release.
Action:
You must IPL before attempting to start the new release of ENF. You can restart the old release of ENF if you must wait to IPL.
Reason:
CAIENF has initialized successfully and is available for use by other applications.
Action:
No action is required.
Reason:
CAIENF has been started while another copy is active. Only a single copy of CAIENF may be active within a CPU at any time.
Action:
Stop CAIENF before attempting the restart.
Reason:
CAIENF is unable to locate a required module. Initialization abends with a user 202 completion code.
Action:
Ensure that module xxxxxxxx exists and that all STEPLIB and LNKLST specifications are correct.
Reason:
CAIENF has encountered a database error or internal abend during initialization processing. Processing terminates with a user 203 abend.
Action:
Ensure that the database defined to CAIENF exists and has correctly initialized (see the Administration Guide for more information on listing the contents of a database).
Reason:
CAIENF is unable to initialize a data element. Processing continues, although applications receive errors if the named data element is accessed.
Action:
Ensure that the database defined to CAIENF exists and has correctly initialized (see the Administration Guide for more information on listing the contents of a database). Also, ensure that the routine that processes the data element exists, and check STEPLIB and LNKLST specifications.
Reason:
CAIENF is unable to initialize an event. Processing continues although the event, if issued, is ignored.
Action:
Ensure that the database defined to CAIENF exists and has correctly initialized (see the Administration Guide for more information on listing the contents of a database). Also, ensure that the routine that initialized the event exists, and check STEPLIB and LNKLST specifications.
Reason:
CAIENF is restarting after a prior shutdown or abend.
Action:
No action is required.
Reason:
CAIENF has received an error of code nnnn from its database component. This message is followed by other messages that give a more detailed description of the condition.
Action:
See accompanying messages.
Reason:
Produced following message CAS9207E when diagnostic options are enabled. Message contains the text of a database component-generated error message.
Action:
No action is required.
Reason:
Produced following message CAS9207E when diagnostic options are enabled. Message contains the text of a database query that was issued by CAIENF.
Action:
No action is required.
Reason:
CAIENF has trapped recursive errors that are no longer recoverable. CAIENF abends with a user 210 completion code. Other messages explain the cause of the error.
Action:
See original error description(s).
Reason:
CAIENF has been restarted with the REINIT control option. All global CAIENF modules are reloaded.
Action:
No action is required.
Reason:
The CAIENF operator command interface has experienced nonrecoverable abend conditions. Processing continues, but no further ENF commands can be processed.
Action:
Restart CAIENF at your earliest convenience.
Reason:
CAIENF has been started with a control option that requires CAIENF to be fully initialized. The command is delayed until CAIENF initialization completes.
Action:
No action is required.
Reason:
Echoes the text of an ENF operator command.
Action:
No action is required.
Reason:
The operator has not replied Y to the CAS9227 message. The shutdown request is ignored.
Action:
No action is required.
Reason:
An invalid control option has been entered. The variable area of the message contains a description of the nature of the problem.
Action:
Correct and reenter the command.
Reason:
CAIENF database initialization is beginning.
Action:
No action is required.
Reason:
The CAIENF database component has been initialized and is now available for processing queries.
Action:
No action is required.
Reason:
An internal CAIENF subtask has terminated or abended. Depending on the nature of the subtask, CAIENF takes corrective actions (such as reestablishing the task).
Action:
No action is required.
Reason:
While processing an event, CAIENF has detected an error condition (such as a storage GETMAIN failure or corruption of internal queues). Data for the current event is lost.
Action:
No action is required.
Reason:
During initialization, CAIENF has not been able to open or read the ENFPARMS file. Parameters entered on the start or //EXEC JCL statements are used with CAIENF system defaults.
Action:
If required, specify an //ENFPARMS DD statement within the CAIENF started task JCL.
Reason:
CAIENF has detected an error during processing for a control option.
Action:
Correct and reenter the control option.
Reason:
CAIENF has detected an error during processing for a control option.
Action:
Correct and reenter the control option.
Reason:
During initialization, CAIENF has detected that the database it is to use is running within another address space. CAIENF continues and uses the external database.
Action:
No action is required.
Reason:
The operator has entered a shutdown request. Replying other than Y causes CAIENF to ignore the shutdown and continue normal processing. If shut down, services are not available to any CAIENF product until CAIENF is restarted.
Action:
Reply Y to continue with the shutdown.
Reason:
The operator has entered a shutdown request. Replying other than Y causes CAIENF to ignore the shutdown and continue normal processing. If shutdown, services are not available to any CAIENF product until CAIENF is restarted.
Action:
Reply Y to continue with the shutdown.
Reason:
The operator has entered a shutdown request. Replying other than Y causes CAIENF to ignore the shutdown and continue normal processing. If shut down, services are not available to any CAIENF product until CAIENF is restarted.
Action:
Reply Y to continue with the shutdown.
Reason:
An internal CAIENF application has been successfully started within the CAIENF address space.
Action:
No action is required.
Reason:
An internal CAIENF application has encountered an error during initialization.
Action:
Consult the documentation for the appropriate application for more information.
Reason:
The ENF parameter or command just processed is obsolete. In the event of a parameter, remove it from the ENFPARMS member. The parameter/command is ignored.
Action:
Remove the parameter from the ENFPARMS member.
Reason:
The CAIENF/CICS service has not been installed. No CAIENF/CICS supported features are available.
Action:
If CAIENF/CICS is not installed, see "CAIENF/CICS Requirements" in the Installation Guide.
If the CAIENF/CICS service is in use at your installation, see "How CAIENF/CICS Checks for Intercept Modules" in the Administration Guide.
Reason:
A P ENF command has been issued to stop CAIENF. At the time this message was issued, CAIENF determined that one or more of its subtasks were still active.
Action:
No action is required. If CAIENF subtasks are still active after four minutes following the initial P ENF command, CAIENF terminates the subtasks and then shuts itself down. If CAIENF writes a dump during the shutdown process, gather all relevant documentation and contact CA Support.
Reason:
A REFRESH command was issued for module xxxxxxxx from the specified library.
Action:
No action is required.
Reason
ENF was unable to initialize an IMUF operation because a critical task either could not be started, ended prematurely, or ended in error.
The name of the failing task.
The system and user completion codes, respectively.
Action
The ENF started task terminates. Report this error to your ENF administrator.
Reason:
The operator has entered a shutdown request during CAIENF backup processing. Replying with a value other than X causes CAIENF to ignore the shutdown and continue normal processing. If shut down, the backup subtask is immediately detached, which may result in unrecoverable database errors.
Action:
Allow the CAIENF backup to complete normally by replying with a value other than Y. When the backup is complete, CAIENF can now be shut down normally through the PENF operator command.
Reason:
An executable module required by the ENF data recording component (Datacom) cannot be found in the ENF STEPLIB/JOBLIB concatenation or the z/OS LINKLIST. This is a non-deletable operator action message.
The name of the missing element.
Action:
ENF initialization aborts. This message is followed by message CAS9237A. Report this condition to your ENF administrator.
This message is posted in tandem with message CAS9236E to report a serious error condition while attempting to initialize the ENF Datacom component. This message advises the user to have their ENF administrator/support personnel verify proper installation of the ENF Datacom event recording component. This is a non-deletable operator action message.
Action:
See message CAS9236E.
Reason:
ENF was started under a version and release of the operating system that is not supported by the product.
Action:
Start ENF under a supported version and release of the operating system. The minimum operating system level for ENF is z/OS 1.4.0.
Reason:
Signifies completion of a CAIENF command.
Action:
No action is required.
Reason:
The command XSYSLOGR=(ON|REF) was issued and there are no events currently marked as record.
Action:
Turn on event recording and issue the command again.
Reason
A MUF command was forwarded by IMUFCMD to the imbedded MUF (IMUF) task.
Action
None. This is an informational message.
Reason
ENF acknowledgement that IMUF operation is in effect.
Action
None. This is an informational message.
Reason
A previous IMUF parameter was already processed. Only one is allowed.
Action
This IMUF statement is discarded and ENF initialization continues.
Reason:
An MVS STOP command was issued against the ENF address space.
Action:
No action is required.
Reason:
An MVS STOP command was issued against the ENF address space.
Action:
No action is required.
Reason:
The shutdown process for ENF took longer than two minutes to complete, and SYNCDUMP(YES) had been specified in ENFPARMs.
Action:
Supply the DUMP to CA Support for review.
Reason:
ENF DIAG(AP) command was issued but trace table is not in CSA.
Action:
Change ENFPARM TRACE so that it is in the following format:
TRACE(nnn,CSA)
Then, recycle ENF and issue ENF DIAG(AP) command again.
Reason:
A CA-ENF listening application has terminated without signaling ENF that ENF services were no longer needed.
The application's ID (JES-assigned job name/number and internal listener name) is displayed in the message.
Action:
Check the log of the listening application for a possible problem.
Reason:
Output from the ENF STATUS operator command. The variable field defines the SMF system ID where CAIENF is running, respectively.
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable fields are defined as the date and time when CAIENF was initialized, whether recording of events to the database is occurring or not, and the percentage of the Datacom database that is being used.
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable fields are defined as follows, respective to the order displayed:
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable fields are defined as follows, respective to the order displayed:
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable fields are defined as follows, respective to the order displayed:
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The first two variable fields, in parentheses, are defined as the diagnostic option and the internal CAIENF status, respectively. The third variable field contains one of the following:
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable fields are defined as follows, respective to the order displayed:
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable fields are defined as follows, respective to the order displayed:
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable fields are defined as follows, respective to the order displayed:
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable fields are defined as follows:
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable fields are defined as follows, respective to the order displayed:
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable fields are defined as follows, respective to the order displayed:
Action:
No action is required.
Reason:
Response from the ENF APPL operator command. The variable fields, with respect to the order displayed, are defined as follows:
Identifies the application currently listening for CAIENF events. The ID consists of the application's JES-assigned job name/number and internal listener name.
Displays the number of events for which the application is currently listening.
Indicates the status of the application. This can be one of six conditions:
Action:
No action is required.
Reason:
Response from the ENFAPPL operator command. CAIENF has determined there are no applications actively listening for CAIENF events.
Action:
No action is required.
Reason:
Response from the ENF APPL operator command. The variable fields, with respect to the order displayed, are defined as follows:
The number of CAIENF events queued to the application.
The elapsed time, in minutes and seconds, since the application last listened for CAIENF events.
Action:
No action is required.
Reason:
Output from the ENF DCOL operator command. The variable fields are defined as follows, respective to order displayed:
Action:
No action is required.
Reason:
Output from the ENF DCOL operator command. The variable fields are defined as follows, respective to order displayed:
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable field is defined as status of the CAIENF/CICS service.
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable fields are defined as follows, respective to the order displayed:
Action:
No action is required.
Reason:
Output from the ENF STATUS operator command. The variable field is defined as the total number of CICS regions with CAIENF installed.
Action:
No action is required.
Reason:
Output from the ENF MAP operator command. Output contains the addresses of various internal CAIENF control blocks and modules.
Action:
No action is required.
Reason:
Output from the ENF MAP operator command. Output contains the addresses of various internal CAIENF control blocks and modules.
Action:
No action is required.
Reason:
Output from the ENF MAP operator command. Output contains the addresses of various internal CAIENF control blocks and modules.
Action:
No action is required.
Reason:
Output from the ENF MAP operator command. Output contains the addresses of various internal CAIENF control blocks and modules.
Action:
No action is required.
Reason:
Output from the ENF MAP operator command. Output contains the addresses of various internal CAIENF control blocks and modules.
Action:
No action is required.
Reason:
Output from the ENF MAP operator command. Output contains the addresses of various internal CAICCI control blocks and modules.
Action:
No action is required.
Reason:
Output from the ENF MAP operator command. Output contains the addresses of various internal CAIENF control blocks and modules.
Action:
No action is required.
Reason:
Output from the ENF MAP operator command. The output contains the address of various internal CAIENF control blocks and the SYSID specified in ENFPARMS.
Action:
No action is required.
Reason:
Output from the ENF EVENT operator command. The variable fields are defined as follows, respective to the order displayed:
Action:
No action is required.
Reason:
Output from the ENF EVENT operator command. The variable fields are defined as follows, respective to the order displayed:
Action:
No action is required.
Reason:
Output from the ENF EVENT operator command. The variable field is defined as number of times event has been issued.
Action:
No action is required.
Reason:
While processing an ENF DUMP command, CAIENF was unable to dynamically allocate a SYSOUT file. RC contains the dynamic allocation return code and reason code in hexadecimal. The dump is not written.
Action:
Examine the dynamic allocation return codes. If required, place an ENFDUMP DD statement in the CAIENF started task JCL to override the dynamic allocation request.
Reason:
While processing an ENF DUMP command, CAIENF was unable to open the dump output file.
Action:
If using a pre-allocated ENFDUMP DD statement, ensure that all JCL parameters are correct.
Reason:
The CAIENF application had one or more events queued to it and the elapsed time since the application last listened for events has exceeded the limit. All events queued to the application have been dropped and no more events will be queued to the application.
The application's ID (JES-assigned job name/number and internal listener name) is displayed in the message.
Action:
Ensure the application is functioning properly. Search the problem reporting databases for a solution. If you are unable to be resolved the problem, contact CA Support.
Reason:
Output from the ENF event, ENF select, or ENF screen operator command. The variable fields are defined as follows, respective to the order display:
Action:
No action is required.
Reason:
Response from the ENF MSGEVENT operator command. CAIENF has determined there are no installation-defined messages that ENF is to intercept and generate JOBFAIL events for.
Action:
No action is required.
Response from the ENF MSGEVENT operator command.
where:
The message prefix.
The JOBFAIL event type.
Action:
No action is required.
Reason:
Response from the ENF MSGEVENT operator command.
where:
The JOBFAIL event description.
Action:
No action is required.
Reason:
Response from the ENF MSGEVENT operator command.
The starting column number of the job name in the intercepted message, or zero if the originating job name is used.
The starting column number of the job number in the intercepted message, or zero if the originating job number is used.
Action:
No action is required.
Reason:
One or more CAS9291I messages immediately follow message CAS9307W, showing the ID of applications that have not responded in a timely manner, indicating a possible stalled condition.
The ID consists of the application's JES-assigned job name/number and internal listener name.
Action:
See the action to be taken in message CAS9307W.
Reason:
Health Checker function xxxx failed. The return code from the function and the reason code provide details about the failure.
Action:
Save all dumps and other diagnostics and contract CA Support for assistance.
Reason:
This informational message reports the number of ENF Health Check monitors that successfully registered with the HealthChecker.
Action:
If the number of Health Check monitors is not equal to the total number of monitors, look for any CAS9292E messages to determine why some of the monitors did not successfully register. If the numbers are equal, there is no need for any additional action.
Reason:
An abend has occurred within a CAIENF address space subtask. The variable field displays the abend code.
Action:
See accompanying messages for more detailed description of the error. Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
An abend has occurred within a CAIENF address space subtask. The variable fields are defined as follows, respective to the order displayed:
Action:
See accompanying messages for a more detailed description of the error. Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
An abend has occurred within a CAIENF address space subtask. The variable fields indicate Registers 0 through 3 at the time of error.
Action:
See accompanying messages for a more detailed description of the error. Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
An abend has occurred within a CAIENF address space subtask. The variable fields indicate Registers 4 through 7 at the time of error.
Action:
See accompanying messages for a more detailed description of the error. Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
An abend has occurred within a CAIENF address space subtask. The variable fields indicate Registers 8 through 11 at the time of error.
Action:
See accompanying messages for a more detailed description of the error. Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
An abend has occurred within a CAIENF address space subtask. The variable fields indicate Registers 12 through 15 at the time of error.
Action:
See accompanying messages for a more detailed description of the error. Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
CAIENF has been shut down or a critical error has forced termination of the CAIENF address space. CAIENF services are no longer available to products that may require them.
Action:
If not in response to a shutdown request, restart CAIENF.
Reason:
A database error has occurred that prevents CAIENF from logging data. CAIENF buffers data within its address space and periodically retries the request.
Action:
Correct the database problem. If not possible, enter the ENF RECORD(NO) operator command to free buffered data and prevent further database access.
Note: ENF RECORD(NO) prevents the recovery of events that occur after this command is issued.
Reason:
A reminder that CAIENF has encountered a database error and is buffering data. CAIENF issues this message following CAS9301E after the internal queue reaches 500 entries.
Action:
Correct the database problem. If not possible, enter the ENF RECORD(NO) operator command to free buffered data and prevent further database access.
Reason:
A database error has occurred that prevents CAIENF from logging data for a specific event. The event has been altered to NORECORD.
Action:
Correct the database problem by referring to messages CAS9207E, CAS9208E, or CAS9209E, which should accompany the CAS9303E message.
Reason:
This message is comprised of one or more lines of follow-up help text that may be posted to the ENF message log by various ENF components following detection of certain error conditions. Help messages are designed to assist users in quickly identifying and resolving error conditions that may simply be due to inappropriate user specifications or configuration parameters.
Identifies the originating error message number (ID) that usually precedes the corresponding help message.
Identifies the problem in more detail and may provide additional problem-resolution data and recommend corrective action. Includes up to 40 characters of text per line.
Action:
The originating error message number (ID) or the help message may suggest a course of action.
Reason:
A FREEMAIN macro for CSA has failed. Storage at the address length and subpool given is not freed.
Action:
If the problem persists, contact CA Support.
Reason:
A FREEMAIN macro for storage within the CAIENF address space has failed. Storage at the address length and subpool given is not freed.
Action:
If the problem persists, contact CA Support.
Reason:
One or more CAIENF applications have events queued to them, and the elapsed time since the application last listened for events is approaching the MAXQTIME limit, indicating the application may be stalled. If the application does not listen for events before the elapsed time exceeds the MAXQTIME limit, the application will be disabled if MAXQTIME is set in DISABLE mode, otherwise just an SVCDUMP is taken.
This message is followed by one or more instances of message CAS9291I, which display the ID of the possibly stalled application/listener.
Action:
Use the ENF APPL operator command to identify the applications with events queued to them and elapsed time approaching the MAXQTIME limit. Ensure the applications are functioning properly. Use the ENF STATUS operator command to review the MAXQTIME setting. If necessary, use the ENF MAXQTIME control option to change the MAXQTIME setting.
Reason:
Invalid characters were detected in a DCM configuration statement.
Identifies the field name in error.
Specifies the actual value from the configuration statement.
Action:
CAS9DCM processing terminates. Report this error to your ENF administrator.
Reason:
The did data set identified by ddname could not be opened. did is the data set ID. The most likely cause is a missing DD statement.
Action:
ENF startup terminates. Report this error to your ENF administrator.
Reason:
This is an error. The DCM object name was omitted from the DCM command or statement.
Action:
CAS9DCM processing terminates for the current DCM command or statement.
Reason:
DCM object objname is a duplicate of a previously stowed object.
Action:
This message is informational only. The duplicate DCM is ignored.
Reason:
DCM object objname could not be loaded into storage.
The z/OS LOAD request return and reason codes.
Action:
CAS9DCM processing terminates for the current DCM. See LOAD macro errors in the z/OS Assembler Services Reference for an explanation of the error return/reason codes. This error should be reported to your ENF administrator.
Reason:
DCM object objname failed CAS9DCM integrity checking.
Action:
CAS9DCM processing terminates. This error should be reported to your ENF administrator.
Reason:
Processing of the current DCM statement completed in error. Error details can be found immediately preceding this message.
Action:
CAS9DCM processing terminates. Report this error to your ENF administrator.
Reason:
DCMs are required for ENF.
Action:
This is an error; the ENF-started task terminates.
Reason:
DBC request failed.
A four-byte string identifying the DBC component that issued the request. All SQL return codes are negative and are preceded by a minus sign.
The failing return code.
Depending on the request, this is either a DBC reason code or SQL error qualifying code.
Action:
Depending on the issuing component and severity of the error, ENF processing may terminate or an attempt may be made to recover from the error. See the CA Datacom®/DB Message Guide for an explanation of error return and reason codes. This error should be reported to your ENF administrator.
Reason:
A DCM statement was detected in the wrong ENF startup data set or there was an attempt to process a DCM command through the ENF command processor. DCM statements are permitted in the ENFPARMS data set only. Entering DCM statements through the ENF command processor is not allowed.
Action:
This is an error. The DCM command or statement is ignored.
Reason:
DBC initialization exceeded the maximum allowable time of one minute.
Action:
CAS9MNGR processing abnormally terminates with a U205 abend. Report this error to your ENF administrator.
Reason:
DCM configuration processing detected a duplicate element in a DCM load module.
Either “data” or “event.”
The data or event name.
The name of the DCM load module where the duplicate element was found.
Action:
This message is informational only. The duplicate element is discarded and processing continues. Report this condition to your ENF administrator.
DCM configuration processing detected a conflict (mismatch) between an attribute in a DCM object event and its counterpart in the database.
A string identifying the unmatched attribute.
For example, attrid might contain the string "#columns" to indicate the number of columns (data items) found in the DCM did not match the number of columns found in the database.
The name of the event.
This is an error. Recording for eventname is disabled. This message is followed by either message CAS9328W or CAS9329E. Report this condition to your ENF administrator.
Reason:
As a result of an error in an ENF task, program call routine, or SRB routine, a symptom dump is being captured for the task shown in the message.
Action:
Review the system log for other messages regarding the cause of the failure. Search the problem reporting databases for a fix for the problem. If the problem is unable to be resolved, contact CA Support.
Reason:
This message is part of the symptom dump resulting from an error in an ENF task and identifies the ABEND completion code and reason code.
Action:
No action is required.
Reason:
This message is part of the symptom dump resulting from an error in an ENF task and identifies the following:
Action:
No action is required.
Reason:
This message is part of the symptom dump resulting from an error in an ENF task and identifies the following:
Action:
No action is required.
Reason:
This message is part of the symptom dump resulting from an error in an ENF task. It identifies the PSW next sequential address minus 6, and the contents of the three full words beginning at that address.
Action:
No action is required.
Reason:
This message is part of the symptom dump resulting from an error in an ENF task. It indicates that the virtual storage at the PSW next sequential instruction address is either unavailable at this time (unallocated) or is inaccessible by the task in error.
Action:
No action is required.
Reason:
This message is part of the symptom dump resulting from an error in an ENF task. It identifies the contents of the access registers and general purpose registers at the time of the error.
Action:
No action is required.
Reason:
This is a follow-on message to a previous error message.
Action:
This is a warning message. The recording for inactive event eventname is disabled. Report this condition to your ENF administrator.
Reason:
This is a follow-on message to a previous error message.
Action:
This is a warning message. The recording for active event eventname has been disabled. Report this condition to your ENF administrator.
Reason:
DCM configuration processing detected an erroneous attribute in a DCM object.
A string identifying the attribute in error.
For example, attrid might specify datalen to indicate the length of the attribute exceeded the maximum allowed for the attribute type.
The name of the event.
The name of the data element in the event.
Action
This is an error message. Recording for eventname is disabled. This message is followed by either message CAS9328W or CAS9329E. Report this condition to your ENF administrator.
Reason:
An SVC dump was captured for the task shown in the message a result of the following:
Action:
No action is required.
Reason:
An attempt was made to capture an SVC dump for the task shown in the message as a result of the following:
However, the SVC dump was suppressed by the MVS component shown in the message. The MVS component is one of the following:
Action:
No action is required.
Reason:
An attempt was made to capture an SVC dump for the task shown in the message as a result of the following:
However, the attempt failed with the return code and reason code identified in the message.
Action:
Review the system log for other messages regarding the cause of the failure. Search the problem-reporting databases for a solution to the problem. If the problem is unable to be resolved, contact CA Support.
Reason:
DCM configuration processing detected a conflict (mismatch) between an attribute in a DCM object event and its counterpart in the database. This error message reports the same condition as that in message CAS9320E, except that this message also includes the name of the attribute.
A string identifying the unmatched attribute.
For example, attrid might specify datatype to indicate that the datatype of a particular column found in the DCM did not match the datatype of its corresponding entry in the database.
The name of the event.
The name of the attribute in error.
Action:
The recording for eventname is disabled. This message is followed by either message CAS9328W or CAS9329E. Report this condition to your ENF administrator.
Reason:
New event eventname from a DCM object has been successfully stowed in the database.
Action:
This message is informational only. No action is required.
Reason:
This is a follow-on message to a previous error condition.
Action:
Check the log for error message details immediately preceding this message.
Reason:
The DBC application programming interface has been successful initialized.
Action:
This is an informational message. No action is required.
Reason:
ENF has received and acknowledged a request to terminate the DBC application programming interface.
Action:
This message is informational only. No action is required.
Reason:
Event eventname from a DCM object has been successfully verified against its counterpart in the database.
Action:
This is an informational message. No action is required.
Reason:
This message is used to report error messages formatted and returned by Datacom and the SQL interface.
Action:
Look in the Datacom Messages Guide for more information about this message.
command cannot be processed at this time. Reason=rr.
ENF operator command command could not be processed for the following (rr) reason:
A “start-up only” command was issued after ENF completed initialization.
A command was issued in an improper environment (for example, an IMUFCMD command was issued when not in IMUF mode), or the command receiver was busy and momentarily could not accept the request.
The command is not processed and ENF processing continues. The reason may be a temporary condition.
Action
If rr is 02, try reissuing the command. If the error persists, report this condition to your ENF administrator.
Reason:
A database archive (backup) request was received, but database operations are not currently active.
Action:
The archive or backup request is discarded.
Reason:
Message CAS9347I displayed unnumbered status messages generated by the ENF database archiver. The archiver is invoked whenever an automatic archiving cycle has been triggered, or an ENF ARCHIVE command has been received.
Action:
This message is informational only. No action is required.
Reason:
The index parameter in the EDCM definition for the event in the DCM object does not contain all the required fields. At a minimum the index parameter in each EDCM must contain the elements DATEL, TIME, SYSNAME, and ENFUNIQ.
The name of the event.
The name of the attribute in error.
Action:
The recording for eventname is disabled. This message is followed by either message CAS9328W or CAS9329E. Report this condition to your ENF administrator.
Reason:
The database control task (DBC) is severing the connection to the database server (Datacom) and temporarily shutting down due to the indicated reason.
The reason for the shut down.
Action:
At 5-minute intervals, ENF attempts to establish the connection with the database server again. If the connect attempt fails, the database server remains in drain mode and message CAS9316E is posted to the ENF message log indicating a connect failure. When the reconnect attempt succeeds, the DBC will be restarted and normal ENF database operations are restored.
Reason:
The CAIENF database archive has been triggered to begin at the date/timestamp indicated by yyyydddhhmmssth.
Action:
No action is required.
Reason:
The CAIENF automatic database archive has completed. The message contains the total number of records archived.
Action:
No action is required.
Reason:
The CAIENF automatic database archive has encountered an I/O error while writing an archive data set.
Action:
No action is required.
Reason:
The CAIENF checkpoint and recovery routine has encountered an error. Checkpoint and recovery processing is no longer available to CAIENF applications.
Action:
No action is required.
Reason:
The CAIENF automatic database archive has completed processing for the named event. nnnnnn contains the total number of records written.
Action:
No action is required.
Reason:
CAIENF has determined there were no records available that met the archive criteria. Other events that may have been available were defined beyond the retention period or designated for purge.
Action:
No action is required.
Reason:
The CAIENF database archive can only execute once a day if ARCHIVE(AUTO) is specified.
Action:
If there is expired event data on the CAIENF database following the issuance of this message, perform one of the following:
If this message is repeatedly issued to the console and there is no expired event data available for archive, it may be necessary to allocate a larger CAIENF database.
Reason:
CAIENF logging has detected an internal problem in the database subtask and is in the process of canceling the current database subtask.
Action:
No action is required.
Reason:
Review message CAS9358E, which indicates database subtask termination. If the database subtask is not available within five minutes after the reinitialization attempt begins, this message is displayed.
Action:
Shut down ENF and restart the service.
Reason:
The CAIENF automatic database archive cannot retrieve the data it needs due to a database error.
Action:
Ensure that the database defined to the archive routine exists and has been correctly initialized (see the Administration Guide for more information on listing the contents of a database).
Reason:
The CAIENF automatic database archive cannot allocate or open the archive file. Archive processing is terminated.
Action:
If using a dynamically allocated archive file, ensure that the parameters specified for DSN, UNIT, SPACE, LABEL, and CATALOG are correct (see message CAS9362E). If using a pre-allocated file, verify the allocation parameters for the data set.
Reason:
CAIENF has encountered a dynamic allocation error.
Action:
Check for one of the following conditions and take action as needed:
Reason:
The global modules identified by the message variable are being refreshed to apply or remove maintenance.
Action:
No action is required.
Reason:
The load library identified by the message variable is being refreshed.
Action:
No action is required.
Reason:
The modules contained in the linklisted STEPLIB are being refreshed.
Action:
No action is required.
Reason:
The query for the database’s current capacity failed. Whether or not to archive cannot be determined.
Action:
See message CAS9316E for more information concerning the failure.
Reason:
An error has occurred during processing of the command defined by the message variable.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
The command just issued is invalid because CAIENF has already been initialized.
Action:
Reissue the command during CAIENF initialization.
Reason:
CAIENF has determined that a database backup is required for the JOB in question, where xxxxxxxx is the job name or job number associated with the active database.
Action:
If ENF ARCHIVE is set to AUTO, no action is required. CAIENF initiates the backup process. If the AUTO backup has already run today, as indicated by message CAS9357W and there is expired event data on the CAIENF, force an unscheduled backup through the ENF ARCHIVE operator command, ENF ARCHIVE(NOW), or execute the archive utility through a batch job.
If ENF ARCHIVE is set to a user-defined time interval, then do one of the following:
If this message is repeatedly issued to the console, and there is no expired event data available for archiving, it may be necessary to allocate a larger CAIENF database.
Reason:
The database is full.
Action:
Use the ENF PURGE(event_name) operator command to clear the database. You should only purge event data that is not critical to the running of your CA solutions. If purging event data is unsuccessful, the current CAIENF database must be deleted. Allocate and initialize a new CAIENF database.
Reason:
The space allocation for a CAIENF database that the batch utility is currently executing against is too small.
Action:
Scratch and reallocate the CAIENF database with a larger space allocation.
Reason:
The CAIENF database has completed purging the named event. nnnnnn contains the total number of records deleted.
Action:
No action is required.
Reason:
The archive process is either starting now (auto-archive) or is scheduled to start at HH:MM.
Action:
No action required.
Reason:
You have requested that the CAIENF AUTOCMDS be reissued during a CAEINF manual start.
Action:
No action is required.
Reason:
CAIENF has encountered a database error while logging event xxxxxxxx. CAIENF is in the process of recovering as much of the old event data as possible before internally issuing a PURGE for the old event data. CAIENF then recreates the event.
Action:
No action is required. This message is informational only.
Reason:
This message indicates the date and time range for events that CAIENF could not recover.
Action:
No action is required.
Reason:
A database error was encountered during CAIENF checkpoint processing. CAIENF cannot read data for event xxxxxxxx after date yyddd and time hhmmssth.
Action:
No action is required.
Reason:
An error occurred when CAIENF was accessing a structure defined in the Coupling Facility. The message will contain information that will help CA Support diagnose the problem. This message is usually issued with message CAS9380E.
Action:
Recycle CAIENF. For assistance, contact CA Support at http://ca.com/support.
Note: When calling CA Support, be sure you have the job log from the CAIENF STC.
Reason:
An error occurred when CAIENF was accessing a structure defined in the Coupling Facility. The message will contain information that will help CA Support diagnose the problem. This message is usually issued with message CAS9379E.
Action:
Recycle CAIENF. For assistance, contact CA Support at http://ca.com/support.
Note: When calling CA Support, be sure you have the job log from the CAIENF STC.
Reason:
Output from the ENF STATUS operator command. The variable fields are defined as follows, respective to the order displayed:
Action:
No action is required.
Reason:
CAIFLOID has found an invalid forward pointer in the LMP product table. The most likely cause of this is a CSA storage overlay.
Action:
IPL the system to correct the problem or contact Level 1 support to obtain the procedure to locate the overlay and delete the contents of CSA storage manually, and rerun the CAS9-started task.
Reason:
The ENFCT command (operator or configuration file) was unable to detect the necessary environment to initialize component tracing.
Action:
Verify that ENF initialization successfully completed.
Reason:
The ENFCT command (operator or configuration file) detected that it has already run.
Action:
No action is required.
Reason:
The return code and reason code will identify the specific error.
Action:
Record the return code and reason code.
Reason:
The archive process is being automatically started because the database was determined to be full.
Action:
No action required.
Reason:
ENF maintains a catalog of Archives for the purpose of restoring ENF events. The catalog table table_name designates the missing database table. The Restore command terminates.
Action:
Contact CA Support for instructions.
Reason:
Processing of all CAS9DUTL commands have completed.
The number of errors encountered.
Action:
Review prior messages for identification and explanation of any possible errors. Correct the problems and rerun the batch job.
Reason:
A request to the database failed.
The request error text provided by the database.
Action:
Contact CA Support for instructions.
Reason:
Message displays a CAS9DUTL command as specified in the CAS9DUTL DUTLIN DD command input file.
The input file record number and command statement are displayed.
Action:
This message is informational only.
Reason:
The number of input statements for CAS9DUTL DUTLIN DD exceeded the maximum 999 allowed.
Action:
Decrease the number of statements containing CAS9DUTL commands or separate the statements into multiple batch submissions.
Reason:
The CAS9DUTL Restore command specific dates for events there were not found in any archive.
Action:
Review the dates for the event specified, correct dates if in error, and rerun the batch job.
Reason:
An Open error occurred with CAS9DUTL ddname DD
Action:
Review the batch job log for z/OS error messages for the specified DD to determine the appropriate action.
Reason:
A problem was identified with a command statement. The statement number, the command, and the specific type of error are displayed.
Action:
Correct the command error for the statement identified and rerun the CAS9DUTL batch job.
Reason:
An error was identified with a keyword in a command statement. The statement number, the command, the keyword, and the specific type of error are displayed.
Action:
Correct the command keyword error for the statement identified and rerun the CAS9DUTL batch job.
Reason:
A syntax error was encountered with a command statement. The number of the statement displays. A CAS9390I message immediate follows with the contents of the command statement encountering the error.
Action:
Correct the syntax of the command statement in error and rerun the CAS9DUTL batch job.
Reason:
The event archive contains data types that do not match the current definition of the event as defined in the database.
Action:
Contact CA Support.
Reason:
A CAS9DUTL command statement contained an invalid parameter for the identified keyword.
Action:
Correct the keyword parameter and rerun the CAS9DUTL batch job.
Reason:
The archive data set encountered a file error. The z/OS I/O error message text is displayed.
Action:
Review the message error text and the job log for additional I/O error messages, correct the problem if possible, and rerun the job.
Reason:
An error was encountered during the Archive/Purge process which caused changes such as deletions made to the database event tables to be backed out.
Action:
Correct the reason for the rollback and restart the Archive/Purge process by entering the ARCHIVE(NOW) command.
Reason:
The Archive/Purge process abnormally terminated due to a rollback. The archive data set created during the process is incomplete.
Action:
Correct the reason for the rollback and restart the Archive/Purge process by entering the ARCHIVE(NOW) command.
Reason:
The archive data set could not be allocated.
Action:
Review your site’s CAIENF control options as well as the resources used to allocate the data set. Correct the reason for the failure and restart the Archive/Purge process by entering the ARCHIVE(NOW) command.
Reason:
The archive data set could not be closed.
Action:
Review your site’s CAIENF control options as well as the resources used to allocate the data set. Correct the reason for the failure and restart the Archive/Purge process by entering the ARCHIVE(NOW) command.
This is an informational message indicating the EOV has been reached while archiving CAIENF event data. Since the archive process does not currently support multiple volumes, a rollback is performed.
Action:
Change the archive data set SPACE allocation information and re-initialize the archive process.
If this condition occurs frequently, consider changing the retention period for your events, so that events are archived more frequently or at different intervals.
Reason:
This is an informational message indicating there is no event xxxxxxxx recorded in the CA Datacom database eligible for archiving or backup.
Action:
None.
This is an informational message indicating the event records for the event indicated by eventname will be archived and purged based upon the date indicated.
Action:
NONE
This is an informational message indicating that the Archive/Purge process is terminating because the process detected a CAIENF or Database shutdown.
Action:
Determine the reason for the process termination. Restart CAIENF and/or the Database and restart the Archive/Purge process by entering the ARCHIVE(NOW) command.
Reason:
An ENF ARCHIVE operation has terminated in error.
Action:
This is a non-deletable operator action message. It is immediately followed by message CAS9409E.
Reason:
This is a follow-on message to CAS9408E.
Action:
Forward the error message information posted by the failed ARCHIVE operation to ENF CA Support.
This is an informational message indicating that Archive data created on a certain date and time is being automatically purge from the archive tables due to an expiration date of the associated data set. For more information, see Message CAS9411I.
Action:
No action required.
This is an informational message indicating that the Archive data set has expired and that information relating to the Archive has been removed from the archive tables. For more information, see Message CAS9410I.
Action:
No action required.
Reason:
A MAXQTIME violation has occurred for the listener. ENF is operating in MAXQTIME "warn" mode. The listener’s oldest event exceeds the maximum allowable time on the queue.
Action:
Determine the reason for the listener’s failure to process the events.
Reason:
An error occurred during ASASYMBM’s processing of the data set name. The return code is documented in the IBM z/OS MVS Assembler Services Reference for ASASYMBM.
The DSNAME command is aborted. The previous or default value for DSNAME is not altered.
Action:
Take the corrective action specified for the return code in the IBM documentation or contact CA Technical Support.
Reason:
After substitutions, the length of the string resulting from ASASYMBM’s processing is zero.
The DSNAME command is aborted. The previous or default value for DSNAME is not altered.
Action:
Modify the DSNAME command to correct the problem and resubmit it.
Reason:
After substitutions, the length of the string resulting from ASASYMBM’s processing is greater than 44 characters.
The DSNAME command is aborted. The previous or default value for DSNAME is not altered.
Action:
Modify the DSNAME command to correct the problem and resubmit it.
Reason:
After substitutions, the string resulting from ASASYMBM’s processing still contains an “&”.
The DSNAME command is aborted. The previous or default value for DSNAME is not altered.
Action:
Modify the DSNAME command to correct the problem and resubmit it.
Reason:
The LINK to ASASYMBM failed. The first part of the error code (xxxxxxxx) is the abend reason code and the second part of the error code (yyyyyyyy) contain the abend code for the failure.
The DSNAME command is aborted. The previous or default value for DSNAME is not altered.
Action:
Research the IBM documentation for the reason code and the abend code then take the corrective action or contact CA Technical Support.
Reason:
An ABEND has occurred during ASASYMBM’s processing.
The DSNAME command is aborted. The previous or default value for DSNAME is not altered.
Action:
Research the IBM documentation for the cause and solution of the ABEND, then take the corrective action or contact CA Technical Support.
Reason:
A listener with job name, job number and listener name has requested a checkpoint recovery for the date specified.
Action:
No action is required.
Reason:
The checkpoint recovery request for the listener with job name, job number and listener name is waiting for the database to be updated before it can start the recovery process.
Action:
No action is required.
Reason:
The checkpoint recovery request for the listener with job name, job number, and listener name is resuming after the database updates have completed.
Action:
No action is required.
Reason:
The checkpoint recovery request for the listener with job name, job number, and listener name has encountered an error. The checkpoint recovery request is terminating.
Action:
Determine the reason for the failure and re-issue the recoveryrequest.
Reason:
The checkpoint recovery request for the listener with job name, job number, and listener name found not events to recover.
Action:
No action is required.
Reason:
CAIENF/CICS interface is being initialized.
Action:
No action is required.
Reason:
CAIENF/CICS interface initialization is complete.
Action:
No action is required.
Reason:
CAIENF/CICS interface is terminating.
Action:
If this message appears at startup, check prior messages to determine why CAIENF/CICS is terminating.
Note: This is a normal message when terminating CAIENF.
Reason:
When starting the CAIENF/CICS interface as a separate PROC outside the CAIENF address space, it was determined that CAIENF was not active.
Action:
Start CAIENF and restart CASCCICS.
Reason:
CAIENF/CICS issued an event macro. The return code specified that a logic error had occurred.
Action:
Check prior messages. For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS has detected that CAIENF has abended.
Action:
Restart CAIENF.
Reason:
An event needed by the CAIENF/CICS interface has not been defined in the CAIENF database.
Action:
Ensure CAS9DCM2 has been run. For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS issued an event macro. The return code that specified 'Events Exceed Maximum' was returned.
Action:
Check prior messages. For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS issued an event macro. The return code specified no data available.
Action:
Check prior messages. For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS issued an event macro. The return code specified a listen error.
Action:
Check prior messages. For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS issued an event macro. The return code specified that the token address is invalid.
Action:
Check prior messages. For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS issued an event macro. The return code specified was undefined.
Action:
Check prior messages. For assistance, contact CA Support at http://ca.com/support.
Reason:
A nonzero return code was returned when attaching the Command Processor.
Action:
Try recycling CAIENF. If the same message returns, CAIENF/CICS code runs, but you will not be able to issue commands.
Reason:
When a CICS region starts up, a CICSINIT event is issued. If the Concerto subtask is active, a separate utility TCB is attached for each CICS region.
Action:
No action is required.
Reason:
One of the subtasks issued a GETMAIN with a bad return code.
Action:
No action is required.
Reason:
CAIENF/CICS is in the process of recovering.
Action:
No action is required.
Reason:
A nonzero return code was returned when establishing the recovery environment.
Action:
CAIENF/CICS code runs, but is not able to recover when a problem occurs.
Reason:
Not enough CSA to GETMAIN the CAIENF/CICS control block.
Action:
Try again later.
Reason:
A CICS region, which had an attached utility TCB running in the CAIENF address space, has ended. This message indicates that CAIENF has captured the ENFTERM event.
Action:
No action is required.
Reason:
CAIENF/CICS has received an ENFTERM event.
Action:
No action is required.
Reason:
A user has stopped the CAIENF address space. The CAIENF CICS code is detaching any active subtasks to avoid SA03 abends.
Action:
No action is required.
Reason:
A user has stopped the CAIENF address space. CAIENF is waiting for all CICS utility TCBs to deactivate.
Action:
No action is required.
Reason:
The main CICS TCB has captured the ENFTERM event. CAIENF is checking the status of any attached utility TCBs.
Action:
No action is required.
Reason:
CAIENF/CICS has been restarted.
Action:
No action is required.
Reason:
CAIENF/CICS subtask was previously attached and activated. Request is ignored.
Action:
No action is required.
Reason:
Tried to attach the CAIENF/CICS subtask, but CAIENF was not active.
Action:
Start CAIENF.
Reason:
CAIENF/CICS SPAWN has begun its initialization process into the CICS region. Message issued by module CASSPxxZ, where xx is the CICS release.
Action:
No action is required.
Reason:
CAIENF/CICS SPAWN has completed the allocation of its working storage area. Message issued by module CASSPxxZ, where xx is the CICS release.
Action:
No action is required.
Reason:
CAIENF/CICS SPAWN has completed the allocation of its working storage area. Message issued by module CASSPxxZ, where xx is the CICS release.
Action:
No action is required.
Reason:
CAIENF/CICS SPAWN has begun allocating the CICS User Exit Table (UET). Message issued by module CASS0xxZ, where xx is the CICS release.
Action:
No action is required.
Reason:
CAIENF/CICS SPAWN has attached it CICS TCA. Message issued by module CASSPxxZ, where xx is the CICS release.
Action:
No action is required.
Reason:
CAIENF/CICS SPAWN has notified CAICCI that it is ready for work. Message issued by module CASSPxxZ, where xx is the CICS release.
Action:
No action is required.
Reason:
CAIENF/CICS SPAWN has completed its initialization process. It is now ready for work. Message issued by module CASSPxxZ, where xx is the CICS release.
Action:
No action is required.
Reason:
CAIENF/CICS SPAWN has installed its TRUE intercept. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
No action is required.
Reason:
CAIENF/CICS SPAWN has notified CAICCI that the service call was successful. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
No action is required.
CAIENF/CICS SPAWN has detected an error and has notified CAICCI of the error. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN could not locate the SPAWNKEY. Message issued by module CASSPxxA, where xx is the CICS RELEASE.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN GETMAIN for EIS/EIB storage has failed. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN GETMAIN for USER storage has failed. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN has gotten a nonzero return from CAICCI services. The task was suspended for five seconds, and the CAICCI RECEIVE command was retried ten times and still failed. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN could not locate the SPAWN FMH data. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN could not locate CAICCI FMH. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN located an invalid FMH type. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN found an error in the SPAWN control statement for the specified SUBTYPE. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN attached another task to wait once more for SPAWN requests, but the attach TCA failed. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN could not locate a transaction ID within the SPAWN PROCESS statement. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
Check the syntax on the PROCESS statement. It should contain the TRAN_ID value.
Reason:
CAIENF/CICS SPAWN attempted to spawn the transaction and CICS notified you that the transaction was disabled. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
Investigate why the specified transaction is disabled within the CICS region.
Reason:
CAIENF/CICS SPAWN could not locate the program specified. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
Specified program name needs to be defined to CICS.
Reason:
CAIENF/CICS SPAWN attempted to spawn the transaction and CICS notified you that the program was disabled. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
Investigate why the specified transaction is disabled within the CICS region.
Reason:
CAIENF/CICS SPAWN received a nonzero return code from CICS for the specified terminal. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
The EIBRESP2 value represents the CICS response 2 code. Refer to the IBM Application Programming Reference for an explanation of the codes.
Reason:
CAIENF/CICS is attaching the Command Processor.
Action:
No action is required.
Reason:
CAIENF/CICS Command Processor is inactive.
Action:
Try recycling CAIENF. If the same message returns, CAIENF/CICS code runs, but you will not be able to issue commands.
Reason:
The CAIENF/CICS Command Processor received an invalid command.
Action:
Correct the syntax and reissue the command.
Reason:
The CAIENF/CICS Command Processor received an invalid command.
Action:
Correct the syntax and reissue the command.
Reason:
CAIENF/CICS is attaching the Command Processor.
Action:
No action is required.
Reason:
A CAIENF CICS command (START/STOP/REFRESH,JOBNAME) was issued and the job is not known to CAIENF/CICS.
Action:
Correct JOBNAME and reissue the command.
Reason:
A user has issued an ENF CICS(STOP,xxxxxxxx) command, and CAIENF was not active in the region at the time.
Action:
No action is required.
Reason:
A user has issued an ENF CICS(STOP,xxxxxxxx) or ENF CICS(START,xxxxxxxx) command, and the CAIENF Command Processor has found that the address space is terminating.
Action:
No action is required.
Reason:
A CAIENF/CICS command (START/STOP/REFRESH,JOBNAME) was issued and CAIENF/CICS is already in that status.
Action:
Wait until the previous command has finished processing before issuing another command.
Reason:
A user has issued an ENF CICS(STOP,xxxxxxxx) or ENF CICS(START,xxxxxxxx) command to stop or start a CA solution.
Action:
No action is required.
Reason:
CAIENF/CICS has started and is not establishing its intercepts in all CICS regions.
Action:
No action is required.
Reason:
When setting up a cross memory environment, an invalid ASCB was encountered.
Action:
Take an SVCD of the job. For assistance, contact CA Support at http://ca.com/support.
Reason:
Major CAIENF control block could not be located.
Action:
Take an SVCD of the job. For assistance, contact CA Support at http://ca.com/support.
Reason:
When setting up a cross memory environment, an error was encountered.
Action:
Take an SVCD of the job. For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS was asked to start or stop in an address space that is not a CICS region. Three reasons can cause this to happen:
Action:
Perform one of the following (respective to the appropriate reason presented above):
Reason:
CAIENF/CICS was asked to start or stop in an address space that is not a supported CICS release.
Action:
No action is required.
CAIENF/CICS was trying to install intercepts and the modules could not be located.
Action:
Install CAIENF/CICS modules in CSA, CENFLIB, or STEPLIB.
Reason:
The STARTCCP command for started-task-name (xxxxxxxx) did not complete successfully for one of the following reasons (yy):.
The command was issued as part of ENFPARMS. It can only be used after ENF is started.
The started-task-name is currently active.
The started-task-name is missing from the command.
The started-task-name is an unknown service name.
The MVS START command that STARTCCP issued has failed.
The second operand of the STARTCCP command is not FORCE.
Action:
Take whatever action is appropriate for the supplied reason code. For reason code 7, contact CA Support.
Reason:
As requested by the STARTCCP command, started-task-name (xxxxxxxx) has been successfully started.
Action:
No action required – informational message only.
Reason:
A CAIENF CICS command (START/STOP,JOBNAME,xxxx) was issued and the CA product is not known to CAIENF.
Action:
Install product xxxxDCM2 in CAIENF database and recycle CAIENF.
Reason:
A user has issued an ENF CICS(STOP) command in an attempt to stop a CA solution. This solution is defined to the CAIENF database as unstoppable through this command.
Action:
No action is required.
Reason:
A user has issued an ENF CICS(START) command in an attempt to start a CA solution. This solution is defined to the CAIENF database as nonstartable through this command.
Action:
No action is required.
Reason:
A CAIENF/CICS command (START,JOBNAME,xxxx) was issued and the CA product is already started.
Action:
No action is required.
Reason:
A user has issued an ENF CICS(STOP) command in an attempt to stop a CA solution, and the solution is not installed in the region.
Action:
No action is required.
Reason:
A user has issued an ENF CICS(STOP) command in an attempt to stop a CA solution. The solution was not active in the region at the time.
Action:
No action is required.
Reason:
A user has successfully stopped a CA solution through an ENF CICS(STOP) command.
Action:
No action is required.
Reason:
To stop a CA solution running in any of the CICS regions, a user issued an ENF CICS(STOP) command to all CICS regions known to CAIENF. This message reports the number of CICS regions in which the product was stopped.
Action:
No action is required.
Reason:
An abend has occurred while a CA solution was in control at a CAIENF/CICS intercept point. The variable fields are defined as follows, respective to the order displayed:
Action:
See accompanying messages for more detailed descriptions of error. Save all dumps and other diagnostics for CA Support assistance. Contact the product's technical assistance group.
Reason:
A DCM has been added to the CAIENF/CICS database, but the CA solution initialization program was not found during CAIENF startup.
Action:
Complete the CA solution installation by adding the library containing the CA product initialization program to CAIENF's STEPLIB or add the library to the linklist.
Reason:
CAIENF/CICS SPAWN received a nonzero return code from CICS for the specified net name. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
The EIBRESP2 value represents the CICS response 2 code. Refer to the IBM Application Programming Reference for an explanation of the codes.
Reason:
CAIENF/CICS SPAWN could not dynamically install the specified terminal. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN received a nonzero return code from CICS. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
The EIBRESP2 value represents the CICS response 1 code. Refer to IBM's Application Programming Reference for an explanation of the codes.
Reason:
CAIENF/CICS SPAWN could not dynamically define the requested transaction ID. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN received a nonzero return code from CICS. The EIBRCODE value represents the CICS response code. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
Refer to IBM's Application Programming Reference for an explanation of the codes.
Reason:
CAIENF/CICS SPAWN received a nonzero return code from the CICS CEMT command due to a translation error. The translation value represents the CICS response code (EIBRCODE). Message issued by module CASSPxxA, where xx is the CICS release.
Action:
Refer to the IBM Application Programming Reference for an explanation of the codes.
Reason:
CAIENF/CICS SPAWN received a nonzero return code from the CICS CEMT command due to an execution error. The execution value represents the CICS response code (EIBRCODE). Message issued by module CASSPxxA, where xx is the CICS release.
Action:
Refer to the IBM Application Programming Reference for an explanation of the codes.
Reason:
CAIENF/CICS SPAWN received a nonzero return code from CICS; however, the return code was outside the range of expected error codes. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN could not locate the required SPAWN PROCESS statement within the FMH data stream. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
Add the PROCESS statement to your SPAWN control statements. If one is present, check the syntax.
Reason:
CAIENF/CICS SPAWN found an error in the syntax of the RESOURCE statement within the FMH data stream. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN found an error in the syntax of the TIME statement within the FMH data stream. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN has exceeded its capacity within the services table. Message issued by module CASSPxx1, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN could not locate this entry on the services table. Message issued by module CASSPxx2, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN is processing the CEMT CANCEL command. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
No action is required.
Reason:
CAIENF/CICS SPAWN has already found an ENF TRUE intercept; it does not need to install a SPAWN TRUE. Message issued by module CASSPxx1, where xx is the CICS release.
Action:
No action is required.
Reason:
The CAIENF/CICS Status Table is full and the current CICS being initialized cannot be added to the table. The table limit is 80 entries.
Action:
Bring down another CICS and try to initialize the previous CICS again. For assistance, contact CA Support at http://ca.com/support.
Reason:
CAIENF/CICS SPAWN could not locate the work queue for this spawn request. Message issued by module CASSPxxA, where xx is the CICS release.
Action:
No action required.
Reason:
CAIENF/CICS SPAWN could not locate the CA Common Services for z/OS LCA module. SPAWN initialization failed. Message issued by module CASSPxxZ, where xx is the CICS release.
Action:
For assistance, contact CA Support at http://ca.com/support.
Reason:
Output from the ENF STATUS operator command. The variable field is defined as the status of the CAIENF/CICS SPAWN service.
Action:
No action is required.
Reason:
This is a 40-character general action message.
Action:
Take appropriate action if indicated.
Reason:
This is a 40-character general disaster message.
Action:
Take appropriate action if indicated.
Reason:
This is a 40-character general error message.
Action:
Take appropriate action if indicated.
Reason:
This is a 40-character general informational message.
Action:
Informational; take appropriate action if indicated.
Reason:
This is a 40-character general warning message.
Action:
Take appropriate action if indicated.
Reason:
The CAICCI subsystem has encountered an internal error while processing normal data transfer services. This message is accompanied by another CAS9 message indicating the exact nature of the problem. The above items indicate the VTAM return code at the time when the abnormal condition occurred.
Action:
See the IBM VTAM Programming manual for VTAM return codes, feedback codes, and sense information. This message is accompanied by another CAS9 message that indicates the type of request that has failed.
Reason:
The CAICCI subsystem has encountered an internal error while processing normal data transfer services. This message is accompanied by another CAS9 message indicating the exact nature of the problem. The above items indicate the contents of registers 15, 0, and 1 at the time of error. This message is accompanied by another CAS9 message that indicates the type of request that has failed.
Action:
No action is required.
Reason:
The CAICCI subsystem has encountered an internal error while processing normal data transfer services. This message is accompanied by another CAS9 message indicating the exact nature of the problem or the type of request that has failed. This message indicates internal error flags.
Action:
Note return codes and notify CA Support of the problem.
Reason:
Displayed on the console whenever a CAICCI STATUS is requested and CAICCI is not operational.
Action:
No action is required.
Reason:
The CAICCI subsystem was unable to initialize the CAICCI communication manager.
Action:
This message is accompanied by another CAS9 message indicating the exact nature of the problem. Save all appropriate documentation for CA Support evaluation.
Reason:
The CAICCI subsystem was unable to initialize the CAICCI dispatch manager.
Action:
This message is accompanied by another CAS9 message indicating the exact nature of the problem. Save all appropriate documentation for CA Support evaluation.
Reason:
The CAICCI subsystem was unable to determine the SYSID for this host's CAICCI.
Action:
Define the SYSID through the SYSID options command of CAICCI. Refer to the Installation Guide for further information.
Reason:
The CAICCI subsystem was unable to determine the APPLID for this host's CAICCI.
Action:
No action is required if remote host communications are not required. Refer to the Installation Guide for further information.
Reason:
An attempt has been made to initialize the CAICCI subsystem, but failed due to missing initialization parameters.
Action:
Missing APPCL function. Refer to the Installation Guide for further information. Update CAICCI through APPCL options and recycle CAIENF.
Reason:
The CAICCI subsystem has encountered an internal error while processing normal data transfer services. This message is accompanied by another CAS9 message indicating the exact nature of the problem.
Action:
Determine the nature of the CAIENF failure and correct before restarting CAICCI.
Reason:
The CAICCI subsystem has encountered an internal program check-type error while processing normal data transfer services. This message is accompanied by another CAS9 message indicating the exact nature of the problem.
Action:
Determine the nature of the CAIENF failure and correct before restarting CAICCI.
Reason:
The CAICCI subsystem has encountered an internal logic error while processing normal data transfer services. This message is accompanied by another CAS9 message indicating the exact nature of the problem.
Action:
Determine the nature of the CAIENF failure and correct before restarting CAICCI.
Reason:
The CAICCI subsystem has determined that CAIENF is no longer operational. CAICCI terminates.
Action:
Determine the nature of the CAIENF failure and correct before restarting CAICCI.
Reason:
The CAICCI subsystem is in the process of being initialized. xxxxxxxx in the message refers to the CAICCI version and modification level. For example, V1M0L005 refers to version 1, modification 0, level 005.
Action:
No action is required.
Reason:
This message indicates the ACB name that CAICCI used in attempting to start a session with VTAM, and was unsuccessful. This message is accompanied by messages CAS9605, CAS9606, and CAS9622. Probable user error.
Action:
Check the APPCL or PROTOCOL statement to ensure that the proper ACB name was specified. Display the ACB name using VTAM network services and ensure proper definitions.
Reason:
The CAICCI subsystem has issued a VTAM "OPEN" request against the VTAM ACB and received a negative response.
Action:
The CAICCI subsystem is terminated because no retry time was specified in the ENFPARM APPCL control card. Refer to the Installation Guide for further information.
Reason:
The CAICCI subsystem is being terminated. This message is accompanied by another CAS9 message indicating the exact nature of the problem.
Action:
Refer to the accompanying CAS9 messages.
Reason:
The CAICCI subsystem "INTERFACE" module is not initialized. A probable condition of this message is a missing or corrupted "CASNMINT" module.
Action:
The CAICCI subsystem is abnormally terminated. Verify that the above module has been installed correctly and has not been corrupted.
Reason:
The CAICCI subsystem has issued a VTAM "OPEN" request against the VTAM ACB and received a negative response. The OPEN is retried in xx minutes.
Action:
This message appears whenever the ACB is inactive, improperly defined, or simply not defined. Refer to the Installation Guide for further information.
Reason:
The CAICCI subsystem has been made operational.
Action:
No action is required.
Reason:
The CAICCI subsystem is being terminated abnormally. This message is accompanied by another CAS9 message indicating the exact nature of the problem.
Action:
Refer to the accompanying CAS9 CAICCI messages.
Reason:
This message indicates that CAICCI was unable to start all required subtasks. The module name xxxxxxxx was either not found or was invalid.
Action:
Check the CAICCI STEPLIB to ensure that the module has been placed in the LOADLIB properly.
Reason:
The CAICCI subsystem is unable to return to problem state. This message may be a symptom of a larger "corrupted storage" problem.
Action:
Refer to the accompanying CAS9 CAICCI messages. Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
One or more of the CAICCI subsystem modules are not available or not initialized. A probable condition of this message is a missing or corrupted module. Modules referred to can be:
Action:
The CAICCI subsystem is abnormally terminated. Verify that the above modules were installed correctly and have not been corrupted. Refer to the Installation Guide for further information.
Reason:
The CAICCI startup component (CASNMNET) has initialized and is operational.
Action:
No action is required.
Reason:
CAICCI Component Trace initialization failed. The return code (R15) and reason code (R0) will identify the specific error.
Action:
Record the return code and reason code and contact customer support.
Reason:
The CAICCI subsystem has encountered corrupted CSA storage. This message may be a symptom of a larger "corrupted storage" problem.
Action:
Refer to the accompanying CAS9 CAICCI messages. Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
The CAICCI subsystem Network Manager (CASNMNET) is being terminated abnormally. This message is accompanied by another CAS9 message indicating the exact nature of the problem.
Action:
Refer to the accompanying CAS9 CAICCI messages.
Reason:
The CAICCI subsystem Network Manager (CASNMNET) has terminated the CAICCI subsystem.
Action:
No action is required.
Reason:
The CAICCI subsystem Network Manager (CASNMNET) has determined that the CAICCI subsystem is to be terminated. This message is accompanied by another CAS9 message indicating the exact reason of the termination.
Action:
Refer to the accompanying CAS9 CAICCI messages.
Reason:
The CAICCI subsystem Network Manager (CASNMNET) has determined that the CAICCI subsystem is running from a library that is not APF authorized.
Action:
Refer to the Installation Guide for further information.
Reason:
The CAICCI subsystem has issued a VTAM "OPEN" request against the VTAM ACB and received a positive response. CAICCI is now in session with the SSCP.
Action:
No action is required.
Reason:
The CAICCI subsystem Communication Manager (CASNMCOM) has been initialized and is operational.
Action:
No action is required.
Reason:
The CAICCI subsystem has encountered corrupted Private Area storage associated with a mainline control CAICCI control block.
Action:
CAICCI is abnormally terminated. Refer to the accompanying CAS9 CAIENF messages. Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
The CAICCI subsystem has encountered corrupted CSA storage. This message may be a symptom of a larger "corrupted storage" problem.
Action:
CAICCI is abnormally terminated. Refer to the accompanying CAS9 CAIENF messages. Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
The CAICCI subsystem Communications Manager (CASNMCOM) has determined that the CAICCI subsystem is to be terminated. This message is accompanied by another CAS9 message indicating the exact reason of the termination.
Action:
Refer to the accompanying CAS9 CAICCI messages.
Reason:
The CAICCI subsystem Communications Manager (CASNMCOM) is being terminated abnormally. This message is accompanied by another CAS9 message indicating the exact nature of the problem.
Action:
Refer to the accompanying CAS9 CAICCI messages.
Reason:
The CAICCI subsystem Dispatch Manager (CASNMCOM) has initialized and is operational.
Action:
No action is required.
Reason:
The CAICCI subsystem Dispatch Manager (CASNMDSP) has determined that the CAICCI subsystem is to be terminated. This message is accompanied by another CAS9 message indicating the exact reason of the termination.
Action:
Refer to the accompanying CAS9 CAICCI messages.
Reason:
The CAICCI subsystem Dispatch Manager (CASNMDSP) is being terminated abnormally. This message is accompanied by another CAS9 message indicating the exact nature of the problem.
Action:
Refer to the accompanying CAS9 CAICCI messages.
Reason:
The CAICCI subsystem Interface Manager (CASNMCOM) has initialized and is operational.
Action:
No action is required.
Reason:
The CAICCI subsystem Interface Manager (CASNMINT) has determined that the CAICCI subsystem is to be terminated. This message is accompanied by another CAS9 message indicating the exact reason of the termination.
Action:
Refer to the accompanying CAS9 CAICCI messages.
Reason:
The CAICCI subsystem Interface Manager (CASNMINT) is being terminated abnormally. This message is accompanied by another CAS9 message indicating the exact nature of the problem.
Action:
Refer to the accompanying CAS9 CAICCI messages.
Reason:
This message provides supplementary information when a VTAM RPL request has failed. This message indicates:
Action:
No action is required.
Reason:
This message indicates the VTAM LOSTERM EXIT RC (reason code) and the VTAM LU (logical unit) of the session that has been terminated. The reason code may be found in the IBM VTAM Programming manual. CAICCI will try to reconnect to the lost LU.
Action:
No action is required.
Reason:
The CAICCI subsystem has issued a VTAM "REQSESS" request against the remote LU and received a negative response.
Action:
This message appears whenever the remote LU is inactive, improperly defined, or simply not defined. Refer to the Installation Guide for further information. Refer to the accompanying CAS9 CAICCI messages.
Reason:
The CCICT command (operator or configuration file) detected that it has already run.
Action:
None.
Reason:
The CCICT command (operator or configuration file) detected that the requested number of buffers with the specified buffer size would exceed the size of the CTRACE Data Space. The requested number of buffers is reduced to the maximum $$$$$$$.
Action:
None.
Reason:
CAICCI Node definition has been updated and processed.
Action:
No action is required.
Reason:
The sense information received from VTAM has indicated that the MAXRU specified in the PROTOCOL, NODE, or MAXRU statement (xxxxx) for the LU (yyyyyyyy) has exceeded the maximum length. To determine the required MAXRU for host connected through NCP, refer to the:
See the IBM z/OS Communications Server SNA Resource Definition Reference. You should also consult with your data center's VTAM/NCP system programmer for further information.
Action:
Update the MAXRU values on CCIPARMS or ENFPARMs for the PROTOCOL, NODE, and MAXRU statements on the local and remote systems as needed, and restart CAIENF.
Reason:
The number of Outstanding Send Requests of all local CCI applications to all remote CCI applications has exceeded nnnnnn. This message will be issued for every increase of 1000 Outstanding Sends. This message does not necessarily indicate a problem. If the message occurs once, it indicates a momentary increase in CCI processing. If it is displayed more than once, it indicates that the CCI workload volume is exceeding its processing throughput capacity. This could be a problem with a communication link, with an application that invokes CCI services, or there is a problem with the service class or dispatching priority of one of the CCI processes.
Action:
Normally there is no action required. Monitor message frequency. If the message continues to be displayed, take dumps of the ENF/CCI address space and contact CCI support.
Reason:
The CAICCI subsystem has requested storage for an ACB and received a negative response. This message appears when "private area" storage is no longer available. CAICCI continues to operate at a degraded level due to the storage constraint condition. xxxxxxxx refers to the return code (R15) from storage management.
Action:
The CAICCI subsystem may be terminated, region size increased, and then restarted. Refer to the Administration Guide for details on recycling CAIENF.
Reason:
The CAICCI subsystem has requested storage for an EXLST and received a negative response. This message appears when the private area storage is no longer available. CAICCI continues to operate at a degraded level due to the storage constraint condition. xxxxxxxx refers to the return code (R15) from storage management.
Action:
The CAICCI subsystem may be terminated, region size increased, and then restarted. See "Event Notification Facility" in the Administration Guide for details on recycling (restarting) CAIENF.
Reason:
The CAICCI subsystem has requested storage for a VTAM RPL and received a negative response. This message appears when "private area" storage is no longer available. CAICCI continues to operate at a degraded level due to the storage constraint condition. xxxxxxxx refers to the return code (R15) from storage management.
Action:
The CAICCI subsystem may be terminated, region size increased, and then restarted. See "Event Notification Facility" in the Administration Guide for details on recycling (restarting) CAIENF.
Reason:
The CAICCI subsystem has requested storage for an NIB and received a negative response. This message appears when "private area" storage is no longer available. CAICCI continues to operate at a degraded level due to the storage constraint condition. xxxxxxxx refers to the code (R15) from storage management.
Action:
The CAICCI subsystem may be terminated, region size increased, and then restarted. See "Event Notification Facility" in the Administration Guide for details on recycling (restarting) CAIENF.
Reason:
The CAICCI subsystem has requested storage from any buffer and received a negative response. This message appears when "private area" storage is no longer available. CAICCI continues to operate at a degraded level due to the storage constraint condition. xxxxxxxx refers to the return code (R15) from storage management.
Action:
The CAICCI subsystem may be terminated, region size increased, and then restarted. See "Event Notification Facility" in the Administration Guide for details on recycling (restarting) CAIENF.
Reason:
The CAICCI subsystem has requested storage management to modify a VTAM control block (yyy) and received a negative response. This message appears when "private area" storage is corrupted. CAICCI continues to operate at a degraded level due to the storage problem. xxxxxxxx refers to the return code (R15) from storage management.
Action:
The CAICCI subsystem can be recycled to "clean up" the storage condition. Save all dumps and other diagnostics for CA Support assistance, if required. See "Event Notification Facility" in the Administration Guide for details on recycling (restarting) CAIENF.
Reason:
There was an internal error in CAICCI between two internal tasks.
Action:
If this message occurs after maintenance is installed, an IPL or REFRESH of CAS9VTAM and CAS9CCI2 is required; otherwise, refer to the accompanying CAS9 messages.
Reason:
The CAICCI subsystem residing as a CAICCI Network Primary (yyyyyyyy) has received a logon request from a CAICCI Network Secondary (xxxxxxxx).
Action:
No action is required.
Reason:
CAICCI subsystem residing as a CAICCI Network primary (yyyyyyyy) has accepted the logon request from a CAICCI Network Secondary (xxxxxxxx) and is now in session with it.
Action:
No action is required.
Reason:
The CAICCI subsystem residing as a CAICCI Network Primary (yyyyyyyy) has lost the session with the CAICCI Network Secondary (xxxxxxxx).
Action:
No action is required. See the accompanying CAS9 CAICCI messages for further details on session loss. This message can occur for several reasons:
Reason:
The CAICCI subsystem residing as a CAICCI Network Primary (yyyyyyyy) has rejected the logon request from a CAICCI Network Secondary (xxxxxxxx).
Action:
No action is required. See the accompanying CAS9 CAICCI messages for further details on session loss. This error may occur if a non-CAICCI application attempts a logon to the CAICCI subsystem.
Reason:
The CAICCI subsystem residing as a CAICCI Network Primary (yyyyyyyy) was accepted by the CAICCI Network Secondary (xxxxxxxx); however, the SSCP did not allow the session connection.
Action:
No action is required. See the accompanying CAS9 CAICCI messages for further details on session loss. This error may occur if insufficient storage is available to allow session establishment.
Reason:
CAICCI received an incoming logon request from a nonsupported LU. Specifics of reason are shown in the xxxxxxxxxxxxxxxxxxxxxxxx message.
Action:
Verify that the incoming LU session requestor is a proper CAICCI system. Record all appropriate messages and notify CA Support.
Reason:
CAICCI has detected a conflict in the alias name passed by the remote platform. This alias name is already presently used by another platform with a different long name.
Action:
CAICCI will use a hex value of the TCP/IP address as the short name.
Reason:
This message will always appear with message CAS9677W. This name displayed is the long name attempting to sign on which has the conflict.
Action:
No action is required. (See message CAS9677W.)
Reason:
An abend has occurred within CAICCI. The variable field displays the abend code.
Action:
This message is possible only with CAICCI 2.1.
See accompanying messages for more detail description of the error. Save all dumps and other diagnostics for CA Support assistance if required.
Reason:
The CAICCI subsystem residing as a CAICCI Network Secondary (yyyyyyyy) has requested a session with the CAICCI Network Secondary (xxxxxxxx).
Action:
No action is required.
Reason:
The CAICCI subsystem residing as a CAICCI Network Secondary (yyyyyyyy) has received positive acknowledgment from the CAICCI Network primary (xxxxxxxx) and is now in session with it.
Action:
No action is required.
Reason:
The CAICCI subsystem residing as a CAICCI Network secondary (yyyyyyyy) has lost the session with the Network Primary (xxxxxxxx).
Action:
Refer to the accompanying CAS9 CAICCI messages for further details on session loss. This message can occur for several reasons:
Reason:
The CAICCI subsystem, residing as a CAICCI Network Secondary (yyyyyyyy), has determined that the MAXRU is greater than the CAICCI subsystem allows. This is indicative of a non-CAICCI subsystem attempting session establishment using invalid BIND parameters.
Action:
No action is required. See the accompanying CAS9 CAICCI messages for further details on session loss.
Reason:
The CAICCI subsystem residing as a CAICCI Network Secondary has requested a MAXRU that is greater than the SSCP allows. An inconsistency between the MAXRU size (NODE statement in the CAICCI parameters) and the SSCP, or NCP, exists.
Action:
The CAICCI subsystem is terminated. see "CAICCI Control Options" in the Reference Guide for details about the NODE statement.
Reason:
This message indicates the ACB name of the remote CAICCI that this CAICCI attempted to contact and was unable to. This message is accompanied by message CAS9605N or CAS9606N. Probable user error.
Action:
Check the APPCR or NODE statement to ensure that the proper ACB name has been specified. Display the ACB name using VTAM network services and ensure proper definitions.
Reason:
This message indicates an inconsistency between the local host (PROTOCOL) statement and the remote system's NODE statement.
Action:
Ensure consistency among all CAICCI PROTOCOL statements and NODE statements.
Reason:
This message will be displayed to show the image of the incoming CINIT or BIND.
Action:
Refer to the accompanied CAS9 CAICCI message for further details on session connection request failure.
Reason:
A second NODE or GATEWAY statement was encountered for the same remote SYSID but specified a different protocol type. Only one protocol type may be assigned for each remote SYSID. The protocol defined by the first NODE statement for a SYSID is used. Subsequent NODE statements specifying a different protocol for the SYSID are ignored.
Action:
Remove the NODE statement specifying the incorrect protocol type.
Reason:
The CAICCI subsystem is unable to locate a control block (xxxx) and is unable to continue.
Action:
The CAICCI subsystem is abnormally terminated. For assistance, contact CA Support at http://ca.com/support.
Reason:
The CAICCI subsystem is unable to attain storage for control block xxxxxxxx, where yyyyyyyy is the cause.
Action:
The CAICCI subsystem is abnormally terminated. For assistance, contact CA Support at http://ca.com/support.
Reason:
The CAICCI subsystem is unable to perform VTAM function xxxxxxxx for reason yyyyyyyy.
Action:
The CAICCI subsystem writes a snap dump and continues processing. For assistance, contact CA Support at http://ca.com/support.
Reason:
The CAICCI subsystem is unable to attain storage for control block xxx.
Action:
The CAICCI subsystem writes a snap dump and continues processing. For assistance, contact CA Support at http://ca.com/support.
Reason:
The CAICCI subsystem is unable to free storage for control block xxx.
Action:
The CAICCI subsystem writes a snap dump and continues processing. For assistance, contact CA Support at http://ca.com/support.
Reason:
The CAICCI subsystem has determined that another CAICCI is active within this host.
Action:
The CAICCI subsystem terminates.
Reason:
The CAICCI subsystem is about to be terminated.
Action:
No action is required.
Reason:
The CAICCI subsystem is at final termination but may be restarted. Once CAICCI has terminated, it can only be restarted by stopping and restarting ENF.
Action:
Reply Y to terminate CAICCI. Any other reply is treated as an N (NO) response and results in a restart of CAICCI.
Reason:
Separator mark used to denote separation in line and resource displays.
Action:
No action is required.
Reason:
CAICCI has knowledge of xxxxxxxx number of receivers. yyyyyyyy are receivers that are local to this host. zzzzzzzz are receivers that are remote to this host.
Action:
No action is required.
Reason:
CAICCI has a receiver whose ID is aaaaaaaaaaaaaaaaaaaaaaaa.
Action:
No action is required.
Reason:
CAICCI has a receiver whose EID is bbbbbbbbbbbbbbbbbbbbbbbbbb.
Action:
No action is required.
Reason:
CAICCI has a receiver that is owned by SYSID aaaaaaaa. It has initiated xxxxxxxx receive requests and yyyyyyyy sends have been targeted to it. The type ID resource b is either L (local for this host) or R (remote host-owned resource).
Action:
No action is required.
Reason:
CAICCI has a receive outstanding. Y(es) or N(o). CAICCI date of last receive initiated was xxxxxxxx. CAICCI time of last receive initiated was yyyyyyyy.
Action:
No action is required.
Reason:
CAICCI has a receiver that allows queuing. Y(es) or N(o). CAICCI date of last send initiated to this receiver was xxxxxxxx. CAICCI time of last send initiated to this receiver was yyyyyyyy.
Action:
No action is required.
Reason:
This message is produced as a result of a DISPLAY RESOURCE request. ROUT will be either Y(es) or N(o) to indicate if there is a current receive outstanding. DOLRI indicates the Date Of the Last Receive Initiated. TOLRI indicates the Time Of the Last Receive Acknowledged. D(eletable) indicates whether this receiver is being terminated, Y(es) or N(o).
Action:
No action is required.
Reason:
This message is produced as a result of a DISPLAY RESOURCE request. QUE will be either Y(es) or N(o) to indicate if this receiver allows sends to be queued to it. DOLSI indicates the Date Of the Last Send Initiated. TOLRI indicates the Time Of the Last Send Acknowledged.
Action:
No action is required.
Reason:
This message is displayed in response to a DISPLAY RVTLOCK or DISPLAY RRTLOCK command.
The response to a DISPLAY RVTLOCK will be either RVT LOCKED or RVT UNLOCKED.
The response to a DISPLAY RRTLOCK will be either RRT LOCKED or RRT UNLOCKED.
Action:
If the response to either command is UNLOCKED, no action is required. If the response to either command is LOCKED, a resource lock has not been released. CCI will continue to run but with extremely degraded performance. Contact CCI support if this occurs.
Reason:
The variables refer to the following:
Indicates whether this CAICCI link speaker is P(rimary) or S(econdary).
Indicates whether this CAICCI link is active: Y(es) or N(o).
Identifies the type of link represented by this CAICCI link: N(etwork), T(CP/IP), X(ES), or M (XCF).
Identifies the LU type represented by this CAICCI link: LU0, TCP/IP, XES, or XCF.
Identifies the origin of the link: R(emote) or L(ocal).
Identifies the release date of the CAICCI system format: mm/dd/yy or yyyymmdd.
Action:
No action is required.
Reason:
This CAICCI link APPLID is aaaaaaaa. This CAICCI link SYSID is bbbbbbbb. The number of CAICCI line drops encountered is cccccccc.
Action:
No action is required.
Reason:
The variables refer to:
Action:
No action is required.
Reason:
The variables refer to:
Action:
No action is required.
Reason:
This message is produced as a result of a DISPLAY LINE request. MXRUP is the Maximum Request Unit Size for the Primary session partner. That is the maximum size that the Secondary CAICCI LU can send to the Primary CAICCI LU. MXRUS is the Maximum Request Unit Size for the Secondary session partner. That is the maximum size that the Primary CAICCI LU can send to the Secondary CAICCI LU. MP and MS are the MAXRU sizes in special format that is specified in the CINIT and BIND.
Action:
No action is required.
Reason:
This message is produced as a result of a DISPLAY LINE request. SENDQ indicates the number of sends that have been queued on this line. TSENDO indicates the total number of send requests outbound that have been sent across this line. TSENDA indicates the total number of send requests that have been acknowledged across this line.
Action:
No action is required.
Reason:
This message is produced as a result of a DISPLAY SYSID request. xxxxxxxx represents the CAICCI SYSID of this host.
Action:
No action is required.
Reason:
This message is produced as a result of a DISPLAY NODE or a DISPLAY PROTOCOL request. xxxx will either be PROT or NODE determined by the type of request that is being made. Type is the LU type or protocol type. RETRY is the time interval in minutes that CAICCI will use before retrying a session request. START indicates the startup option selected. SHUT indicates the shutdown option selected.
Note: See the Installation Guide for more information on the Start and Shut options.
Action:
No action is required.
Reason:
This message is produced as a result of a DISPLAY NODE or a DISPLAY PROTOCOL request. xxxx is either PROT or NODE (determined by the type of request that is being made). MAXRU is the maximum request unit that can be sent by this side to its session partner. SYSID is the CAICCI SYSID. ACB may or may not be present in the message. When present, the ACB refers to the VTAM ACB name selected.
Action:
No action is required.
Reason:
This message is produced as a result of a CCI(DISPLAY,LINK) request for non-VTAM nodes. The CAICCI link SYSID is aaaaaaaa and the number of CAICCI link drops encountered is bbbbbbbb.
Action:
No action is required.
Reason:
This message is produced as a result of a CCI(DISPLAY,LINK) request for a TCP/IP node. xxx.xxx.xxx.xxx is the TCP/IP address, while yyyy is the port number.
Action:
No action is required.
Reason:
This message is produced as a result of a DISPLAY NODE request. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx is the TCP/IP address and port number as they were entered on the NODE statement specified in CCIPARMS.
Action:
No action is required.
Reason:
This message is produced as a result of a CCI(DISPLAY,LINK) request for a TCP/IP node.
The TCP/IP address if IPv4.
IPv6 format of address.
Action:
No action is required.
Reason:
This message is produced as a result of a CCI(DISPLAY,LINK) request for a TCP/IP node.
The active PORT.
Action:
No action is required.
Reason:
This message is produced as a result of a CCI(DISPLAY,LINK) request for a TCP/IP node.
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx is the TCP/IP DNS Hostname.
Action:
No action is required.
Reason:
This message is produced as a result of a DISPLAY CONNECT request. Up to seven remote CAICCI SYSIDs will be displayed on this line.
Action:
No action is required.
Reason:
This displays the startup CAICCI requested start option (RSTART), requested stop or shut option (RSHUT), the current start option (CSTART), the current stop or shut option (CSHUT), and the (SYSPLEX) ID of which this CAICCI system is a member.
Action:
No action is required. This message is informational only.
Reason:
This message is displayed in response to a DISPLAY, RECEIVE command. For each local receiver, this message displays the number of messages that are on the receiver’s pending queue awaiting the receiving application’s read request.
Action:
No action is required.
Reason:
This message is displayed in response to a DISPLAY, RECEIVE command. For each local receiver, this message displays the Jobname and Job Number of the application that created the receiver.
Action:
No action is required.
Reason:
A CONNECT statement was specified, but no NODE definition for the specified SYSID (xxxxxxxx) was found.
Action:
Specify the NODE definition for this CONNECT request.
Reason:
One of the CAICCI modules (xxxxxxxx) was unable to initialize. This message will be accompanied by one or more CAS9 CAICCI messages.
Action:
Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
This message indicates the CAICCI Server Manager is active.
Action:
No action is required.
Reason:
This message indicates the CAICCI Server Manager is being terminated normally.
Action:
No action is required.
Reason:
This message indicates the CAICCI Server Manager is being terminated abnormally.
Action:
Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
This message indicates the CAICCI LU Services Manager is operational and at PUT level xxxxxxxx.
Action:
No action is required.
Reason:
This message indicates the CAICCI LU Services Manager is being terminated normally.
Action:
No action is required.
Reason:
This message indicates the CAICCI LU Services Manager is being terminated abnormally.
Action:
Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
This message indicates the CAICCI Server Manager is active.
Action:
No action is required.
Reason:
This message indicates the CAICCI SPAWN manager is being terminated normally.
Action:
No action is required.
Reason:
This message indicates the CAICCI SPAWN manager is being terminated abnormally.
Action:
Save all dumps and other diagnostics for CA Support assistance, if required.
Reason:
This message accompanies other CAICCI link messages and indicates the VTAM sense modifiers.
Action:
Refer to the appropriate VTAM documentation for the exact nature of the problem.
Reason:
This message accompanies other CAICCI link messages and indicates the VTAM sense modifiers.
Action:
Refer to the appropriate VTAM documentation for the exact nature of the problem.
Reason:
CAICCI receiver is no longer available on the system.
Action:
Determine the nature of the CA solution failure and contact CA Support.
Reason:
CAICCI receiver is no longer available on the system.
Action:
Determine the nature of the CA solution failure and contact CA Support.
Reason:
CAICCI is receiver no longer available on the system.
Action:
Determine the nature of the CA solution failure and contact CA Support.
Reason:
An unauthorized user has requested a session with CAICCI.
Action:
Session request is not accepted. Follow up as your data center policy dictates.
Reason:
An unauthorized user has requested a session with CAICCI.
Action:
No action is required. This message is informational only.
Reason:
A CAICCI SPAWN server (CASNMVSR) has been initialized and is ready to accept work from the CAICCI SPAWN manager.
Action:
No action is required. This message is informational only.
Reason:
A CAICCI SPAWN server (CASNMVSR) has been requested to terminate itself.
Action:
No action is required. This message is informational only.
Reason:
A CAICCI SPAWN server (CASNMVSR) is being terminated abnormally. This message is accompanied by other CAS9 messages indicating the exact reason of the termination.
Action:
Refer to the accompanying CAS9 CAICCI messages and take appropriate action.
Reason:
A CAICCI SPAWN server has terminated. xxxxxxxxxxxxxxxxxxxxxxxx represents the reason of the termination.
Action:
No action is required. This message is informational only.
Reason:
The message displays the CAICCI SPAWN server name of xxxxxxxxxxxxxxxxxxxxxxxx and the CAICCI RECEIVE ID of yyyyyyyyyyyyyyyyyyyyyy.
Action:
No action is required. This message is informational only.
Reason:
The message displays the CAICCI SPAWN server job name of xxxxxxxx, job number of yyyyy, and the z/OS ASID of zzzz.
Action:
No action is required. This message is informational only.
Reason:
This message is produced in response to a CAICCI LOGGER DISPLAY command. z will be either a Y or N, indicating whether the logger data set specified in DSN= is opened.
Action:
No action is required. This message is informational only.
Reason:
This message is produced in response to a CAICCI LOGGER DISPLAY command and shows the available spaces, the percent full, and the number of extents the LOGGER data set is currently using.
Action:
No action is required. This message is informational only.
Reason:
This message is produced in response to a CAICCI LOGGER PURGE command. nnnnnnnn is the number of records deleted from the LOGGER data set.
Action:
No action is required. This message is informational only.
Reason:
Attempted to start an additional CAILGR address space.
Action:
The new CAILGR address space will terminate.
Reason:
The LOGGER data set is equal to or greater than 80% full.
Action:
If the LOGGER data set was allocated with a secondary allocation, the number of extents are not at the maximum and there is available space on the disk volume where the logger data set is allocated, VSAM will allocate an additional extent. No further action is needed at this time.
If there is no secondary allocation or no available space on the disk volume, or the number of extents is at the maximum, the LOGGER facility will terminate when the LOGGER data set becomes full.
Reason:
A VSAM error occurred during a WRITE to the CCILGR Assured Delivery database.
Action:
Consult the IBM manual Z/OS/DFP Macro Instructions for Data Sets for the VSAM FDBK and FTNCD.
Reason:
When CCILGR is not running, the LOGGER API is unable to get the ENQ required to open the LOGGER database.
Action:
Contract Common Services support.
Reason:
During REORG processing of the VSAM file, the REORG process failed.
Action:
If the reply is “C” CCILGR will start.
Important! Data may be lost.
If the reply is “A” CCILGR will abend with abend code 3233 (CA1).
For assistance, contact CA Support at http://ca.com/support.
Reason:
VSAM file failed to open. @@($$$) is the OPEN reason code.
Action:
Make sure the VSAM file is defined correctly.
Reason:
The CAIENF/DB2 interface is being initialized.
Action:
No action is required.
Reason:
The CAIENF/DB2 interface has completed initialization. $$$$ is the defined z/OS system for the interface.
Action:
No action is required.
Reason:
The CAIENF/DrB2 interface, defined as z/OS Subsystem $$$$, has terminated.
Action:
No action is required.
Reason:
CAIENF/DB2 is not installing its intercepts into the DB2 system xxxxx.
Action:
If the CAIENF/DB2 intercepts are required in this DB2 system, the actions listed in the Administration Guide (CAIENF/DB2 Execution) must be taken. Otherwise, this message is informational.
Reason:
Indicates that the ENF/DB2 DDF processing thread has successfully started.
Action:
No action is required.
Reason:
The CCITCP address space has completed initialization and is ready to service applications. $$$$ is the port number CCITCP is using, and %%%%%% is the Internet address of the z/OS host reported by TCP/IP.
Multiple messages are associated with this message number. All of them are informational regarding the initialization of the underlying communication protocol (TCP/IPv4, TCP/IPv6, and SSL) by CCITCP, CCITCPGW, CCISSL, and CCISSLGW.
Action:
No action required.
Reason:
CAICCI received a connection request from a remote user. In this message, $$ contains a CCITCP logical task identifier and %%%%%% contains the Internet address of the remote user connecting to CAICCI.
Action:
No action required.
The following CAS9855I informational messages are displayed on the console by CCISSLGW when a connection is established. These messages require no action.
Reason:
A remote node yyyyyyyy, with IP address nnn.nnn.nnn.nnn, has reconnected to this host.
Action:
No action is required.
Reason:
During remote reconnection to host xxxxxxxx, the IP address has changed from the last connection.
Action:
If a MULT-LAN card is available on this remote host, the host IP address was changed, or if Virtual IP Addressing (VIPA) is used, ignore this message. Otherwise, there may be two or more remote nodes with the same system ID name, which is a configuration problem.
Reason:
A remote connection is about to be closed. The message identifies both the number of data bytes transferred and the number of network packets required.
Action:
No action required.
Reason:
CAICCI has received a data packet from a remote application that appears to be invalid. The message contains information that may be important for CAICCI support personnel in diagnosing the problem. After reporting the error, CAICCI will close the connection to the remote system.
Action:
Retry the failing operation. If the problem persists, contact CAICCI support.
Reason:
CCITCP and CCITCPGW require External Security (CA ACF2, CA Top Secret, or RACF).
Action:
Beginning with IBM TCP/IP Version 3.4, IBM requires OMVS segments to be defined to the external security product installed. See the IBM documentation for details about defining an OMVS segment.
Reason:
A TCP/IP Sockets API error has occurred. The variable portion of the message identifies the specific API invoked and explains the error that occurred. If the error can be associated with a single user, then that user's connection will be broken and other sessions will be unaffected. Otherwise, if the error is global in nature or occurs during initialization, CCITCP will terminate.
Certain errors may indicate a lack of memory within the CCITCP address space. If you receive one of these errors, either increase the size of the CCITCP address space (by increasing the REGION= parameter in the CCITCP started task JCL), or run another copy of the CCITCP address space.
Action:
Correct the problem identified in the error message and retry the failing operation.
Reason:
Multiple messages are associated with this message number. All of them are informational regarding the parameters and commands that were passed to CCITCP, CCITCPGW, CCISSL, and CCISSLGW, their run-time environment, and their resultant mode and status of operation.
Action:
No action required.
Reason:
The CCITCP address space was started before TCP/IP for z/OS. CAICCI will periodically attempt to connect to TCP/IP and will continue operating once TCP/IP starts.
Action:
Start TCP/IP for z/OS, if you have not done so already.
Reason:
The ENF SNMP address space has been started.
Action:
No action is required.
Reason:
An error has occurred while executing the CAICSMF or CAICRIM CLISTs. Actual return code from processing is displayed.
Action:
Probable error in locating CAILIB or member CAISMFU/CAIRIMU does not exist. Check the CAILIB symbolic to ensure that the indicated library is correct and that the members CAISMFU and CAIRIMU exist.
Reason:
The ENF address space has become unavailable.
Action:
Start the ENF address space.
Reason:
MVS system is at pre-ESA level.
Action:
Upgrade the MVS system.
Reason:
ENF address space has become available.
Action:
No action is required.
Reason:
ENF SNMP event is not active to CAIENF. CAS9DCM4 has probably not been installed.
Action:
Install DCM CAS9DCM4 into the CAIENF database.
Reason:
An attempt has been made to start the ENF SNMP address space a second time.
Action:
No action is required.
Reason:
The ENF SNMP Monitor has completed its initialization.
Action:
No action is required.
Reason:
The P ENFSNMPM command has been issued and accepted. ENFSNMPM will shutdown.
Action:
No action is required.
Reason:
The ENF SNMP Monitor TRACE facility is now turned on to get tracing for diagnosis.
Action:
No action required. This message is informational.
Reason:
The ENF SNMP Monitor TRACE facility is now turned off.
Action:
No action required. This message is informational.
Reason:
This command is not valid for the ENF SNMP Monitor.
Action:
Check if your command is TRAce, NOtrace, SNAP or NOsnap.
Reason:
The SNAP facility is now turned on to dump hex ENF data to diagnose problems with the ENF SNMP monitor.
Action:
No action required. This message is informational.
Reason:
The SNAP facility for ENF SNMP Monitor is now turned off.
Action:
No action required. This message is informational.
Reason:
Another CAS9 initialization procedure is running on the system. This instance of CAS9 will wait up to 20 minutes for the other CAS9 to end. If the other instance of CAS9 does not end within 20 minutes, this instance of CAS9 will terminate.
Action:
No action is required.
Reason:
One of a group of messages issued in response to an ENF/CICS QUERY request.
The status (active or inactive) of the ENF/CICS interface.
Action:
No action is required. This message is informational.
Reason:
One of a group of messages issued in response to an ENF/CICS QUERY request.
This message displays the product ID, interface name, entry point address, and
status of one or more installed ENF/CICS applications.
Action:
No action is required. This message is informational.
Reason:
The purpose of this general information message is to display miscellaneous
ENF/CICS status information. This message would be issued, for example, in response
to an ENF/CICS QUERY request, to indicate the absence of any installed ENF/CICS
applications.
Action:
No action is required. This message is informational.
Reason:
This message is issued in response to a product/region-specific ENF/CICS QUERY
request. It confirms that product product is installed in CICS region region and is
currently active.
Action:
No action is required. This message is informational.
Reason:
This message is issued in response to a product/region-specific ENF/CICS QUERY
request. It indicates that product product is not installed in CICS region region.
Action:
No action is required. This message is informational.
Reason:
This message is issued in response to a product/region-specific ENF/CICS QUERY
request. It indicates that product product is installed in CICS region region, but it
is currently inactive.
Action:
No action is required. This message is informational.
Reason:
A SYSPRINT DD statement could not be found. The job cannot continue without this statement.
Action:
Supply a SYSPRINT DD statement in the execution JCL.
Reason:
A DCMLIB DD statement could not be found. The job cannot continue without the statement.
Action:
Supply a DCMLIB DD statement in the execution JCL.
Reason:
An input control statement was found that was not a comment or a DCM( statement.
Action:
Correct the control statement that is in error.
Reason:
An input DCM control statement was found that contained a blank before the closing parenthesis was found. The statement is considered to be terminated at the blank and the data following the blank is ignored.
Action:
Correct the control statement that is in error.
Reason:
A DCM load module must contain an eyecatcher of EDCM as the first characters. The DCM named in the message was found and loaded into storage, but the eyecatcher was not EDCM. Mapping of the named DCM is bypassed.
A DCM load module must also contain a version number of 1 or 2. If the version is not 1 or 2, then the DCM will not be mapped.
Action:
Research the named DCM to determine if the name was specified incorrectly or if the named member is not really a DCM.
For version 1 or 2 incompatibility, contact CA Support.
Reason:
The DCM named in the message was not found in the DCMLIB. Mapping of the named DCM is bypassed.
Action:
Research the named DCM to determine if the name was specified incorrectly or if the DCM is in a library other than the one named on the DCMLIB DD statement.
Reason:
An I/O error occurred while loading the named DCM from the DCM library. Mapping of the named DCM is bypassed.
Action:
Review the job log to determine if z/OS reported any errors. check the DCM library for errors and retry the job.
Reason:
The operating system reported an unknown type of error while loading the named DCM. Mapping of that DCM is bypassed.
Action:
Review the job log to determine if z/OS reported any errors. Check the DCM library for errors and retry the job.
Reason:
The operating system was unable to load the named DCM. Mapping of that DCM is bypassed.
Action:
Review the job log to determine if z/OS reported any errors. Check the DCM library for errors and retry the job.
Reason:
The DCM named in the message was previously found in a DCM control statement. The duplicate entry is ignored.
Action:
Remove the DCM name that is reported in the message, since it will already be processed by the previous reference.
Reason:
The internal DCM table is limited to 99 entries. There were more than 99 DCM names provided in the control statements. The program terminates.
Action:
Reduce the number of DCM names in the DCM control statements so that no more than 99 DCMs are processed in one run of the program.
Reason:
A request to the operating system for storage to hold the named DCM failed. There is not enough storage available.
Action:
Do one of the following:
Reason:
While parsing the DCM names in the DCM statement, a name was found that contained more than 8 characters. The name is truncated at 8 characters and the rest of the card is processed normally.
Action:
Find the incorrect DCM name and correct it so that it only contains 8 characters.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |