ADDRESS

CA-GSS/ISERV Commands › CA-GSS Initialization Parameters › ADDRESS

ADDRESS

This parameter defines a REXX ADDRESS environment.

Syntax

ADDRESS name module [limit [DETACH] [MAXTASK nnn] [TYPE ttt]

Parameters

name

ADDRESS environment name. Most environments provided by CA or used by CA products require a specific name (a name for the ADDRESS or one provided by an ALTNAME statement).

module

Name of the load module that processes the ADDRESS environment. In general, the load modules required are provided with the product associated with the service.

Load modules must be accessible to CA‑GSS using STEPLIB/JOBLIB/LINKLIST search. Modules must be link-edited with correct linkage parameters.

limit

For reliability, ADDRESS code is executed in subtasks. To prevent possible looping, you can specify the maximum amount of CPU time permitted for processing a single ADDRESS instruction. Specify the value in seconds. Specify 0 (zero) for unlimited time.

Default: 15.

DETACH

Detaches the subtask that processed the ADDRESS command following completion of the IMOD task that used it.

MAXTASK nnn

Maximum number of concurrently executing IMOD tasks that can use this ADDRESS environment.

Value: 0 to 32,767 (inclusive). Specify 0 to prevent any limitation.

Default: 10.

An IMOD task attempting to obtain the use of an ADDRESS environment that is at its MAXTASK value is suspended until another IMOD task relinquishes use of the ADDRESS environment.

TYPE ttt

CA‑GSS supports a variety of interfaces for ADDRESS environment load modules. To identify which interface is required, provide the TYPE keyword. TYPE 0 environments are TSO/E REXX compatible. TYPE 255 environments cannot be directly invoked. For other types, see "Preferred Names".

Default: CA‑GSS tries to determine the type by examining the ADDRESS name for forms that it recognizes.

Usage Notes

Whenever an IMOD task issues an ADDRESS command, a subtask is assigned to the IMOD task. More ADDRESS requests of the same name are referred to the same subtask for the life of the IMOD task. When the IMOD task ends, the subtask is released for use by another IMOD task or it is detached.
For security, each ADDRESS-processing subtask runs under the user ID of the entity that started the IMOD task.
For charge-back purposes, CPU time that an ADDRESS-processing task accrues is passed back to the IMOD task.
For information about writing your own ADDRESS environments, see "Providing Your Own Functions and ADDRESS Environments."

Preferred Names

Product	Address Name	Load Module	Type	MAXTASK	DETACH
DB2 (function)	DSNALI ⁽²⁾ DSNHLI2 ⁽²⁾	DSNALI DSNHLI2	255 255	- ---	No No
IDCAMS (IBM)	IDCAMS	IDCAMS	1	-	No
INFO/MGMT (IBM)	INFO	BLGYRXM	0	-	Yes
CA OPS/MVS Event Management and Automation	OPER OPSREQ AOF OSF OPSVALUE ⁽²⁾	OPGLEVMG OPGLEVMG OPGLEVMG OPGLEVMG OPGLEVMG	10 11 12 13 255	- - - - -	No No No No No
CA SYSVIEW Performance Management	SYSVIEWE⁽¹⁾ COMMAND	GSVXAPIE GSVXAPIE	0 0	- -	Yes Yes
CA Jobtrac Job Management	JOBTRAC	GJTRGCUU	3	5	No
CA MIM Resource Sharing	TPCF	MIMAPI1	7	-	No
CA 11 Workload Automation Restart and Tracking	RERUN	RUNTADDR	3	5	No
CA View	XPVIEW	SARINTF	0	-	No
CA 7 Workload Automation	CA7	CAL2X2WR	0	15	No

Table Notes

Define the COMMAND as an alternative name (using the ALTNAME parameter), because many existing IMODs can refer to ADDRESS SYSVIEWE by its previous name.
These ADDRESS names are placeholders only. No ADDRESS environment of this name is available to REXX processing.