CA OPS/MVS® Event Management and Automation OPS MVS Event Managem… · Chapter 1: Messages and...

Message Reference Release 12.1

CA OPS/MVS Event Management and Automation

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation is proprietary information of CA and may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA.

If you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

Online and telephone contact information for technical assistance and customer services

Information about user communities and forums

Product and documentation downloads

CA Support policies and guidelines

Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected].

To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

http://www.ca.com/supportmailto:[email protected]://www.ca.com/docs

Contents 5

Contents

Chapter 1: Messages and Descriptions 7

Product Messages ........................................................................................................................................................ 7

Chapter 2: SSMGA Messages 779


Chapter 1: Messages and Descriptions

The following are descriptions of messages issued by CA OPS/MVS. For more information about messages issued by CA OPS/MVS, see the chapter Understanding CA OPS/MVS Messages in the User Guide. For online access to the following message descriptions, go to OPSVIEW Option 5.5.

Product Messages OPS0001U Initialization GETMAIN failed - increase storage size Modifiable: No Explanation: Insufficient storage. The product was unable to obtain enough storage to allocate the initial program stack. Action: Check the abend code to determine whether the region size should be increased. Increase the region size if necessary and restart the product. OPS0002U Load module OPMS not found - check libraries Modifiable: No Explanation: The load module containing the master control block could not be found during product initialization. Action: Check that the module (OPMS) can be found in a load library in the standard load module search sequence (STEPLIB, JOBLIB, LINKLIST, LPALIST). OPS0003U Authorization test failed - APF authorization needed Modifiable: No Explanation: The product is not APF authorized. An APF authorized library must be made available to hold the product load modules. The initial product module (OPINMA) must be link edited with an authorization

Product Messages

8 Message Reference

code of 1. All of the product modules must be stored in an authorized library. Action: Put the product load modules in an APF authorized library. An existing or new library may be used. Note that if a new one is created, an IPL may be required to make the change effective to the APF list. To make a dynamic change, use any one of the major online z/OS performance tools (for example, CA SYSVIEW Performance Management). OPS0004U Master scheduler control block error - contact systems programming Modifiable: No Explanation: The product early code failed because the current environment could not be identified. Action: Check if the product early code is being properly invoked, correct any errors, and then restart the product. OPS0005U Environment cannot be identified - contact systems programming Modifiable: No Explanation: None of the possible supported environments have been detected. CA OPS/MVS can be run as a started task, a batch job, or a TSO address space. The environment is not one of those supported. Action: Choose one of the above environments and restart the product. OPS0006U Load module mod not equal to storage copy - contact systems programm ing Modifiable: No Explanation: Either the length or the content of a load module loaded by the product during product initialization does not match an existing storage copy. The new load module may be longer or shorter or may contain different object code. Action: Check the product load module libraries. Make sure that all of the load modules are being obtained from the correct library.

Product Messages


The variable fields of the message text are: mod Module name OPS0007U Load module mod GETMAIN failed - increase memory size Modifiable: No Explanation: The product tried to obtain storage for a load module. The GETMAIN operation failed. Action: Increase the region storage size, if need be. Restart the product and contact CA Customer Support if the error recurs. The variable fields of the message text are: mod Module name OPS0008U Load module mod delete failed - contact systems programming Modifiable: No Explanation: The product tried to delete a load module during product initialization or termination. The delete operation failed. Action: Check the error messages associated with this problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: mod Module name OPS0009U Execution DEQ failed - contact systems programming Modifiable: No Explanation: Some type of error occurred while the product was releasing the execution ENQ. The execution ENQ is used to prevent more than one copy of the product from using a single subsystem ID. Multiple copies of the product can execute concurrently so long as each copy uses a different subsystem ID. Action: Check the error messages associated with this problem. If

Product Messages

10 Message Reference

possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. OPS0010U Load module mod release code error - contact systems programming Modifiable: No Explanation: The release code stored in a load module loaded by the product does not match the overall product release code. All of the load modules used by the product must have the same release code (except for the installation user exit and the JES2 offsets module). Action: Check the release code of the failing load module. Reinstall the incorrect load module, if need be. Restart the product and verify that the problem has been corrected. Contact CA Customer Support if the problem cannot be resolved. The variable fields of the message text are: mod Module name OPS0011U Load failed OPMDLD - check libraries Modifiable: No Explanation: The product tried to load a critical subroutine during product initialization or termination. The LOAD macro failed. The subroutine is used to load all of the product execution modules. Action: Check the error messages associated with this problem. There may be one or more contents supervision error messages referring to the current problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. OPS0012U OPMS storage FREEMAIN failed - contact systems programming Modifiable: No Explanation: The product tried to free the storage used by the master control block during product termination. The FREEMAIN operation failed.

Product Messages


Action: Check the error messages associated with this problem. There may be one or more storage management error messages referring to the current problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. OPS0013U SSCT locate error - contact systems programming Modifiable: No Explanation: The product tried to find the current subsystem ID in the subsystem control block chain. A loop was found in the subsystem control block chain. Action: This serious error may cause other components of the system to fail. If the system is having other problems (such as loop errors), try to resolve the other problems before restarting the product. If the product is the only component experiencing any difficulty, contact CA Customer Support to obtain additional assistance. OPS0014U mod Deallocation failed - contact systems programming Modifiable: No Explanation: The product attempted to release the storage used by a load module during product termination. The FREEMAIN operation failed. Action: Check the error messages associated with this problem. There may be one or more storage management error messages referring to the current problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: mod Module name OPS0015U pd-js subsystem ss waiting for execution ENQ Modifiable: No Explanation:

Product Messages


Each active copy of the product must use a different subsystem ID. This restriction is enforced using the product execution ENQ. The product execution ENQ contains the current subsystem ID, so that multiple copies of the product can execute if each copy uses a different subsystem ID. A new copy of the SS subsystem has been started and is attempting to get the execution ENQ. The execution ENQ for subsystem SS is already held by another copy of the product. Action: Either cancel the newly started SS subsystem that is waiting on the execution ENQ or stop the currently active copy of the SS subsystem. Stopping the currently active copy of the SS subsystem allows the new copy of the SS subsystem to complete initialization and start execution. The new copy of the SS subsystem may have to be stopped using the ASID keyword of the MVS CANCEL command. OPS0016U Execution ENQ error - contact systems programming Modifiable: No Explanation: Each active copy of the product must use a different subsystem ID. This restriction is enforced using the product execution ENQ. The product execution ENQ contains the current subsystem ID, so that multiple copies of the product can execute if each copy uses a different subsystem ID. The product tried to obtain the execution ENQ. The ENQ macro failed. Action: Check the error messages associated with this problem. There may be one or more ENQ/DEQ error messages referring to the current problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. OPS0017I pd-js subsystem subsys termination complete Modifiable: No Explanation: This is the standard product execution completed message. Action: This is not an error message and no action is required. The variable fields of the message text are: subsys Subsystem name string

Product Messages


OPS0018W Storage not released area bytes Modifiable: No Explanation: The product must not release some small amounts of CSA/ECSA storage obtained during product initialization. For example, the storage used for the subsystem control block can never be released. In addition, the product cannot release the storage used by the JES3, IMS, and subsystem interface routines. Active MVS dynamic exit routines also remain in CSA. The total amount of storage not released should always be small, no more than a few hundred bytes of CSA and approximately 16 KB of ECSA. In general, the product should only retain storage the first time it is started after an IPL. Action: Check the amount of storage not released by the product. If the storage amount is large, or if storage is retained even though the product has already been stopped and started since the last IPL, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: area Storage area OPS0019U Load module mod is not reentrant - contact systems programming Modifiable: No Explanation: The main product address space loaded a module during product initialization. The module was checked to verify that the module was loaded into non fetch-protected, key zero storage. The module was found to be loaded into fetch-protected storage. This check shows that the module was not link edited with the reentrant (RENT) attribute. Action: Check if the module shown in the error message is reentrant. Check the library containing the module. If you cannot determine the cause of the error, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: mod Module name OPS0020U Program stack CHANGKEY failed - contact systems programming

Product Messages


