ca ops/mvs® event management and automation ops mvs event...available sample aof rules and ops/rexx...

Release Notes Release 11.09.00

CA OPS/MVS® Event Management and Automation

Third Edition

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 may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, 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 © 2011 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

CA Technologies Product References

This document references the following CA Technologies products:

■ CA OPS/MVS® Event Management and Automation (CA OPS/MVS)

■ CA Mainframe Software Manager (CA MSM)

■ CA Spectrum® (CA Spectrum)

■ Product 2 Name

Contact CA Technologies

Contact CA Support

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

■ 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].

If you would like 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/support

mailto:[email protected]

http://www.ca.com/docs

http://www.ca.com/docs

Contents 5

Contents

Chapter 1: New Features 7

Available Sample AOF Rules and OPS/REXX Programs .................................................. 7

Samples Added for CA Products ................................................................ 7

Samples Added for CA OPS/MVS Components .................................................... 8

Samples Added for Other Vendor Products ...................................................... 8

Applications Added for z/OS Activities ........................................................... 9

AOF Parameter AOFMSGIDn ..................................................................... 10

BROWSECOF Parameter ......................................................................... 10

BROWSEMAXINUSE Parameter ................................................................... 10

CmdRespRemoteLog ............................................................................ 10

RULEPREFIX3 Parameter ......................................................................... 10

Hardware Services (HWS) ........................................................................ 11

Chapter 2: Enhancements to Existing Features 13

OPSHMC REXX Program ......................................................................... 13

Netview Message Table Entry .................................................................... 14

Restructured OPS/REXX Distributed Libraries ........................................................ 14

SMP/E FMID Name Change ................................................................... 14

OPS/REXX Functions ............................................................................ 14

OPSCAWTO Function ........................................................................ 15

OPSINFO Function .......................................................................... 15

OPSLOG Function ........................................................................... 15

Address MQ ................................................................................... 17

ADDRESS OPER ................................................................................ 17

SSMGA and SSM Enhancements .................................................................. 19

SSM Monitored Columns Added .................................................................. 20

OPSVIEW SOF ISPF Interface ..................................................................... 20

Parameters Changed ............................................................................ 21

Parameters Dropped ............................................................................ 22

Variables Dropped .............................................................................. 22

Demand Analysis Request ....................................................................... 22

Documentation ................................................................................ 24

CA HTML Bookshelf ......................................................................... 24

Appendix A: Messages 27


Chapter 1: New Features

This section contains the following topics:

Available Sample AOF Rules and OPS/REXX Programs (see page 7) AOF Parameter AOFMSGIDn (see page 10) BROWSECOF Parameter (see page 10) BROWSEMAXINUSE Parameter (see page 10) CmdRespRemoteLog (see page 10) RULEPREFIX3 Parameter (see page 10) Hardware Services (HWS) (see page 11)

Available Sample AOF Rules and OPS/REXX Programs

CA OPS/MVS distributes sample AOF rules and OPS/REXX programs that demonstrate various aspects of automating operations in a mainframe environment. These procedures adhere to the specific environment where they have been created and tested, and depending on the desired outcome, the provided automation may need to be modified from site to site.

The primary purpose of these rules and programs is to do the following:

■ Outline and demonstrate automated techniques that are needed across all data centers

■ Illustrate the effective usage of the automation tools that CA OPS/MVS provides, such as the OPS/REXX host environments, OPS/REXX functions, global variables, local variables, and much more

■ Provide the syntax of these applications that you can use as references and templates or starting points when you implement site-specific automation

Note: For more information on the sample rules and programs provided with CA OPS/MVS, see the appendixes in the User Guide.

Samples Added for CA Products

The following samples have been added for CA products.

■ CA MIM environment automation:

MIAIBR14

Causes tape volume dismounts to occur under CA MIA GLOBAL Tape Device Allocation Serialization for Tape Volumes that remain mounted in unallocated MIA-managed tape devices.


8 Release Notes

