System Operation

This chapter describes how to start and shut down the OSI system and how to use the log files which record operating information about the OSI system.

1. Starting and Shutting Down OSI

In order to operate the OSI system, Tmax, which is a TP-monitor, must be running and the modules of OpenFrame/Base and OpenFrame/Batch must be prepared, to be able to run.

Starting and Shutting Down OSI

TCache must be created before starting up the control region. TCache can be created using the pfmtcacheadmin tool.

1.1. Starting OSI

The following are the steps for starting OSI.

Start osiomsvr and base/batch modules required in Tmax engine and OSI sytem. (osiboot)

Starting Tmax consists of three internal stages. The stages are performed simultaneously using the osiboot tool.

Tmax is started.
The server modules used by other packages of OpenFrame that are needed to start OSI, are also started.

In order to perform the second stage the server modules used in packages other than OSI, must be configured beforehand in a environment configuration file named "osi.ofsys.seq". Consideration should be given to the operating order of each server.

To enable the operation of BMP in OSI, the server modules required in OpenFrame/Batch must be started when Tmax is started.

The following example is a general example of this.
```
$ cat osi.ofsys.seq
TPFMAGENT
ofrsasvr
ofrlhsvr
ofrdmsvr
ofrdsedt
ofrcmsvr
ofruisvr
ofrsmlog
obmjmsvr
obmjschd
obmjinit
obmjhist
obmjspbk
ofrpmsvr
obmtsmgr
obmjtimr
tmsvr
#osimq001
```

osiomsvr to start the OSI system server and user server is started.

Start Tmax through osiboot as follows:

$ osiboot

TMBOOT for node(NODE1) is starting:
  TMBOOT: TMM is starting: Wed Mar 10 19:37:02 2021
  TMBOOT: CLL is starting: Wed Mar 10 19:37:02 2021
  TMBOOT: CLH is starting: Wed Mar 10 19:37:02 2021
  TMBOOT: TLM(tlm) is starting: Wed Mar 10 19:37:02 2021
[2021-03-10T19:37:02.848282] [osiboot(5670)           ] [M] [OSI7061M] System server(ofrsasvr) booting ok
[2021-03-10T19:37:02.851625] [osiboot(5670)           ] [M] [OSI7061M] System server(ofrlhsvr) booting ok
[2021-03-10T19:37:02.855374] [osiboot(5670)           ] [M] [OSI7061M] System server(ofrdmsvr) booting ok
[2021-03-10T19:37:02.859919] [osiboot(5670)           ] [M] [OSI7061M] System server(ofrdsedt) booting ok
[2021-03-10T19:37:02.864295] [osiboot(5670)           ] [M] [OSI7061M] System server(ofrcmsvr) booting ok
[2021-03-10T19:37:02.868285] [osiboot(5670)           ] [M] [OSI7061M] System server(ofruisvr) booting ok
[2021-03-10T19:37:02.873191] [osiboot(5670)           ] [M] [OSI7061M] System server(ofrsmlog) booting ok
[2021-03-10T19:37:02.877533] [osiboot(5670)           ] [M] [OSI7061M] System server(obmjmsvr) booting ok
[2021-03-10T19:37:02.881853] [osiboot(5670)           ] [M] [OSI7061M] System server(obmjschd) booting ok
[2021-03-10T19:37:02.886434] [osiboot(5670)           ] [M] [OSI7061M] System server(obmjinit) booting ok
[2021-03-10T19:37:02.890673] [osiboot(5670)           ] [M] [OSI7061M] System server(obmjhist) booting ok
[2021-03-10T19:37:02.897808] [osiboot(5670)           ] [M] [OSI7061M] System server(obmjspbk) booting ok
[2021-03-10T19:37:02.905868] [osiboot(5670)           ] [M] [OSI7061M] System server(ofrpmsvr) booting ok
[2021-03-10T19:37:02.920575] [osiboot(5670)           ] [M] [OSI7061M] System server(obmtsmgr) booting ok
[2021-03-10T19:37:02.937001] [osiboot(5670)           ] [M] [OSI7061M] System server(tmsvr) booting ok
[2021-03-10T19:37:02.943765] [osiboot(5670)           ] [M] [OSI7061M] System server(osiomsvr) booting ok
[2021-03-10T19:37:02.943791] [osiboot(5670)           ] [M] [OSI7051M] Booting process complete.

Start the system server (control region) by IMSID using JCL.

Start the OSI system server (control region) after starting Tmax.

One OSI system is started by each IMSID. When using a 3 OSI system configuration, start three OSI systems per IMSID. The OSI system is started by running JOB in JCL, using the tjesmgr tool.