Modifiable: No Explanation: The product tried to change the protect key of a private area control block obtained during product initialization. The attempted change, using the CHANGKEY macro, failed. Action: Check the error messages associated with this problem. There may be one or more storage management error messages referring to the current problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. OPS0021S Abend error abcd at mod+x'mdoff' Modifiable: No Explanation: A serious abend occurred during product initialization, execution, or termination. The abend was not recoverable, and the product was forced to terminate. Action: Check the abend code and any related abend messages. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. Note the exact contents of the above error message and any other error messages associated with the product failure. The variable fields of the message text are: abcd Abend code mod Module name mdoff Module offset OPS0022U First three characters of the subsystem name must be 'OPS' Modifiable: No Explanation: Each copy of the product must use a unique subsystem ID string. The default subsystem ID is specified in the started task procedure or it can be specified in the START command used to start the product. In either case, the subsystem ID string must always be exactly four characters long, and the first three characters must be OPS. The last character must be alphabetic.

Product Messages


Action: Fix the subsystem ID string used to start the product by modifying the product started task procedure or by changing the product START command. Restart the product using a valid subsystem ID string. OPS0023U Subsystem name must be four (4) characters long Modifiable: No Explanation: Each copy of the product must use a unique subsystem ID string. The default subsystem ID is specified in the started task procedure or it can be specified in the START command used to start the product. In either case, the subsystem ID string must always be exactly four characters long. Action: Fix the subsystem ID string used to start the product by modifying the product started task procedure or by changing the product START command. Restart the product using a valid subsystem ID string. OPS0024U Last character of subsystem name must be alphabetic Modifiable: No Explanation: Each copy of the product must use a unique subsystem ID string. The default subsystem ID is specified in the started task procedure or it can be specified in the START command used to start the product. In either case, the subsystem ID string must always be exactly four characters long and end with an uppercase alphabetic character. Action: Fix the subsystem ID string used to start the product by modifying the product started task procedure or by changing the product START command. Restart the product using a valid subsystem ID string. OPS0025U Load module mod not copied - insufficient ECSA Modifiable: No Explanation: The amount of ECSA storage available was not sufficient to contain the specified module. Note that there are potentially many more product modules yet to be loaded. The product terminates on the

Product Messages


first occurrence of this condition. Action: Increase the amount of ECSA by increasing the value of the second subparameter of the CSA parameter in Logical Parmlib member IEASYSxx. Note that you must IPL to make this change effective. For more information, see the IBM Initialization and Tuning manual. The variable fields of the message text are: mod Module name OPS0026U Load module mod reload failed Modifiable: No Explanation: The product tried to reload one of the product modules. The reload process failed. Action: Check for any additional messages that may help explain why the reload failed. Check if an executable copy of the module is in the current STEPLIB or other load library. Contact CA Customer Support if the cause of the load failure cannot be determined. The variable fields of the message text are: mod Module name OPS0027U Current operating system not supported Modifiable: No Explanation: The product checked the host system and found that the host system is not running a supported version of z/OS. The minimum supported operating system level is currently z/OS Version 1 Release 11. Action: The product only supports z/OS Version 1 Release 11 and higher. A supported level of the operating system will have to be installed before the product can be used. OPS0028W ISPF services not available for request rules Modifiable: No Explanation: This message is preceded by two contents supervision messages

Product Messages


(CSV003I and CSV0028I) indicating that either the ISPLINK or ISPEXEC modules could not be loaded by the CA OPS/MVS main address space. This will not prevent CA OPS/MVS from running. However, ISPF services will not be available in request rules. Any attempt to use ISPF services under these conditions results in a return code of 20 from the ISPF service call. Action: Make the ISPF interface modules (ISPLINK and ISPEXEC) loadable by the CA OPS/MVS address space by placing them in the LPALIST, LINKLIST, or STEPLIB concatenations. OPS0029U Load module mod must be loaded in global storage Modifiable: No Explanation: The module loader performs some internal consistency checks to make sure that modules required to be in global storage are actually loaded there. This message indicates that the load options for the module indicated are incorrect. The product terminates on the first occurrence of this condition. Action: The customer cannot resolve this problem. Contact CA Customer Support for additional assistance. The variable fields of the message text are: mod Module name OPS0030W mem CLIST returned with code rc Modifiable: Yes Explanation: The product executes an initialization CLIST during product initialization. The initialization CLIST (OPSTART1) usually executes a member in SYS1.PARMLIB (by default member OPSSPA00) that sets a variety of product parameters. The initialization CLIST failed. The product tries to copy the CLIST execution error messages to the console to help diagnose the current problem. Action: Check the CLIST execution error messages and correct the current problem. The current problem is frequently caused by a misspelled product parameter name or an error in the CLIST PROC statement. The variable fields of the message text are: mem Member name