■ CA SYSVIEW environment automation:

SYSVCHCK

Demonstrates a coding technique you can use to obtain and interrogate various CA SYSVIEW related data and generate SMTP email alerts for any exceeded defined thresholds.

The specific CA SYSVIEW data you can obtain include:

– Coupling facility related data

– MQ related data

– Page data set related data

– WLM related data

■ CA DB2 DBM products:

PDT0170

Demonstrates logic needed to process data collector messages from the Execution Manager (Xmanager) component and invoke TSFBATCH Proc Unload to submit detector data to TSF.

Samples Added for CA OPS/MVS Components

The following samples have been added for the CA OPS/MVS components.

■ SSM Component

SSMQUERY

Demonstrates the logic needed to identify the table where the SSM resource resides, for SSM configurations that have STCs in multiple resource tables.

■ HWS Component

APIHWSV

Formats and issues HWS hardware event data (variables) as a multi-line WTO (MLWTO).

Samples Added for Other Vendor Products

The following sample has been added for other vendor products.

■ CICS automation

SHUTCICS

Demonstrates logic that can be used to initiate a controlled shutdown of a CICS region.



Applications Added for z/OS Activities

The following applications have been added for z/OS activities.

■ Processing cross-system events

EOJXSYS

Demonstrates the logic that can be used to obtain status or event data from another system such as the maximum condition code of a batch job in order to perform some automated action on a local system.

■ Processing hardware failures:

IEC606I

Processes the first occurrence of a VTOC error condition from the specific DASD device within a sysplex. All other identical issuances of this failure for the same VTOC error will not be processed for the next 10 minutes. This prevents reacting to the same event more than once. Create dynamic JCL to invoke the ICKDSF utility to reinitialize the VTOC when the IEC606I event occurs.

■ USS processes management:

SSMUSS1

Demonstrates a coding technique that can be used to monitor and control USS daemon server processes such as INETD within System State Manager (SSM).

TCPIPUSS

Demonstrates a technique used to query the statuses of z/OS Unix processes associated to a particular ASID.

■ zFS file system:

BPXI078D

Replies to WTOR generated by the OMVS zFS files system during initialization.

SHUTZFS

Initiates the shutdown of the OMVS zFS file system.

STARTZFS

Restarts the OMVS zFS file system after being stopped using the command F OMVS,STOPPFS=ZFS.

■ zOS system IPL:

IPLTIME

Issues various system commands after a system IPL.

AOF Parameter AOFMSGIDn

10 Release Notes

AOF Parameter AOFMSGIDn

The new AOF parameter AOFMSGIDn can specify a 1- to 10-character AOF special character message ID pattern. There are three AOFMSGIDn parameters named AOFMSGID1 to AOFMSGID3.

Note: For more information, see the Parameter Reference.

BROWSECOF Parameter

Control whether OPSLOG includes message events intercepted by the CICS Operational Facility.


BROWSEMAXINUSE Parameter

BROWSEMAXINUSE is a display only parameter that displays the maximum number of messages in the OPSLOG message area for the OPSLOG that is currently being used.


CmdRespRemoteLog

This parameter controls whether output for commands routed to a remote SOF server is also written to the remote server log. The response is always logged in the local SOF server regardless of this option.


RULEPREFIX3 Parameter

This parameter sets the high level qualifier (up to 10 levels and a maximum of 26 characters) of the tertiary rule sets. This parameter allows for a third level of ruleprefix, and should only be specified if RULEPREFIX and RULEPREFIX2 are already in use. This parameter will require more overhead than using RULEPREFIX alone, or RULEPREFIX with RULEPREFIX2 alone, but adds flexibility to the rules data set naming conventions. A duplicate rule set found using RULEPREFIX3 is ignored if a rule set with the same name is found using RULEPREFIX or RULEPREFIX2.


Hardware Services (HWS)


Hardware Services (HWS)

