Step 5A: Configure NetView DSIPARM Data Set

SysOps ProcOps
✓ ✓

Sample: INGSTGEN

A sample is provided for this step in the INGSTGEN member of the SINGSAMP library. Copy the contents of INGSTGEN to your CxxSTGEN or CxxSTUSR and configure it to match your installation. See the INGSTGEN sample for further details.

Copy any DSIPARM and SINGPARM member that you need to configure into a data set allocated in DSIPARM before the SMP/E-maintained NetView DSIPARM and SA z/OS target libraries and edit it there.

Then change the following members in the copied NetView DSIPARM data set:

NetView Style Sheet
Tower Statements: The various SA z/OS components or environments are activated with the following TOWER.SA statements.
SysOps
This enables application or more general resource automation.
ProcOps
This enables Processor Operations.
GDPS®
This enables GDPS to run under SA z/OS. Use this definition regardless of the specific GDPS product that is running (GDPS Metro, GDPS HM, GDPS XRC or GDPS GM).

Additionally the following GDPS subtowers are available to distinguish between the GDPS product running on the system:

PPRC
For GDPS Metro (formerly named GDPS/PPRC)
HM
For GDPS HM (formerly named GDPS/PPRC HM)
XRC
For GDPS XRC (formerly named GDPS/XRC)
GM
For GDPS GM (formerly named GDPS/GM)
Furthermore, code one of the following indicating whether or not this is the production versus K-system:
  • PROD for a production system
  • KSYS for a K-system
This information is used by SA z/OS to pick up the appropriate definition members that vary for the GDPS controlling system (K system) and the production system. For example, the K system constitutes a subplex of its own and must therefore use a different XCF group name.
GDPSSAT
This statement enables the GDPS Satellite support required in a GDPS Continuous Availability (GDPS AA) environment.
See the INGSTGEN sample for further details about the SA tower statements.
To enable SA z/OS, make sure that the following TOWER statements are activated in the NetView style sheet (that is, uncomment them): 
TOWER =  SA
TOWER.SA  = SYSOPS
Kanji Support: If you plan to use Kanji support make sure that you update the NetView style sheet as follows:
  1. transTbl =DSIKANJI must be specified.
  2. transMember =CNMTRMSG must be uncommented.
For more details, refer to the chapter Installing the National Language Support Feature in IBM Z® NetView Installation: Configuring Additional Components.

Timer Catchup Processing: SA z/OS requires init.TIMER=NO for its timer catchup processing. If you do not have any timers defined in the SA z/OS policy or none of the defined timers has the CATCHUP=YES option, you can code init.TIMER=YES to cause your saved timers to be restored at NetView startup time.

Refer to the NetView documentation for details about configuring the NetView style sheet.

AOFMSGSY (optional)
If you have renamed any automation tasks in AOFOPFxx, you will need to make corresponding changes to the AOFMSGSY member.

If you want to define your own synonyms, you may use INGSYNU member which is automatically included from AOFMSGSY. By using this member, you can avoid changing the product supplied AOFMSGSY member.

Copy and edit the AOFMSGSY member that resides in ING.SINGPARM and do the following:
  1. If you want to define actions for messages that the SA z/OS NetView Automation Table does not trigger any actions for, you can use the symbol %AOFALWAYSACTION%.

    This synonym contains the action statement that is used for all messages in a Begin-End block that SA z/OS does not trigger any action for. The default, NULL, is that no action will be taken and the message does not continue to search for further matches in the same AT.

    See Generic Synonyms: AOFMSGSY in IBM Z System Automation Customizing and Programming for a description of these synonyms.

NetView Automation Tables
If you need to build NetView Automation Tables (ATs) in a way that is not supported by the customization dialog, you can use the INGMSGU1 fragment for user entries. INGMSGU1 is included before INGMSG02. You can also use the INGMSGU2 fragment for user entries. INGMSGU2 is included after INGMSG02.
If you want to have additional entries that are only valid to your environment, you can use either a separate AT (specified in the customization dialog) or use one of the user includes. The following shows the AT structure: 
INGMSG01
    │
    ├── %INCLUDE AOFMSGSY
    │ │
    │ └── %INCLUDE INGSYNU      
    │ 
    ├── %INCLUDE INGMSGU1
    │
    ├── %INCLUDE INGMSG02
    │
    └── %INCLUDE INGMSGU2
Message Revision Table
During the build of the automation control file, a NetView Revision Table is being built by the customization dialog. For more information about activating the built Message Revision Table (MRT), see the topic AT/MRT/MPF Build and Activate in IBM Z System Automation User's Guide.
INGXINIT
The communication DST initialization processing will read data that is specified in the DSIPARM member INGXINIT. Copy and edit the INGXINIT member, which resides in ING.SINGPARM. Uncomment the following parameters and specify your values:
FUNCTIONLEVEL
System Automation user function level. You can specify a value up to 5-digit number in the range 0 - 65535. The default value is 0.