Product Messages


rc Return code OPS0031S ABEND abcd OCCURRED AT mod+mdoff DURING desc Modifiable: Yes Explanation: This error message describes an abend that occurred during CA OPS/MVS main address space initialization or termination processing. Action: There may be one or more error messages related to the current problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: abcd Abend code mod Module name mdoff Module offset desc Description (for example, PROCESS BLOCK FREE) OPS0032I mem REQUESTED SHUTDOWN - CODE = var1 Modifiable: Yes Explanation: The product initialization CLIST, REXX EXEC, or both requested immediate product shutdown by setting the first eight characters of the OPSTART1RESVAL parameter to SHUTDOWN. Action: Determine why the product initialization CLIST, REXX EXEC, or both requested immediate product shutdown. Correct the situation and restart the product. The variable fields of the message text are: mem Member name (OPSTART1) var1 Last 8 characters of OPSTART1RESVAL string OPS0033W PROCESS value (var) too low, increased to var Modifiable: Yes Explanation: The product has found that the initial process block count as set through the PROCESS parameter or its default value is too low. CA

Product Messages


OPS/MVS has increased the value to a more acceptable value. Action: Review the setting of the PROCESS parameter in the initialization CLIST (OPSTART1). For more information on the PROCESS parameter, see the CA OPS/MVS Parameter Reference. The variable fields of the message text are: var Old PROCESS parameter value var New PROCESS parameter value OPS0034I STOP command detected during initialization Modifiable: Yes Explanation: The product has detected a STOP command during early product initialization. The initialization CLIST (OPSTART1) may or may not have completed successfully. STOP commands issued after the completion of the initialization CLIST or REXX EXEC are not honored until initialization has completed. Action: None. This message is for informational purposes only. OPS0035S ESTAE service Error RC=rc, Reason code=rs Modifiable: Yes Explanation: The product tried to create an ESTAE recovery environment. The ESTAEX macro failed. Action: Check the error messages and the return code associated with this problem. There may be one or more ESTAE error messages referring to the current problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: service Current operation, create or delete ESTAE rc Return code rs Reason code OPS0036S service OF desc FAILED, RC=rc Modifiable: Yes

Product Messages


Explanation: This is a generic error message used to describe a wide variety of product initialization, execution, and termination errors. The message text provides the current operation and what the current operation was trying to do. Action: Check the error messages and the return code associated with this problem. There may be one or more error messages referring to the current problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: service Current operation, GETMAIN, FREEMAIN, ATTACH, and so on desc Description rc Return code OPS0037E desc service ERROR RC=rc Modifiable: Yes Explanation: Some type of process block pool error occurred during product initialization or product termination. The message text provides the current operation and what the current operation was trying to do. Action: Check the error messages and the return code associated with this problem. There may be one or more error messages referring to the current problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: desc Description service Process pool operation, create, delete, get, release, and so on rc Return code OPS0038S Invalid desc located at addr Modifiable: Yes

Product Messages