Hardware Services (HWS) provides the ability to automate hardware (HMC) functions. Through HWS, hardware event notifications are captured as CA OPS/MVS Generic API events. Rule-based automation can be designed for hardware events such as hardware message events, security events, and operating system message events. The CA OPS/MVS AOF Rules User Guide lists the hardware events and associated event data available through HWS.

HWS interfaces with the Hardware Interface Service. The Hardware Interface Service is CA common service software that provides hardware functions to CA products by utilizing underlying hardware service technology. Currently, the Hardware Interface Service utilizes IBM’s BCPii component to provide hardware functions. In order for HWS to provide hardware event notification, the Hardware Interface Service and its supporting services (BCPii) must be available and running on the same system as CA OPS/MVS.

Note: For more information, see the Installation Guide, Administration Guide, AOF Rules User Guide, and the Parameter Reference.


Chapter 2: Enhancements to Existing Features

This section contains the following topics:

OPSHMC REXX Program (see page 13) Netview Message Table Entry (see page 14) Restructured OPS/REXX Distributed Libraries (see page 14) OPS/REXX Functions (see page 14) Address MQ (see page 17) ADDRESS OPER (see page 17) SSMGA and SSM Enhancements (see page 19) SSM Monitored Columns Added (see page 20) OPSVIEW SOF ISPF Interface (see page 20) Parameters Changed (see page 21) Parameters Dropped (see page 22) Variables Dropped (see page 22) Demand Analysis Request (see page 22) Documentation (see page 24)

OPSHMC REXX Program

The OPSHMC sample REXX program has been enhanced to include the following four new keywords that retrieve or set a new group of attribute values:

■ ProfileReset

Allows specification of a reset activation profile name that the REXX program will use to match with one of the Reset Activation Profile names defined on your HMC.

■ ProfileLoad

Allows specification of a load activation profile name that the REXX program will use to match with one of the Load Activation Profile names defined on your HMC.

■ ProfileImage

Allows specification of an image activation profile name that the REXX program will use to match with one of the Image Activation Profile names defined on your HMC.

■ ProfileGroup

Allows specification of a group activation profile name that the REXX program will use to match with one of the Group Activation Profile names defined on your HMC.

Note: For more information, see the Administration Guide.

Netview Message Table Entry

14 Release Notes

Netview Message Table Entry

The Netview message table entry PDS member name OPSAUTO in SYS1.OPS.CNTL has been changed to OPSAUTOW in order to avoid a potential conflict with the CA OPS/MVS REXX function named OPSAUTO.

Note: For more information, see the Installation Guide.

Restructured OPS/REXX Distributed Libraries

The OPS/REXX distributed libraries have been restructured as follows:

opsmvshlq.REXX

Programs in this library cannot be modified by the end-user.

This library now contains OPS/REXX programs that support component functionality. The programs in this library are updated by installing PTFs, and upgrading to new releases.

opsmvshlq.SAMPLE.REXX

Programs in this library can be modified by the end-user.

This library replaces the OPSMVS.SAMPLES library. It contains for following:

■ Programs to support sample automated applications within opsmvshlq.SAMPLE.RULES.

■ Programs that provide logic templates for utilizing many of the automation tools within CA OPS/MVS and component programs.

Programs being utilized from this library can be copied into the end-users opsmvshlq.USER.REXX library.

SMP/E FMID Name Change

The SMP/E FMID naming standard for CA OPS/MVS has been changed from CIXvrnn to CCLXvrn.

Under this new standard the base product FMID for r11.9 (B9) has changed from CIXB900 to CCLXB90.

Note: For more information, see the Installation Guide.

OPS/REXX Functions

The following OPS/REXX functions have been enhanced.

OPS/REXX Functions


OPSCAWTO Function

The OPSCAWTO function has been updated to include an option for adding the CA OPS/MVS enterprise ID to the SNMP trap sent to the target IP address. This option will assist SNMP management software such as CA Spectrum to uniquely identify the source of the SNMP trap. CA Common Services for z/OS PTF T62T946 must be applied for the enterprise ID option to be effective.

