INIT

Purpose

The INIT statement defines the run-time options for processing requests that are sent to HCL Workload Automation for Z from a PIF application. The parameters specified in the INIT statement override the settings specified in the INIT request of the PIF application. INIT is defined in the parameter file identified by the EQQYPARM DD statement in the JCL of the PIF application and in the parameter file identified by the EQQPARM DD statement in the server procedure.

Note: If you plan to run PIF applications many times per day from a long-running non-TSO address space (for example, NetView®), to prevent a storage shortage do not specify the EQQYPARM ddname. Instead, specify the parameters either in the PIF application or in the controller INTFOPTS initialization statement. When you run a PIF application by specifying the EQQYPARM ddname, a TSO environment must be established each time and some of the resources remain allocated until the task ends. This might lead to a storage shortage, if the commands are issued many times.

Format


1  INIT?  ADOICHK (
2.1! N
2.1 Y
1 )?  ADOPSEG (
2.1 VERS0
1 )?  CALENDAR (
2.1 calendar name
1 )?  CWBASE (
2.1 base year for PIF century window
1 )?  DATINT (
2.1! N
2.1 Y
1 )?  HIGHDATE (
2.1 991231
2.1! 711231
2.1 cccccc
1 )?  LUNAME (
2.1 LU name
1 )?  OIWSNAME (
2.1! ERROR
2.1 IGNORE
1 )?  REMHOSTNAME (
2.1 hostname
2.1 IP address
1 )?  REMPORTNUMBER (
2.1! 425
2.1 TCPIP port
1 )?  SUBSYS (
2.1 subsystem name
1 )?  TRACE (
2.1! 0
2.1 4
2.1 8
1 )?  USRLEV (
2.1! 14
1 )?  VERADGRD (
2.1 FULL
2.1 YES
2.1! NO
1 )?  VERSRWSN (
2.1 FULL
2.1 YES
2.1! NO
1 )

Parameters

ADOICHK(Y|N)
Use this option to specify whether or not you want AD/OI consistency checks to be made every time an application is deleted or modified.

Consistency checks involve looking in the application description database for matches for all the operator instructions in the application. Any operator instructions without a match are deleted.

The checks are made immediately after the application description PIF action has completed with a zero return code.
Y
Consistency checks are performed whenever an application description record is deleted or replaced using the PIF.
N (default)
Consistency checks are not performed.
ADOPSEG (VERS0)
PIF applications can use this option to keep the values for certain fields in the operation part of application descriptions at a Replace.

The ADOPSEG can be used for programs that do not define the fields following the ADOPWSINFO fields in the ADOP segment, and that do not keep the value in the empty field at the segment end.

When updating an application description, Replace, the fields following the ADOPWSINFO in the ADOP segment are not updated, their current values are kept. When creating an application description, or adding an operation to an application description, the fields following the ADOPWSINFO fields in the ADOP segment are given default values.

CALENDAR(calendar name)
Specifies the HCL Workload Automation for Z default calendar. You can specify a name from 1 to 16 characters, referencing a calendar in the calendar database.

This parameter is used by the programming interfaces only if no calendar is specified in the application description. It is used by programming interfaces to validate that the EVERY options specified for an application run cycle are consistent with the application calendar work day end time.

If DEFAULT is specified and no calendar with the name DEFAULT exists, all days are considered work days and the work day end time is set to 00.00.

If this parameter is not set or the specified calendar does not exist in the calendar database, the validation on the EVERY options is not performed. Any inconsistencies in the definition will be highlighted by a warning message during long-term plan creation or modification.

CWBASE(base year for PIF century window)
Specifies the origin for the century window used by the PIF application. Valid values are 00 through 99. If you specify 00, HCL Workload Automation for Z uses the same date representation in communication with the PIF application as in the dialog. If you specify 72, the HCL Workload Automation for Z internal date representation will be used. This parameter affects the date representation for all dates except the default valid-to and out-of-effect dates. The default dates are determined by the value of the HIGHDATE parameter or the PIFHD parameter of the INTFOPTS statement.

For more information about the base year, see the PIFCWB parameter of the INTFOPTS statement.

The CWBASE parameter overrides the global setting of the PIFCWB parameter of the INTFOPTS statement.