Explanation: The product found an invalid control block during product termination. The control block tag contained an invalid character string. Action: Check the error messages associated with this problem. There may be one or more error messages referring to the current problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: desc Description addr Address OPS0039E cnt process block(s) still in use Modifiable: Yes Explanation: The product uses a pool of stack control blocks to process messages and other events. The stack blocks are obtained and released as need be, by a variety of product routines. In some cases, a product routine may fail to release a process block. Action: No action is required to resolve this problem. The product will release all of the space used by the stack control blocks even if they appear to still be in use. If this problem recurs, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: cnt Number of process blocks OPS0040I msg Modifiable: Yes Explanation: This message is not an error message. The current message is used to display the output from the product initialization CLIST (OPSTART1) on the system consoles. Action: Although the current message is not an error message, the output from the product initialization CLIST is only sent to the product consoles if the initialization CLIST terminates with a non-zero return code. The CLIST messages should be carefully checked for

Product Messages


any error messages. Restart the product, if need be. Contact CA Customer Support if the problem (non-zero CLIST termination code) recurs. The variable fields of the message text are: msg Message or message text OPS0041H msg Modifiable: Yes Explanation: This message is not an error message. The current message is used to write the output from the product initialization CLIST (OPSTART1), and any REXX EXECs called from it, onto the system hardcopy log. Action: Check the hardcopy messages for any indication of a product initialization error. In most cases, there is no indication of an error. If an error has occurred, resolve the problem and restart the product. Contact CA Customer Support if the problem recurs. The variable fields of the message text are: msg Message or message text OPS0042I Restart after emergency product shutdown - errdesc (jb-asid) Modifiable: Yes Explanation: The product is restarting after an emergency product shutdown. The reason for the shutdown is described in this message. The JOBNAME and ASID in the message are possibly (but not definitely) related to the reason for the prior emergency shutdown. Action: None. This message is issued to document a prior emergency shutdown since it may not have been possible to issue message 3146 at that time. The variable fields of the message text are: errdesc Reason for prior emergency shutdown jb JOBNAME asid Address space identifier OPS0043O Restart after emergency product shutdown - errdesc (jb-asid) Modifiable: Yes

Product Messages


Explanation: The product is restarting after an emergency product shutdown. The reason for the shutdown is described in this message. The JOBNAME and ASID in the message are possibly (but not definitely) related to the reason for the prior emergency shutdown. Action: Automateable message to allow notification of prior emergency shutdown since it may not have been possible to issue message 3146 at that time. The variable fields of the message text are: errdesc Reason for prior emergency shutdown jb JOBNAME asid Address space identifier OPS0045E JES2 control blocks module has not been assembled Modifiable: Yes Explanation: The JES2 control blocks module has not been reassembled. Some JES2-related product functions will not operate correctly. This is not a fatal error condition. Action: Reassemble and relink the JES2 offsets module (OPJ2CB), and then restart CA OPS/MVS . OPS0046I Attempting to match a default JES2 offset table Modifiable: Yes Explanation: The JES2 control blocks module has not been reassembled. Attempting to match a default JES2 control block offset table. This is an informational message only. Action: None. OPS0047I JES2 default offset table found for JES2 release var1 Modifiable: Yes Explanation: A supplied default JES2 control block module has been found. CA OPS/MVS will use this table for all functions requiring JES2

Product Messages


offsets. Action: If your installation has modified any JES2 control blocks, using the default tables may result in errors when using any CA OPS/MVS JES2-related functions. If this is the case, you should assemble and link the CA OPS/MVS JES2 offsets module (OPJ2CB) and restart CA OPS/MVS or reload the JES2 offsets module dynamically. The variable fields of the message text are: var1 JES2 release level OPS0048E NO DEFAULT JES2 OFFSET TABLE AVAILABLE FOR JES2 RELEASE var1 Modifiable: Yes Explanation: No default JES2 control block module was found for the current release of JES2. Certain JES2-related CA OPS/MVS functions (for example, the OPSJES2() REXX function) will not be usable. Action: Assemble and link the JES2 offsets module (OPJ2CB). Then restart CA OPS/MVS or reload the module dynamically. The variable fields of the message text are: var1 JES2 release level OPS0049E INCOMPATIBLE VERSION OF JES2 OFFSET TABLE FOUND, REASSEMBLE var1 Modifiable: Yes Explanation: An incompatible version of the JES2 offset table has been detected. This may be the result of using a JES2 offset table assembled with an older release of CA OPS/MVS . Certain JES2-related CA OPS/MVS functions (for example, the OPSJES2() REXX function) are not usable. Action: Assemble and link the JES2 offsets module (OPJ2CB). Then restart CA OPS/MVS or reload the module dynamically. The variable fields of the message text are: var1 OPJ2CB Module name OPS0050O js evn DETECTED Modifiable: Yes