Note: For more information, see the Command and Function Reference.

OPSINFO Function

The following capabilities have been added to the OPSINFO function:

■ var = OPSINFO(‘LPARNUM’)

Returns the LPAR number as a hexadecimal number. This number distinguishes the configuration from all other level-2 configurations provided by the same LPAR hypervisor.

■ var = OPSINFO(‘LCSSID’)

Returns the logical channel subsystem ID (LCSSID) as a hexadecimal number. There are four logical channel subsystems in one processor. Each processor can have up to 1024 CHPIDs.


OPSLOG Function

The OPSLOG function has been updated to in include both basic and expanded formats.

The Basic format are as follows:

■ opcode

■ Select which message to retrieve

■ Indicate the maximum number of message

■ ID filer.

OPS/REXX Functions

16 Release Notes

The Expanded formats are as follows:

■ opcode

■ Time, date, message number

■ Message count

■ Log name

■ Job name

■ Message ID

■ System Name

■ User

■ Colors

■ Rule set

■ Event type

■ ASID

■ Exit type

■ Scan text

■ Column display

■ Direct the output

■ Prefix name

■ System name of the remote or local MSF system

■ Wait time


Address MQ


Address MQ

The Address MQ has been enhanced.

■ The following commands have been added:

– SET

The ADDRESS MQ SET command sets the queue attributes. This command has the following syntax:

SET CONHANDLE(varHCONN) OBJHANDLE(varHOBJ) ATTRIBUTES(attrs) STEM(varSTEM)

■ All attributes are read from compound variable.

■ STEM is optional.

■ CONHANDLE and OBJHANDLE identifies the object.

– INQUIRE

The ADDRESS MQ INQUIRE command inquires which attributes are set for the queue or queue manager. This command has the following syntax:

INQUIRE CONHANDLE(varHCONN) OBJHANDLE(varHOBJ) ATTRIBUTES(attrs)

STEM(varSTEM)

■ All attributes are stored in compound variable.

■ STEM is optional.

■ CONHANDLE and OBJHANDLE identifies the object.

■ The OPEN command has been enhanced to include the QUEUE, QMGR, and OPTIONS.

The ADDRESS MQ OPEN command has the following syntax:

OPEN {QUEUE(name)|QMGR(name)} OPTIONS(opts) CONHANDLE(varHCONN)

OBJHANDLE(varHOBJ)

– QMGR(name) - Defines the queue manager name. Mutually exclusive with QUEUE(name).

– OPTIONS(SET,INQUIRE) - Specifies options for setting and inquiring your access or other options.


ADDRESS OPER

CONTYPE keyword of the CA OPS/MVS ADDRESS OPER host command now includes the XTRACONS value. CA OPS/MVS selects the first available extra extended console. Extra extended consoles are controlled by the EXTRAEXTCONSOLES parameter.

ADDRESS OPER

18 Release Notes


SSMGA and SSM Enhancements


SSMGA and SSM Enhancements

SSMGA and SSM have been enhanced as follows:

■ The SSMGA monitor applications, 4.11.2 and 4.11.G, have been enhanced to provide three display modes: edit, view, and browse. All modes allow line commands.

Edit mode (Default)

Allows all the functions of the application.

View mode

The same as edit except that all type-over changes must be confirmed before execution.

Browse mode

Does not allow any type-over changes.

The default mode can be set for each user with the general settings OPSVIEW application 0.1.

■ OPSVIEW 4.11.2 now provides:

– INACTIVE movable resource copies are highlighted as SSMGA CNTL to denote that they are under the control of SSMGA.

– The SSM Resource Filters panel includes the ability to filter resources by Move Mode.

■ The SSMGAOPR MGROUP command for moving groups of resources now includes a DESIRED operand. This allows the user to specify a desired state for those group members on their destination system.

■ SSMGAOPR DGROUP command for displaying group sizes will now also display the individual members of a group when the operand MEMBERS is included.