DATINT(Y|N)
The keyword allows updates of the same record by different users to be serialized as soon as the request is handled by the PIF code. The default value, N, serializes the update of the same record only immediately before the VSAM access and this could lead to unpredictable results for a PIF user. Specify Y if you want to obtain the serialization at PIF level. This means that if a PIF program containing an update request starts, and in the meantime, another PIF program runs with the same record update request, the first one will be rejected and its update will not be handled. Note that the user IDs of the two programs must be different, otherwise is not performed.
HIGHDATE(991231|711231|cccccc)
Specifies the high date presented to the PIF application in the default valid-to fields of applications and run cycles. For more information about the high date, see the PIFHD parameter of the INTFOPTS statement.
You can select one of these values:
991231
Use this if you have specified the CWBASE parameter as 72.
711231
As displayed in the HCL Workload Automation for Z dialog. This date represents 31 December 2071.
cccccc
A 6-character string to symbolize the default valid-to date, for example DEFHID. The string cannot include numeric characters. The character string will be displayed and will always be processed by HCL Workload Automation for Z as the default valid-to date.
The HIGHDATE parameter overrides the global setting of the PIFHD parameter of the INTFOPTS statement.
LUNAME(LU name)
Identifies the LU node name of the server communicating with the controller system. This keyword overrides the setting of the LU name given in the EQQYCOM INIT request. This is valid only if the server uses the APPC protocol.
OIWSNAME(IGNORE|ERROR)
Specifies whether to ignore the workstation name argument when it is used in a PIF program as the argument of an OI/OICOM resource code.

By default, an error message appears, for instance, when an OICOM list or an OI deletion is requested with the use of the work station name argument. The message states the erroneous use of the no longer significant argument and no list or deletion will be performed. The workstation name argument, when present, is simply ignored if the OIWSNAME keyword is set to IGNORE.

REMHOSTNAME (hostname|IP address)
The server host name or IP address used by the PIF program to communicate with the server through a TCP/IP network. This parameter overrides the value of REMHOST specified in the EQQYCOM INIT request. If you specify the REMHOSTNAME parameter in the INIT statement of the server procedure, it is ignored. REMHOSTNAME and LUNAME are mutually exclusive.
REMPORTNUMBER (value|425)
The server TCP/IP port number used by the PIF program to communicate with the server through a TCP/IP network. This parameter overrides the value of REMPORT specified in the EQQYCOM INIT request. If you specify the REMPORTNUMBER parameter in the INIT statement of the server procedure, it is ignored. Valid values are from 0 to 65535. The default is 425. REMPORTNUMBER and LUNAME are mutually exclusive.
SUBSYS(subsystem name)
Identifies the name of the subsystem controller to which the request is directed. This keyword overrides the setting of the RESOURCE parameter in the EQQYCOM INIT request.
TRACE(4 |8|0)
Defines the level of trace information HCL Workload Automation for Z writes to the diagnostic file (EQQDUMP). Specify 0, which is the default value, if you do not want trace information. Specify 4 if you want partial trace information. Specify 8 if you want full trace information.
USRLEV (11|12|13|14)
Communicates to EQQYCOM the level of the user program. If not specified, the programming interface assumes that the user-written program is invoking the PIF at its latest version, which is 14.
Valid values are:
11
Identifies HCL Workload Automation for Z V9.5. If you are using this level, you need to recompile the user-written applications to see the changes in the segment layouts.
12
Identifies the enablement of changes done for HCL Workload Automation for Z V9.5.0.1.
13
Identifies the enablement of changes done for HCL Workload Automation for Z V9.5.0.2.
14
Identifies the enablement of changes done for HCL Workload Automation for Z V9.5.0.3.
VERADGRD(FULL|YES|NO)
Application descriptions that are members of an application group have the name of the group definition in field ADGROUPID of segment ADCOM. VERADGRD controls the verification of this field when a new application description is created or an existing one is replaced. The verification is done for active application descriptions.

Specify FULL to check that the group definition is active and valid for at least a part of the validity period of the application description being created or updated.

Specifying YES is the same as specifying FULL, except that the application group id is accepted if the application description already has this application group id. It could be an update without any change to the application group id or an insert of a new version when there already are active versions with the same application group id.

Specifying NO means that no check is made to verify that the application group exists.

VERSRWSN(FULL|YES|NO)
The special resource description, SR, has fields representing workstations, the full workstation names or generic names; field SRDWSNAME of segment SRDWS for default connected workstations, field SRIWSNAME of segment SRIWS for workstations connected to an interval. VERSRWSN controls the verification of these fields when a new special resource is created or an existing one is replaced.

Specify FULL to verify the workstation fields against the workstation description file. Each workstation field in the resource description must match at least one of the workstation descriptions.

Specifying YES is the same as specifying FULL except that the workstation value is accepted if the resource description already has this workstation name. It could be an update without any change to the workstation names.

Specifying NO means that no check is made to verify that the workstation description exists.

Examples

 INIT SUBSYS(OPCB)                1
      HIGHDATE(991231)            2
      CWBASE(72)                  3
      LUNAME(SEIBM200.IS4MSV3B)   4
In this example of an INIT statement:
1
A PIF application sends a request to the OPCB subsystem. The statement will override global settings of the INTFOPTS statement.
2
The default valid-to date will be presented to the to the PIF application as 991231.
3
72 is the base year for the PIF application.
4
The request is sent to the LU node SEIBM200.IS4MSV3B.