Product Messages


Explanation: The product detected JES2 or JES3 initialization or termination. This message is provided for informational purposes and can also be used to trigger one or more automation procedures. Action: No action is required in response to this message. However, this message can be used to activate one or more automation procedures. The variable fields of the message text are: evn Event OPS0051S JES subsystem name error Modifiable: Yes Explanation: An invalid job entry subsystem name was found in the operating system control blocks. CA OPS/MVS considers a JES subsystem name to be valid if it is JES2, JES3, or matches the name specified on the JESNAME product parameter. Action: Check the system generation parameters. Check if the JES subsystem ID is one of the supported values. Check if the JESNAME product parameter needs to modified. If the JES subsystem ID appears to be one of the supported values, and the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. OPS0052S cb control block error Modifiable: Yes Explanation: The product tries to locate and validate the job entry subsystem (JES2 or JES3) control blocks during product initialization. One of the control blocks cannot be located or is invalid. Action: Check the error messages associated with this problem. There may be one or more error messages referring to the current problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: cb Control block

Product Messages


OPS0053E js initialization not complete Modifiable: Yes Explanation: The product checked the current status of the job entry subsystem during product initialization. The job entry subsystem was either not found or was still initializing. Action: This may or may not be an error message. Verify that the reported JES status is in fact correct. If the actual JES status did not match the JES status reported by the product, check for any other error messages. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. OPS0054E JES3 not active Modifiable: Yes Explanation: The product checked the current JES3 status during product initialization. The job entry subsystem was either not found or was still initializing. Action: This may or may not be an error message. Verify that the reported JES3 status is in fact correct. If the actual JES3 status did not match the JES3 status reported by the product, check for any other error messages. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. OPS0055E JES3 consoles not active Modifiable: Yes Explanation: The product checked the status of the JES3 consoles during product initialization. The JES3 consoles are still initializing. Action: This may or may not be an error message. Verify that the reported JES3 console status is in fact correct. If the actual JES3 console status did not match the JES3 console status reported by

Product Messages


the product, check for any other error messages. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. OPS0064E JES3 cb LEVEL rel UNSUPPORTED Modifiable: Yes Explanation: The product checked the JES3 release level during product initialization. The host system JES3 release level is not supported by the product. Action: Verify that the reported JES3 release level is correct. The JES3 release used by the host system may or may not work with the current release of the product. Contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: cb Control block rel Release number or string OPS0070H MSF st Modifiable: Yes Explanation: The MSF initialization and termination routines use this message to report MSF status. MSF status information is provided during product initialization, termination and MSF restart. Note that an attempt to restart MSF is not allowed when a restart is already in progress. Since MSF restart can take a significant amount of time and involves multiple asynchronous processes, a restart may not be allowed for some time after a prior restart appears to be complete. A restart is only considered to be complete after this message is issued with the 'restart complete' status text. Action: Verify that the reported MSF status is correct. If the reported MSF status is correct, then the current message is normal. If the reported MSF status is incorrect, check for any related error messages. If possible, fix the problems identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are:

Product Messages


st Status OPS0071E MSF - service OF desc FAILED, RC=rc Modifiable: Yes Explanation: This is a generic error message used to describe a wide variety of MSF initialization, execution, and termination errors. The message text provides the current operation and what the current operation was trying to do. Action: Check the error messages and the return code associated with this problem. There may be one or more additional error messages referring to the current MSF problem. If possible, fix the problem identified by the error messages and restart the product. If the problem cannot be resolved, contact CA Customer Support to obtain additional assistance. The variable fields of the message text are: service Current operation, add, or delete

CA OPS/MVS® Event Management and Automation OPS MVS Event Managem… · Chapter 1: Messages and...

Documents

Transcript of CA OPS/MVS® Event Management and Automation OPS MVS Event Managem… · Chapter 1: Messages and...