■ Messaging has been improved to indicate when a system becomes the GLOBAL system.

■ When a new SSM global is assigned, resource movement is now deferred until global status table is rebuilt. This addresses the thrashing issue when multiple systems are being shutdown and IPLed in staggered manner over short period of time.

■ Error reporting has been improved when updating movable resource entries on the non-SSMGA owner system.

■ Error reporting has been improved when using SSMGAOPR to move a resource or group of resources to:

– An undefined system

– An inactive system

– A non-MSF connected system

SSM Monitored Columns Added

20 Release Notes

– A system not in primary + alternate system list

■ A new utility has been added to update the primary system, move mode, and system list for a movable resource on every designated system.

SSM Monitored Columns Added

SSM can monitor up to five additional columns as specified by the user in the following parameters:

■ SSMMONITOREDCOL1





You can modify these parameters using the following methods:

■ The OPSVIEW panel 4.1.1

■ The OPSPRM OPS/REXX function

■ The OPSPARM POI Command Processor

If a column name specified in one of these parameters exists in any of the tables currently being managed by SSM, it will be set as a monitored column. If SSMAUDIT is set to YES, all changes to this column will be logged to OPSLOG using the trace message OPS7914T. Changes to monitored columns also trigger global events. A user-defined exit can be written to react to these changes.

Note: For more information, see the Parameter Reference and the User Guide.

OPSVIEW SOF ISPF Interface

The OPSVIEW SOF ISPF interface has been enhanced by adding an ACTivate line command to the SOF switch file display that issues an SOF ACTIVATE command for a selected switch file.

Confirmation of the requested command is always required.

Note: For more information, see the OPSVIEW User Guide.

Parameters Changed


Parameters Changed

The command queue entries for the following parameters have been moved above the bar into 64-bit storage:

■ OSFQUE

New Default: 1700

The OSFQUE default value has increased from 1024 to 1700 queued commands. The new value exploits the 64-bit storage.

■ OSFTSLQUE

New Default: 1700


■ OSFTSPQUE

New Default: 1700


■ USSQUE

New Default: 1700


Parameters Dropped

22 Release Notes

Parameters Dropped

The following parameters were removed in this release:

■ BYPASSINITEOM

This parameter did prevent EOM rule processing for JES initiators but did not prevent the allocation of a process block. Prevention of process block depletion was the original intent of this parameter.

■ INITHCS

This parameter determined whether CA OPS/MVS has installed and enabled z/OS Health Checks for the product. Now this will automatically occur on CA OPS/MVS startup. To provide consistency with other CA products with health checks we removed this parameter-based capability to temporarily deactivate or permanently delete health checks as this is already provided by the IBM Health Checker infrastructure. Customers can do this for individual or all product checks through the HZSPRMxx PARMLIB member or by issuing modify commands to the Health Checker started task.

Note: The default for this parameter was that z/OS Health Checks was installed and enabled.

■ OCMAXTIME

This parameter controlled the maximum time a command console could be allocated for command response collection. The value specified could cause a conflict with specified or default CMDWAIT/WAIT operands of OPSCMD or Address OPER.

Variables Dropped

The following variable was removed in this release:

■ SEC.OPAURQTY

Demand Analysis Request

The following demand analysis requests (DARs) were incorporated:

16566432:2, 19454426:1

Adds the ability to specify up to five additional SSM monitored columns using parameters SSMMONITOREDCOL1 through to SSMMONITOREDCOL5.

16953293-01

New applications provided for starting and stopping USS file systems.

Demand Analysis Request


17107583:1

SSMGA has been enhanced through a new rule to let the global system transfer automatically to the next highest SSMPRIORITY.

17565607-01

mproved error reporting when problems encountered with moving a resource or group of resources to another system.

17573061-01

Improved error reporting when attempting to update movable resource entries on a non-SSMGA owner system.

18127752:01