The following is an example of starting the system server (control region) whose IMSID is IMSA, with JCL.
```
//IMSACTL  JOB
//STEP1    EXEC PGM=DFSMVRC0,
//            PARM='CTL,IMS,IMSID=IMSA'
//MODBLKSA DD DISP=SHR,DSN=OSI.IMSA.DEFLIBA
//MODBLKSB DD DISP=SHR,DSN=OSI.IMSA.DEFLIBB
//IMSACBA  DD DISP=SHR,DSN=IMS.ACBLIBA
//IMSACBB  DD DISP=SHR,DSN=IMS.ACBLIBB
//DFSRESLB DD DISP=SHR,DSN=IMS.RESLIB
//FORMATA  DD DISP=SHR,DSN=OSI.IMSA.MFSLIBA
//FORMATB  DD DISP=SHR,DSN=OSI.IMSA.MFSLIBB
//STEPLIB  DD DISP=SHR,DSN=OSI.IMSA.STEPLIB
//QBLKS    DD DISP=SHR,DSN=OSI.IMSA.MQLIB
//MODSTAT  DD DISP=SHR,DSN=OSI.IMSA.MODSTAT
//SYSOUT   DD SYSOUT=*
//
```
In the PARM parameter of JCL which starts the IMS system server, the following two items can be configured.

Item Description

IMSID

Unique IMS ID of the system server. (4 bytes)

AUTO

Option to automatically execute "/NRESTART" or "/ERESTART" command after starting the server. (YES|NO)
Enable OSI system by OSI commands

After starting the system server (control region) with JCL, execute "/NRE" or "/ERE" command if it is not the first OSI system startup. The "/NRE" command is used when the server was normally shut down through the "/CHE" command. And when it was not shut down normally, "/ERE" command is used. Otherwise, an error occurs and the command is not executed. After that, execute "/START DC" command to log on to the terminal.

In the following example, the OSI command, /NRE and /STA DC of the system server whose IMSID is IMSA are input in order.
```
$ imscmd IMSA /NRE
IMS control region : [IMSA]
Requested command  : [NRE]
----------------------------------------
NRESTART COMMAND IN PROGRESS
*21069/194013*
----------------------------------------
Command '/NRE' execution done
$ imscmd IMSA /STA DC
IMS control region : [IMSA]
Requested command  : [STA DC]
----------------------------------------
START COMMAND COMPLETED
*21069/194018*
----------------------------------------
Command '/STA DC' execution done
```
Start the user server per IMSID (dependent region) using JCL.

After the system server (control region) is started, execute the MPP start JCL command, according to the class to be processed. MPP can be started by running jobs as needed. It can also be started by using "/START REGION" which is an OSI command.

The following is an example of JCL that starts the user server (dependent region) whose IMSID is IMSA.
```
//IMSAMSG  JOB
//STEP1    EXEC PGM=DFSRRC00,
//            PARM='MSG,001002003004,W00099000,,,R,,,,IMSA,,,,'
//STEPLIB  DD DISP=SHR,DSN=OSI.IMSA.STEPLIB
//SYSPRINT DD SYSOUT=*
//SYSOUT   DD SYSOUT=*
//SYSDBOUT DD SYSOUT=*
//
```
The following is an example of the "/START REGION" command, which starts the user server (dependent region) whose JCL name is IMSAMSG.
```
$ imscmd IMSA /START REGION IMSAMSG
IMS control region : [IMSA]
Requested command  : [START REGION IMSAMSG]
----------------------------------------
START COMMAND COMPLETED
*21069/194050*
----------------------------------------
Command '/START REGION IMSAMSG' execution done
```
For detailed information about "/START REGION", refer to OpenFrame OSI Command Reference Guide.

Item	Description
IMSID	Unique IMS ID of the system server. (4 bytes)
AUTO	Option to automatically execute "/NRESTART" or "/ERESTART" command after starting the server. (YES\|NO)

1.2. Shutting Down OSI

The following are the steps for shutting down OSI.

Shut down the system server (control region) and the user server (dependent region).

Use the OSI command to terminate the system server (control region) and the user server (dependet region). The OSI command is CHECKPOINT, and shut down the system server after terminating the user server.

The following is an example of shutting down the system server and the user server whose IMSID is IMSA, using the OSI command.
```
$ imscmd IMSA /CHE FREEZE
IMS control region : [IMSA]
Requested command  : [CHE FREEZE]
----------------------------------------
CHECKPOINT COMMAND IN PROGRESS
*21069/194108*
----------------------------------------
Command '/CHE FREEZE' execution done
```

