How to add or modify the //STEPLIB DD to the OPSOSF and OSFTSL Server tasks, without restarting the OPS/MVS main task.
Article ID: 10472
Updated On:
Products
Issue/Introduction
The OPSOSF are Primary Address Spaces, started as Servers tasks that handle asynchronous action requests from various CA OPS/MVS facilities, while OSFTSL are used to execute Rexx in a long running OSF server.
The OSF uses OPSOSF address spaces as servers that handle asynchronous action requests from various CA OPS/MVS facilities. They include the following facilities:
– Automated Operations Facility (AOF)
– Enhanced Console Facility (ECF)
– IMS Operations Facility (IOF)
– Multi-system Facility (MSF)
They use z/OS cross-memory services to handle action requests and they may be swappable or non-swappable, as determined by the value of the OSFSWAPPABLE parameter.
By design, OPSOSF servers can only be started by CA OPS/MVS. You should never try to start an OPSOSF server manually. OPSOSF servers abend if they are not started correctly.
The number of OPSOSF servers that CA OPS/MVS starts and keeps active is determined by the values of the OSFMIN and OSFMAX parameters. Their values can range from 1 to 30. Both parameters have a default of 2.
The OSFTSL address space is automatically started by OPSMAIN as a Server that handles and executes Rexx in a long running OSF server.
How to add or modify the //STEPLIB DD to these OPSOSF and/or OSFTSL Server tasks, without restarting the OPS/MVS main task?
Environment
Resolution
The OPSOSF and OSFTSL address spaces are automatically started by OPS/MVS main task to execute some requested activity. Their procedures are cataloged during product installation and You always need to reflect in these cataloged procedures every change You need to perform, this should be the first step to do.
So, You need to add/change the //STEPLIB DD in the cataloged procedure, double-checking that the added load library is the same of the OPSMAIN Primary Task.
Then, to have these Server Tasks refreshed under OPS without having to stop/restart it, OPSVIEW Option 4.3 can be used.
OPSVIEW option 4.3 is the ‘Operator Service Facility Panel’ and it looks like the following:
Operator Server Facility XXXX --- O P S V I E W --- OPSP ----- Row 1 to 5 of 5
Command ===> Scroll ===> CSR
Number of commands on the OSF Execute Queue: 0 SYSTEM ===> *
Maximum OSF Execute Queue Depth : 5 WAIT ===> 30
Average OSF Execute Queue Time (in seconds): 0.010817 CLASS ===> TSO
ASID Taskname Status J Trans Elapsed CPU Time Lines Curr/Last Command
---- -------- -------- - ----- -------- -------- ------- -----------------
_ 0032 OPSOSFP IDLE Y 586 35.58.06 050.896S 1268 OI P(emailone) ARG(
_ 0033 OPSOSFP IDLE Y 239 35.58.06 004.505S 489 OI P(emailone) ARG(
_ 0034 OPSOSFP IDLE Y 46 35.58.06 002.692S 97 OI checksmf
_ 0035 OPSOSFP IDLE Y 37 35.58.06 000.528S 76 OI P(MSFCHECK)
_ 0036 OPSOSFP IDLE Y 4 35.58.05 008.114S 10 OI P(MSFCHECK)
******************************* Bottom of data ********************************
If CLASS ===> TSO is selected (this is the default), then all the ACTIVE OPSOSF Server Tasks are displayed, while, selecting CLASS ===> TSF , all the OSFTSL ACTIVE Server Tasks are displayed.
Here a sample display:
Operator Server Facility XXXX --- O P S V I E W --- OPSP ----- Row 1 to 2 of 2
Command ===> Scroll ===> CSR
Number of commands on the OSF Execute Queue: 0 SYSTEM ===> *
Maximum OSF Execute Queue Depth : 0 WAIT ===> 30
Average OSF Execute Queue Time (in seconds): UNAVAIL CLASS ===> TSL
ASID Taskname Status J Trans Elapsed CPU Time Lines Curr/Last Command
---- -------- -------- - ----- -------- -------- ------- -----------------
_ 002B OPSOSFP IDLE N 0 36.13.04 000.048S 2
_ 002F OPSOSFP IDLE N 0 36.13.04 000.049S 2
******************************* Bottom of data ********************************
You can cycle the ACTIVE Servers in these two panels so that the new Server Tasks will pick up the new modified cataloged procedures, which will reflect the new //STEPLIB DD content, without stopping and restarting OPS/MVS main task.
Feedback