Displays the maximum number of messages in the OPSLOG message area for the current in-use OPSLOG.

18978790:1

Adds OPSINFO support for LCSS ID (logical channel subsystem ID).

DAR 19129300

Moved the OPJ2CB linkage editor statements to JES2ASM member in OPS.CNTL. This change eliminates the need to edit the OPJ2CB source code member when creating suffixed versions.

For more information, see the CA OPS/MVS Installation Guide.

19266145:3

OPSVIEW now supports a FIND command for an System State Manager resource name from the 4.11.2 panel.

19558495:1

Adds an ACTivate line command to the SOF switch file display that issues an SOF ACTIVATE command for a selected switch file.

19715060-01

The CA OPS/MVS rule OPHCRULE for use with the CA Health Checker Common Service is now enabled automatically after AOF initialization is complete.

Documentation

24 Release Notes

19902789:1

The explanation text for the Process Block health check has been enhanced to provide the time and date of the last process block failure plus information on how to reset the health check once the underlying problem is corrected.

20079223:1

Controls whether parameter message events intercepted by CICS Operation Facility are written to the OPSLOG.

20283401:1

Added the Switch Operation Facility to control whether commands routed to a remote SOF server can also respond to the remote server log.

Documentation

This section contains topics related to documentation enhancements.

CA HTML Bookshelf

This release contains the CA HTML bookshelf, which is an HTML help system that provides access to all deliverables in the product documentation set in both HTML and PDF. HTML provides robust online viewing and search capabilities, while PDF provides a print-friendly option.

The HTML bookshelf features include:

■ A single help screen that displays all documentation for this release.

■ An all-in-one search tool that searches the entire documentation set and returns matches found in both the HTML and PDF formatted documentation, without the need for a specialized .PDX index file.

■ Additional links for using the bookshelf, downloading Acrobat Reader, and contacting CA Technologies.

Note: You must have Adobe Reader 8 or above to view the PDF files in the bookshelf.

Documentation


Search the Bookshelf

The bookshelf includes a search facility that helps you locate information throughout the set.

To search the bookshelf

1. Enter your search criteria in the Search field in the upper right corner of the bookshelf and press Enter.

The search returns HTML results listed by topic and PDF results listed by guide. The results are sorted by date so that the most recently updated topics or PDFs appear at the top of the list. To find a topic in a PDF, open the PDF and view the list of topics within the PDF that match the search criteria.

2. (Optional) Click Sort by Relevance.

The list is reordered so that the HTML topics or PDFs that contain the most matches appear at the top of the list.


Appendix A: Messages

This section lists the new and changed messages in Release 11.9.

Note: For information about each message, see the Message Reference.

OPSH165I

Based on this information, the current high watermark percentage for process block usage is &THRPCT. The exception threshold percentage is &THRPCT.

Reason:

The PROCESS parameter determines how many process blocks are allocated in the extended private area of the CA OPS/MVS main address space when the CA OPS/MVS address space initializes. The value of the SSEXEXITHICOUNT parameter indicates the high water mark for the number of used process blocks.

Allocating the right number of process blocks is critical. The number cannot be too low, because each event processed by CA OPS/MVS requires its own process block. If a process block is not available, then CA OPS/MVS will not capture or respond to the event, which in turn could lead to undesirable results on your system. Furthermore, setting the value too high has its own implications; the number of process blocks you specify may use so much virtual storage that CA OPS/MVS fails to function correctly.

Currently there are enough process blocks for CA OPS/MVS events.

Action:

This message is informational only.

Documentation

28 Release Notes

OPSH167I

Based on this information, the current high watermark percentage for process block usage is &ACTPCT. The exception threshold percentage is &THRPCT.

Reason:

The PROCESS parameter determines how many process blocks are allocated in the extended private area of the CA OPS/MVS main address space when the CA OPS/MVS address space initializes. The value of the SSEXEXITHICOUNT parameter indicates the high water mark for the number of used process blocks. SSEXEXITFAILURES parameter displays the number of failed attempts to allocate a process block.