This parameter is used to control what capabilities the agent is allowed to perform when operating in a System Automation sysplex environment with systems at different service levels.

Refer to Function levels for a detailed description and when to use function levels.

GRPID
2-byte XCF group ID. Default is blank. The value must be the same as specified for GRPID in the corresponding member HSAPRMxx.
PLEXID
2-byte suffix used to build the extended XCF communication group with the name INGPX$xx. For suffix xx you can specify all alphanumeric characters except the suffix $$ (#@ are acceptable, for instance). If PLEXID is not specified, the automation agent is not a member of the extended XCF communication group.

If you are running more than one NetView on your system, they cannot be in the same extended XCF communication group. Either leave the PLEXID commented out or make sure that the PLEXIDs used for the NetViews on the same system are unique.

DIAGDUPMSG
This is the number of message buffer IDs that are validated before send and after receive. This is for diagnostic purposes. A value for nnnnn may be chosen between 0 (no validation) and 99999. The default is 0 and performance decreases with larger values.
LIFECYCLE
This parameter allows you to prepare for Life Cycle Recording in order to debug automation manager-related problems. Normally, SA z/OS Service will advise when Life Cycle Recording should be enabled.

The value of nnnn defines the size of the data space in number of megabytes (1 through 2097). A value of 500 is recommended and is sufficient in most situations.

The value of dataset specifies the fully-qualified DSN to be used when offloading the dataspace to disk.

Note: nnnn and dataset must be separated by a semicolon without intervening blanks The total length of 'nnnn;dataset' can be a maximum of 60 bytes.
LOGSTREAM
This parameter defines if the NetView agent should establish a connection to the system logger at initialization time. If NO is specified the agent does not establish a connection. The default is YES which causes the agent to connect to the following log streams:
  • HSA.WORKITEM.HISTORY
  • HSA.MESSAGE.LOG
You may also specify the value GRPID. This allows you to have separate log streams per subplex. If GRPID is specified and the value of the GRPID keyword is not blank, the agent connects to the following log streams:
  • HSA.GRPxx.WORKITEM.HISTORY
  • HSA.GRPxx.MESSAGE.LOG
If the value of the GRPID keyword is blank the LOGSTREAM keyword defaults to YES.
Note: Both values, LOGSTREAM and GRPID, must be the same as in the PARMLIB member HSAPRMxx that is used to start the related automation manager.
PPI
This needs to be set to YES to establish a connection to the end-to-end automation adapter.
PPIBQL
The number of elements in the PPI queue—this indicates how large the response to a request may be. It should be greater than the number of queue elements that you expect to be returned. The default is 3000.
All input requests flow into the PPI queue, so the buffer queue limit, PPIBQL, should match this. If this limit is exceeded (that is, the queue limit is too small):
  • The automation adapter might not be able to send any further requests to the SA z/OS agent, and the agent issues a JNI exception with return code 1735: 
    	INGX9820E JNI function ingjppi failed with return code 1735.
  • The SA z/OS agent might not be able to send any responses to the automation adapter, and an AOF350E message is issued.

If you receive these error messages, increase the buffer queue limit.

Requests are lost, but the end-to-end automation operator will receive exception reports. For more details see IBM Z System Automation End-to-End Automation.

All parameter values must match with the respective parameters in the PARMLIB member HSAPRMxx of the automation manager.

You can specify a GRPID to indicate that a subset of the members of an actual z/OS sysplex is defined in a sysplex group. If specified, the ID may contain 1 or 2 characters. Valid characters are A–Z, 0–9, and the national characters ($, # and @).

The GRPID is prefixed with the string INGXSG to construct the XCF group name that is used for cross system synchronization, for example, INGXSGxy.

If you do not specify a GRPID, the default group name INGXSG is used.

Note: Syntax errors are reported by a message with error code ERRCODE=564. Any syntax errors will stop the initialization process and therefore no automation will be possible.

The following parsing syntax applies:

  • Data can only be specified via key-value-pairs.
  • One or more parameters may be specified on one line.
  • Each record will be parsed for the keyword.
  • Parsing will be stopped and any further input data will be ignored after all keywords listed above are found.
  • If the same parameter is specified multiple times, the last one is used.
  • For any keyword that was not specified, the default value is blank.
  • No blanks between parameters and values are allowed.
  • The syntax of a keyword is equal to the syntax of the parmlib member HSAPRMxx.

An example of a valid syntax is:

GRPID=XY,LIFECYCLE=500,LOGSTREAM=YES

An example of an invalid syntax is:

GRPID = 34 , LIFECYCLE = 500