Shut down Tmax.

If the osidown tool is used, after the server modules which are used in the packages of OpenFrame are shut down, Tmax is shutdown.

The following is an example of shutting down Tmax using osidown.

$ osidown
[2021-03-10T19:41:27.956075] [osidown(5969)           ] [M] [OSI7141M] System server(osiomsvr) shutdown ok
[2021-03-10T19:41:27.960864] [osidown(5969)           ] [M] [OSI7141M] System server(tmsvr) shutdown ok
[2021-03-10T19:41:27.983167] [osidown(5969)           ] [M] [OSI7141M] System server(obmtsmgr) shutdown ok
[2021-03-10T19:41:27.995447] [osidown(5969)           ] [M] [OSI7141M] System server(ofrpmsvr) shutdown ok
[2021-03-10T19:41:27.000641] [osidown(5969)           ] [M] [OSI7141M] System server(obmjspbk) shutdown ok
[2021-03-10T19:41:28.003942] [osidown(5969)           ] [M] [OSI7141M] System server(obmjhist) shutdown ok
[2021-03-10T19:41:28.033647] [osidown(5969)           ] [M] [OSI7141M] System server(obmjinit) shutdown ok
[2021-03-10T19:41:28.040265] [osidown(5969)           ] [M] [OSI7141M] System server(obmjschd) shutdown ok
[2021-03-10T19:41:28.047434] [osidown(5969)           ] [M] [OSI7141M] System server(obmjmsvr) shutdown ok
[2021-03-10T19:41:28.076810] [osidown(5969)           ] [M] [OSI7141M] System server(ofrsmlog) shutdown ok
[2021-03-10T19:41:28.086320] [osidown(5969)           ] [M] [OSI7141M] System server(ofruisvr) shutdown ok
[2021-03-10T19:41:28.093782] [osidown(5969)           ] [M] [OSI7141M] System server(ofrcmsvr) shutdown ok
[2021-03-10T19:41:28.101464] [osidown(5969)           ] [M] [OSI7141M] System server(ofrdsedt) shutdown ok
[2021-03-10T19:41:28.108771] [osidown(5969)           ] [M] [OSI7141M] System server(ofrdmsvr) shutdown ok
[2021-03-10T19:41:28.116562] [osidown(5969)           ] [M] [OSI7141M] System server(ofrlhsvr) shutdown ok
[2021-03-10T19:41:28.124770] [osidown(5969)           ] [M] [OSI7141M] System server(ofrsasvr) shutdown ok

TMDOWN for node(NODE1) is starting:
  TMDOWN: CLH downed: Wed Mar 10 19:41:28 2021
  TMDOWN: CLL downed: Wed Mar 10 19:41:28 2021
  TMDOWN: TLM downed: Wed Mar 10 19:41:28 2021
  TMDOWN: TMM downed: Wed Mar 10 19:41:28 2021
  TMDOWN: TMAX is down

1.3. Restarting OSI

The following are the steps for restarting OSI.

Start Tmax. (osiboot)
Start a system server (control region) for each IMSID, using JCL.
Restart the system server (control region) for each IMSID using the command. After shutting down, using the OSI command, the system server needs to be restarted in order to get the previous system usage information.

The following is an example of restarting the system server (control region) whose IMSID is IMSA using the OSI command.
```
$ imscmd IMSA /NRE
IMS control region : [IMSA]
Requested command  : [NRE]
----------------------------------------
NRESTART COMMAND IN PROGRESS
*21069/195025*
----------------------------------------
Command '/NRE' execution done
```
To allow a terminal to be logged on use "/START DC".
Start a user server (dependent region) per IMSID using JCL or by using "/START REGION".

For more information on "/START REGION", refer to OpenFrame OSI Command Reference Guide.

2. Log Management

In OpenFrame OSI system, the server logs are managed by dividing it into a system server, MPP user server, and BMP user server. This section describes the management method for each server.

2.1. System Server and MPP User Server

The logs generated by OSI system server and MPP user servers are OUT log and ERR log. Both logs are stored in ULOGDIR described in the NODE clause of the Tmax configuration file. Users can freely set ULOGDIR, but it is recommended to set it to the directory under ${OPENFRAME_HOME}/log.

OUT log

If a file name is specified with the [-o] option in the CLOPT clause, all contents written to stdout by the OSI system server and the MPP user server are printed to the file. The output log follows the common output format of OpenFrame.

The following is the output format of the OUT log.