You are receiving this message because the number of process blocks has not changed after &VAR1 hours since the first exception occurred. There are not enough process blocks for CA OPS/MVS events or requests. Based on the current value of parameters SSEXEXITHICOUNT and threshold value, a reasonable new value for PROCESS would be &VAR2.

To modify the value of the parameter

1. Use the OPSPRM function with the SET keyword:

OPSPRM('SET','PROCESS','&VAR3 ')

2. Restart CA OPS/MVS.

The PROCESS parameter can only be set at product initialization. Possible number of process blocks can be between 10 and 250. Always discuss the PROCESS parameter with CA Customer Support before setting it to a value higher than 100.

To reset high water mark for the number of used process blocks SSEXEXITHICOUNT to zero, use OPSVIEW option ‘Set/Display product parameters’ or OPSPRM function with the SET keyword OPSPRM('SET',' SSEXEXITHICOUNT ',0). You could rerun health check in CA SYSVIEW with RUN command or reset it with REF command to update heath check status.

To change the delay between the first exception and receiving this message, use health check user parameter ‘AGE(nn)’, where nn is number of hours. Default value is 6.

Contact CA Customer Support if you have any problem.

Action:

This message is informational only.

Documentation


OPSH168W

Based on this information, the current high watermark percentage for process block usage is &ACTPCT. The exception threshold percentage is &THRPCT. No failed attempt to allocate a process block has occurred.

Reason:

The PROCESS parameter determines how many process blocks are allocated in the extended private area of the CA OPS/MVS main address space when the CA OPS/MVS address space initializes. Allocating the right number of process blocks is critical. The number cannot be too low, because each event processed by CA OPS/MVS requires its own process block. If a process block is not available, then CA OPS/MVS will not capture or respond to the event, which in turn could lead to undesirable results on your system. Furthermore, setting the value too high has its own implications; the number of process blocks you specify may use so much virtual storage that CA OPS/MVS fails to function correctly. The value of the SSEXEXITHICOUNT parameter indicates the high water mark for the number of these process blocks. This health check provides a warning that CA OPS/MVS has reached the exception threshold value during the current life of the product or since the high water mark was last reset.

Action:

It is critical that a process block is available for any event or request that passes through the CA OPS/MVS AOF event processing, even if a rule does not process the event. A frequent cause of process block depletion, particularly as the value of the SSEXEXITHICOUNT parameter gets closer to &VAR1, is inefficiently coded automation.

To identify such automation

1. Access OPSVIEW option 4.1.1

2. View the SSEXEXITHIDATE and SSEXEXITHITIME parameters.

These parameters determine the date and time of the high process block usage when the SSEXEXITHICOUNT value was reached.

This high water mark count was reached on &VAR2 at &VAR3. Using the OPSLOG, locate the date and time as indicated using these parameters. From the OPSLOG command line issue ‘DISPLAY TRACE1 RULE COUNT DATE TIME’, attempt to identify the CA OPS/MVS application or applications (rules, and OPS/REXX programs) that were executing during this high usage period. Common application bad practices are creating logic within rules to ‘trigger’ other rules, such as having a MSG rule issue a command to trigger a CMD rule. Additionally, the triggering of REQ rules from within rules (through the ADDRESS OSF “OPSREQ…”) instead of triggering an OPS/REXX program can cause process block depletion. Contact CA Support if technical assistance is needed in reviewing the OPSLOG to identify process block usage issues.

If no applications can be modified in the short-term, increase the value of the PROCESS parameter. Based on the current value of parameter SSEXEXITHICOUNT and threshold value, a reasonable new value for PROCESS would be &VAR4.

Documentation

30 Release Notes


1. Use the OPSPRM function with the SET keyword.

OPSPRM('SET','PROCESS',' &VAR5 ')




Documentation


OPSH169W

The high watermark for process block usage SSEXEXITHICOUNT has reached the number of allocated process blocks PROCESS, moreover failed attempt to allocate a process block has occurred.