[YYYY-MM-DDTHH:MI:SS.FFFFFF] [MODULE(PID)] [LEVEL] [MSGCODE] MESSAGE-CONTENTS

Field	Description
[YYYY-MM-DDTHH:MI:SS.FFFFFF]	YYYY-MM-DDTHH:MI:SS.FFFFFF type timestamp which includes dates.
MODULE	Module name of the OSI system which prints messages.
PID	Process ID of the application server.
LEVEL	Prints one of the following. M(Message): A message in which the system gives information to users. Various information about the server is printed. E(Error): A message which is printed when an error occurs in the system. It is displayed when users give incorrect information to the system or there is an internal error in the system. W(Warning): A message which is printed when an error occurs in the system, but does not affect the operation of the system. D(Debug): A message which is output for system debugging.
MSGCODE	8-character OSI message code.
MESSAGE-CONTENTS	Field where log messages are printed.

Field

Description

[YYYY-MM-DDTHH:MI:SS.FFFFFF]

YYYY-MM-DDTHH:MI:SS.FFFFFF type timestamp which includes dates.

MODULE

Module name of the OSI system which prints messages.

PID

Process ID of the application server.

LEVEL

Prints one of the following.

M(Message): A message in which the system gives information to users. Various information about the server is printed.
E(Error): A message which is printed when an error occurs in the system. It is displayed when users give incorrect information to the system or there is an internal error in the system.
W(Warning): A message which is printed when an error occurs in the system, but does not affect the operation of the system.
D(Debug): A message which is output for system debugging.

MSGCODE

8-character OSI message code.

MESSAGE-CONTENTS

Field where log messages are printed.

The following is an example of the OUT log file of the MPP user server whose message class is 1 in the IMS system named IMSA.

[2021-03-10T19:59:51.194767] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP2D] [GENERAL]LOG_LEVEL = D
[2021-03-10T19:59:51.217509] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP1D] AGN =
[2021-03-10T19:59:51.217539] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP2D] [SECURITY]TYPE = TACF
[2021-03-10T19:59:51.217564] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP2D] security type is TACF[2]
[2021-03-10T19:59:51.217591] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP3D] [GENERAL]SCHEDULE_RECOVER_MAXCNT = 5
[2021-03-10T19:59:51.227545] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP3D] [MQ]USE_MQ = NO
[2021-03-10T19:59:51.227821] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP1D] CTL's JOBID : JOB02316
[2021-03-10T19:59:51.227844] [IMSAMPP_TCL1(6839)      ] [M] [OSI0291M] IMSA server boots - resource manager initialization starts
[2021-03-10T19:59:51.229970] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP2D] [CPM]REGION_CCSID =
[2021-03-10T19:59:51.229992] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP2D] [CPM]ASCII_TO_EBCDIC = ASCEBCUS.cpm
[2021-03-10T19:59:51.230114] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP2D] [CPM]EBCDIC_TO_ASCII = EBCASCUS.cpm
[2021-03-10T19:59:51.230214] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP0D] cpm version
[2021-03-10T19:59:51.230228] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP2D] [SCREEN]3270_TYPE = 3270-A2
[2021-03-10T19:59:51.230239] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP0D] SCREEN TYPE : A2
[2021-03-10T19:59:51.230255] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP3D] [CPM]CONVERT_TO_SPACE = X'00'
[2021-03-10T19:59:51.230270] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP2D] X'00'(in ASCII) will be converted X'20'
[2021-03-10T19:59:51.230280] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP1D] null character=1a
[2021-03-10T19:59:51.230289] [IMSAMPP_TCL1(6839)      ] [M] [OSI0101M] osimfs version: 7.2.0(4) sbaek@tmax:of7_1_mvs_dev/osi(#1) 2020-11-12 19:43:54
[2021-03-10T19:59:51.231791] [IMSAMPP_TCL1(6839)      ] [D] [DEBUGP2D] [GENERAL]SVCLOG = N
[2021-03-10T19:59:51.231812] [IMSAMPP_TCL1(6839)      ] [M] [OSI0291M] IMSA server boots - resource manager initialization completed

ERR log

If a file name is specified with the [-e] option in the CLOPT clause, all contents written to stderr in the OSI system server and the MPP user server are printedt to the file. The output log follows the common output format of OpenFrame in the same way as the OUT log.

2.2. BMP User Server

The BMP user server creates logs in the SPOOL log directory as the application program is executed in the form of a batch job using JCL. Unlike the MPP user server, the BMP user server manages logs through a directory separated by JOBID by using the same server module in one IMS system. It also follows the common output format of OpenFrame.

For more information, refer to OpenFrame Batch Guide.