Reason:

The PROCESS parameter determines how many process blocks are allocated in the extended private area of the CA OPS/MVS main address space when the CA OPS/MVS address space initializes. Allocating the right number of process blocks is critical. The number cannot be too low, because each event processed by CA OPS/MVS requires its own process block. If a process block is not available, then CA OPS/MVS will not capture or respond to the event, which in turn could lead to undesirable results on your system. Furthermore, setting the value too high has its own implications; the number of process blocks you specify may use so much virtual storage that CA OPS/MVS fails to function correctly. The value of the SSEXEXITHICOUNT parameter indicates the high water mark for the number of these process blocks. The SSEXEXITFAILURES parameter displays the number of failed attempts to allocate a process block from the process block pool because there were no process blocks available.

This health check provides a warning that CA OPS/MVS does not have process blocks available for any event or request.

Action:

It is critical that a process block is available for any event or request that passes through the CA OPS/MVS AOF event processing, even if a rule does not process the event. A frequent cause of process block depletion, particularly as the value of the SSEXEXITHICOUNT parameter gets closer to &VAR1, is inefficiently coded automation.

To identify inefficiently coded automation

1. Access OPSVIEW option 4.1.1

2. View the SSEXEXITHIDATE and SSEXEXITHITIME parameters

These parameters help to determine the date and time of the high process block usage when the SSEXEXITHICOUNT value was reached. This high water mark count was reached on &VAR2 at &VAR3.

3. Use SSEXEXITFAILDATE and SSEXEXITFAILTIME parameter to display the date and time when the last process block allocation failure occurred.

Last block allocation failure occurred on &VAR4 at &VAR5.

4. Using the OPSLOG, locate the date and time as indicated by these parameters. From the OPSLOG command line issue

‘DISPLAY TRACE1 RULE COUNT DATE TIME’

5. Attempt to identify the CA OPS/MVS application or applications (rules and OPS/REXX programs) that were executing during this high usage period.

Documentation

32 Release Notes

Common application bad practices are creating logic within rules to trigger other rules, such as having a MSG rule issue a command to trigger a CMD rule. Additionally, the triggering of REQ rules from within rules (ADDRESS OSF “OPSREQ…”) instead of triggering an OPS/REXX program can cause process block depletion. Contact CA Support if technical assistance is needed in reviewing the OPSLOG to identify process block usage issues.

SSEXEXITFAILURES parameter, which displays the number of failed attempts to allocate a process block, is &VAR6. Increase the value of the PROCESS parameter. Based on the current value of parameters SSEXEXITHICOUNT and threshold value, a reasonable new value for PROCESS would be &VAR7.


1. Use the OPSPRM function with the SET keyword

OPSPRM('SET','PROCESS',' &VAR8')




OPS3268E

Status request name var1 is invalid.

Modifiable: Yes

Reason:

CA OPS/MVS does not recognize the name of the component for which status has been requested.

Action:

Specify a defined component status name.

The variable fields of the message text are:

var1

Specifies the status component name.

Documentation


OPS3269I

SSMGA: OPS=var1 MSF=var2 SSM=var3 SSMPLEX=var4 GBL=var5 PRI=var6

Modifiable: Yes

Reason:

This informational message is issued in response to a MODIFY OPSx,STATUS(SSMGA) and indicates basic status of CA OPS/MVS product SSMGA components.

Action:

None. This message is for informational purposes only.

The variable fields of the message text are:

var1

CA OPS/MVS product status

var2

MSF component status

var3

Stateman mode (Same as OPSINFO)

var4

SSMPLEXNAME (name/NONE). Used in SSMGA.

var5

SSMACTIVEGLOBAL value (Y/N). Used in SSMGA.

var6

SSMPRIORITY (0-1999). Used in SSMGA.

ca ops/mvs® event management and automation ops mvs event...available sample aof rules and ops/rexx...

Documents