Installation and Uninstallation
This chapter describes how to install and uninstall OpenFrame/Batch as well as verify the successful installation.
1. Installation
Batch can be installed automatically using the installer or manually using the script.
1.1. Automatic Installation Using the Installer
Once the installation properties file described in Creating an Installation Properties File is created, OpenFrame can be easily installed by using the installer.
The following installation process applies to all platforms.
-
Copy the installer binary file and installation properties file to the desired directory to install Batch.
-
If no execute permission is granted to the installer binary file, use the chmod command to grant the execute permission.
The following grants the execute permission to an installer binary file for Linux x86 64 bit system.
$ chmod a+x OpenFrame_Batch7_1_MVS_Linux_x86_64.bin
-
Execute the installer at the console prompt.
<installer_file_name> -f batch.properties
Select one of the following two methods using the batch.properties installation properties file, and then press <Enter>.
-
Method 1
$ ./OpenFrame_Batch7_1_MVS_Linux_x86_64.bin –f batch.properties
-
Method 2
$ sh OpenFrame_Batch7_1_MVS_Linux_x86_64.bin -f batch.properties
-
-
The following messages is displayed while OpenFrame/Batch is being automatically installed.
Preparing to install... Extracting the JRE from the installer archive... Unpacking the JRE... Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... Launching installer... Preparing SILENT Mode Installation... =============================================================================== OpenFrame_Batch7.1_MVS (created with InstallAnywhere by Macrovision) ------------------------------------------------------------------------------- =============================================================================== Installing... ------------- [==================|==================|==================|==================] [------------------|------------------|------------------|------------------] Installation Complete.
|
Unlike OpenFrame/Base, Batch does not modify the .profile file. Therefore, the .profile file does not need to be executed to apply environment variables. |
1.2. Manual Installation by Using Scripts
If all the options for automatically creating tables and data sets are set to NO in the installation properties file, scripts must be manually executed after the completion of Batch installation.
The script files are located in the ${OPENFRAME_HOME}/scripts directory, and must be executed in the following order.
-
create_tjes.sh
Creates system tables to be used in Batch.
-
create_jcllib.sh
Creates the SYS1.JCLLIB data set to be used in Batch.
-
create_proclib.sh
Creates the SYS1.PROCLIB data set to be used in Batch.
-
create_userlib.sh
Creates the SYS1.USERLIB data set to be used in Batch.
-
create_templib.sh
Creates the SYS1.TEMPLIB data set to be used in Batch.
|
If all the options for automatically creating tables and data sets are set to YES, the installer runs the script files automatically in this order. |
2. Verifying the Installation
After installing Batch, it is recommended to verify if the product is successfully installed with the following two steps.
2.1. Directory Check
Batch has the following directory structure. The existing OpenFrame directory structure remains unchanged.
${OPENFRAME_HOME}
+---- UninstallerData
+---- bin
+---- config
+---- core
+---- cpm
+---- data
+---- include
+---- lib
+---- license
+---- log
+---- cmd
+---- data
+---- sys
+---- ofdb_scripts
+---- outputq
+---- profile
+---- sample
+---- scripts
+---- schema
+---- shared
+---- SMF
+---- TJES
+---- spbackup
+---- spool
+---- spunpack
+---- temp
+---- tsam
+---- temp
+---- lib
+---- copybook
+---- util
+---- volume_DEFVOL
+---- webde
+---- bin
+---- copybook
- UnistallerData
-
Contains files for deleting OpenFrame.
- bin
-
Contains executable files used in OpenFrame.
- config
-
Contains configuration files for OpenFrame. For more information about OpenFrame configuration, refer to OpenFrame Configuration Guide.
- core
-
Contains Tmax-related files used in OpenFrame, including Tmax server program, service program and Tmax configuration files.
- cpm
-
Contains character code conversion table files.
- data
-
Contains data files and error messages information files that are internally used in OpenFrame.
- include
-
Contains API header files used to compile applications.
- lib
-
Contains shared libraries used in OpenFrame.
- license
-
Contains the following OpenFrame license files.
File Description licbase.dat
Base license file.
lictjes.dat
Batch (TJES) license file.
lictacf.dat
TACF license file.
lichidb.dat
HiDB license file.
licosc.dat (MVS)
OSC license file.
licosi.dat (MVS)
OSI license file.
licaim.dat (AIM)
AIM license file.
- log
-
Contains log files generated by OpenFrame and the following subdirectories, each of which depends on the log file type. For more information, refer to "Appendix D. Log Management" in OpenFrame Base Guide.
Directory Description cmd
Contains manipulation log of OpenFrame.
sys
Contains system log of OpenFrame.
data
Contains data log of OpenFrame.
- ofdb_scripts
-
Contains templates and scripts required for using TSAM, NDB and HiDB.
- outputq
-
Contains data to print. For multi-nodes, placing this directory under a shared directory is recommended.
- profile
-
Contains profiles for individual OpenFrame users.
- sample
-
Contains OpenFrame example files.
- schema
-
Contains data set schema files created by using the cobgensch and pligensch tools.
- scripts
-
Contains script files used for initial configuration of OpenFrame.
- shared
-
Contains information to be shared by nodes in a multi-node environment. Typically, a shared disk such as NFS is used to allow access from all nodes.
- spbakup
-
Stores spool data set backups.
- spool
-
Contains spool data sets. For multi-nodes, placing this directory under a shared directory is recommended.
- spunpack
-
Restores backed up spool data.
- temp
-
Contains temporary working files.
- util
-
Contains utilities used in Batch.
- volume_DEFVOL
-
Used as the default volume for various OpenFrame products.
- webde
-
Manages the WEBDE information used in OpenFrame. For more information about WEBDE, refer to "2.9.5. WEBDE" in OpenFrame Configuration Guide.
|
Directory names may vary depending on the site. To change a directory name, the directory path and name in both the ofsys.conf and tjes.conf configuration file must also be modified. |
2.2. Startup Check
Perform a startup check in the following order.
-
If all the options for automatically creating a script are set to YES, open the ${OPENFRAME_HOME}/UninstallerData/log/install_batch.log file with a text editor to check if any error logs are present.
link_lib_batch.sh START batchinit START batchinit version 7.1.0(1) obuild@tplinux32:ofsrc7/batch(#1) 2007-11-09 16:45:01 Initialize OpenFrame Batch Tables Creating OFM_BATCH_JESST... > "OFM_BATCH_JESST" created... Creating OFM_BATCH_NODEST... > "OFM_BATCH_NODEST" created... Creating OFM_BATCH_NODEST_PK... > "OFM_BATCH_NODEST_PK" created... Creating OFM_BATCH_JCLSST... > "OFM_BATCH_JCLSST" created... Creating OFM_BATCH_JCLSST_PK... > "OFM_BATCH_JCLSST_PK" created... Creating OFM_BATCH_JOBGST... > "OFM_BATCH_JOBGST" created... Creating OFM_BATCH_JOBGST_PK... > "OFM_BATCH_JOBGST_PK" created... Creating OFM_BATCH_JOBQ... > "OFM_BATCH_JOBQ" created... Creating OFM_BATCH_JOBQ_PK... > "OFM_BATCH_JOBQ_PK" created... Creating OFM_BATCH_JOBQ_IDX1... > "OFM_BATCH_JOBQ_IDX1" created... Creating OFM_BATCH_JOBQ_IDX2... > "OFM_BATCH_JOBQ_IDX2" created... Creating OFM_BATCH_JOBQ_IDX3... > "OFM_BATCH_JOBQ_IDX3" created... Creating OFM_BATCH_OUTPUTQ... > "OFM_BATCH_OUTPUTQ" created... Creating OFM_BATCH_OUTPUTQ_PK... > "OFM_BATCH_OUTPUTQ_PK" created... Creating OFM_BATCH_OUTPUTQ_IDX1... > "OFM_BATCH_OUTPUTQ_IDX1" created... Creating OFM_BATCH_OUTPUTQ_IDX2... > "OFM_BATCH_OUTPUTQ_IDX2" created... Creating OFM_BATCH_WAITINFO... > "OFM_BATCH_WAITINFO" created... Creating OFM_BATCH_WAITINFO_PK... > "OFM_BATCH_WAITINFO_PK" created... Creating OFM_BATCH_STEPINFO... > "OFM_BATCH_STEPINFO" created... Creating OFM_BATCH_STEPINFO_PK... > "OFM_BATCH_STEPINFO_PK" created... Creating OFM_BATCH_IOREPORT... > "OFM_BATCH_IOREPORT" created... Creating OFM_BATCH_IOREPORT_PK... > "OFM_BATCH_IOREPORT_PK" created... Creating OFM_BATCH_RESUSAGE... > "OFM_BATCH_RESUSAGE" created... Creating OFM_BATCH_RESUSAGE_PK... > "OFM_BATCH_RESUSAGE_PK" created... Creating OFM_BATCH_SPOOLID... > "OFM_BATCH_SPOOLID" created... Creating OFM_BATCH_SPOOLID_PK... > "OFM_BATCH_SPOOLID_PK" created... Creating OFM_BATCH_JESQ... > "OFM_BATCH_JESQ" created... Creating OFM_BATCH_JESQ_PK... > "OFM_BATCH_JESQ_PK" created... Creating OFM_BATCH_JSS3INFO... > "OFM_BATCH_JSS3INFO" created... Creating OFM_BATCH_JSS3INFO_PK... > "OFM_BATCH_JSS3INFO_PK" created... Creating OFM_BATCH_STEPRPT... > "OFM_BATCH_STEPRPT" created... Creating OFM_BATCH_STEPRPT_PK... > "OFM_BATCH_STEPRPT_PK" created... Creating OFM_BATCH_DDLIST... > "OFM_BATCH_DDLIST" created... Creating OFM_BATCH_DDLIST_PK... > "OFM_BATCH_DDLIST_PK" created... Creating OFM_BATCH_RUNNER... > "OFM_BATCH_RUNNER" created... Creating OFM_BATCH_RUNNER_PK... > "OFM_BATCH_RUNNER_PK" created... create_tjescf.sh START COMPLETED SUCCESSFULLY! COMPLETED SUCCESSFULLY. CFL is done successfully for node(NODE1) SVC tables are successfully generated GST is successfully done TMBOOT for node(NODE1) is starting: TMBOOT: TMM is starting: Tue Mar 16 09:07:07 2021 TMBOOT: CLL is starting: Tue Mar 16 09:07:07 2021 TMBOOT: CLH is starting: Tue Mar 16 09:07:07 2021 TMBOOT: TLM(tlm) is starting: Tue Mar 16 09:07:07 2021 TMBOOT for node(NODE1) is starting: TMBOOT: SVR(TPFMAGENT) is starting: Tue Mar 16 09:07:07 2021 TMBOOT for node(NODE1) is starting: TMBOOT: SVR(ofrsasvr) is starting: Tue Mar 16 09:07:10 2021 TMBOOT for node(NODE1) is starting: TMBOOT: SVR(ofrlhsvr) is starting: Tue Mar 16 09:07:10 2021 TMBOOT for node(NODE1) is starting: TMBOOT: SVR(ofruisvr) is starting: Tue Mar 16 09:07:10 2021 create_jcllib.sh START pdsgen version 7.1.0(0) obuild@tplinux32:ofsrc7/base(#1) 2007-11-09 16:45:00 PDS Dataset Generation Program pdsgen: *** PDS SYS1.JCLLIB is created. create_proclib.sh START pdsgen version 7.1.0(0) obuild@tplinux32:ofsrc7/base(#1) 2007-11-09 16:45:00 PDS Dataset Generation Program pdsgen: *** PDS SYS1.PROCLIB is created. create_userlib.sh START pdsgen version 7.1.0(0) obuild@tplinux32:ofsrc7/base(#1) 2007-11-09 16:45:00 PDS Dataset Generation Program pdsgen: *** PDS SYS1.USERLIB is created. create_templib.sh START pdsgen version 7.1.0(0) obuild@tplinux32:ofsrc7/base(#1) 2007-11-09 16:45:00 PDS Dataset Generation Program pdsgen: *** PDS SYS1.TEMPLIB is created. batch_link.sh START batch_init.sh START volmgr version 7.1.0(8) obuild@tplinux32:ofsrc7/base(#1) 2007-11-09 16:45:00 *** Volume Manager *** COMPLETED SUCCESSFULLY! volmgr version 7.1.0(8) obuild@tplinux32:ofsrc7/base(#1) 2007-11-09 16:45:00 *** Volume Manager *** COMPLETED SUCCESSFULLY! Do you want to execute tjesinit? [Y/N] : tjesinit is finished pdsgen version 7.1.0(0) obuild@tplinux32:ofsrc7/base(#1) 2007-11-09 16:45:00 PDS Dataset Generation Program pdsgen: *** PDS SYS1.TSOMAP is created. pdsgen version 7.1.0(0) obuild@tplinux32:ofsrc7/base(#1) 2007-11-09 16:45:00 PDS Dataset Generation Program pdsgen: *** PDS SYS1.TSOLIB is created. tsomapgen 7.1.0(1) obuild@tplinux32:ofsrc7/batch(#1) 2007-11-09 16:45:01 [INIT] parsing starts!! [INIT] parsing ended!! Compiled map version is [3]. [/home/oframe3/OpenFrame/volume_DEFVOL/SYS1.TSOMAP/INIT.map] create ok. tsomapgen 7.1.0(1) obuild@tplinux32:ofsrc7/batch(#1) 2007-11-09 16:45:01 [LOGIN] parsing starts!! [LOGIN] parsing ended!! Compiled map version is [3]. [/home/oframe3/OpenFrame/volume_DEFVOL/SYS1.TSOMAP/LOGIN.map] create ok. tsomapgen 7.1.0(1) obuild@tplinux32:ofsrc7/batch(#1) 2007-11-09 16:45:01 [LOGOFF] parsing starts!! [LOGOFF] parsing ended!! Compiled map version is [3]. [/home/oframe3/OpenFrame/volume_DEFVOL/SYS1.TSOMAP/LOGOFF.map] create ok. tsomapgen 7.1.0(1) obuild@tplinux32:ofsrc7/batch(#1) 2007-11-09 16:45:01 [NEWPASS] parsing starts!! [NEWPASS] parsing ended!! Compiled map version is [3]. [/home/oframe3/OpenFrame/volume_DEFVOL/SYS1.TSOMAP/NEWPASS.map] create ok. tsomapgen 7.1.0(1) obuild@tplinux32:ofsrc7/batch(#1) 2007-11-09 16:45:01 [FEXPMAP] parsing starts!! [FEXPMAP] parsing ended!! Compiled map version is [3]. [/home/oframe3/OpenFrame/volume_DEFVOL/SYS1.TSOMAP/FEXPMAP.map] create ok. tsomapgen 7.1.0(1) obuild@tplinux32:ofsrc7/batch(#1) 2007-11-09 16:45:01 [FIMPMAP] parsing starts!! [FIMPMAP] parsing ended!! Compiled map version is [3]. [/home/oframe3/OpenFrame/volume_DEFVOL/SYS1.TSOMAP/FIMPMAP.map] create ok. Do you really want to down whole Tmax? (y : n): TMDOWN for node(NODE1) is starting: TMDOWN: SERVER(TPFMAGENT:36) downed: Tue Mar 16 09:07:22 2021 TMDOWN: SERVER(ofrsasvr:37) downed: Tue Mar 16 09:07:22 2021 TMDOWN: SERVER(ofrlhsvr:38) downed: Tue Mar 16 09:07:22 2021 TMDOWN: SERVER(ofruisvr:42) downed: Tue Mar 16 09:07:22 2021 TMDOWN: CLL downed: Tue Mar 16 09:07:22 2021 TMDOWN: TLM downed: Tue Mar 16 09:07:22 2021 TMDOWN: CLH downed: Tue Mar 16 09:07:22 2021 TMDOWN: TMM downed: Tue Mar 16 09:07:22 2021 TMDOWN: TMAX is down -
Start OpenFrame by executing tmboot.
$ tmboot
-
Check that there are no errors during the boot sequence.
TMBOOT for node(NODE1) is starting: TMBOOT: TMM is starting: Mon Mar 15 19:13:52 2021 TMBOOT: CLL is starting: Mon Mar 15 19:13:52 2021 TMBOOT: CLH is starting: Mon Mar 15 19:13:52 2021 TMBOOT: TLM(tlm) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(TPFMAGENT) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(ofrsasvr) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(ofrlhsvr) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(ofrdmsvr) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(ofrdsedt) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(ofrcmsvr) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(ofruisvr) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(ofruisvr) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(ofrsmlog) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(obmjmsvr) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(obmjschd) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(obmjinit) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(obmjhist) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(obmjspbk) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(ofrpmsvr) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(obmtsmgr) is starting: Mon Mar 15 19:13:52 2021 TMBOOT: SVR(obmjtimr) is starting: Mon Mar 15 19:13:52 2021 -
After running tmadmin, use the si command to print the servers list to check if all server processes are successfully started.
If all servers are marked as RDY as in the following, Batch is successfully installed and started.
$ tmadmin --- Welcome to Tmax Admin (Type "quit" to leave) --- $$1 NODE1 (tmadm): si ------------------------------------------------------------------------ clh svrname (svri) status count qcount qpcount emcount ------------------------------------------------------------------------ 0 TPFMAGENT ( 4) RDY 0 0 0 0 0 ofrsasvr ( 5) RDY 0 0 0 0 0 ofrlhsvr ( 6) RDY 0 0 0 0 0 ofrdmsvr ( 7) RDY 0 0 0 0 0 ofrdsedt ( 8) RDY 0 0 0 0 0 ofrcmsvr ( 9) RDY 0 0 0 0 0 ofruisvr ( 10) RDY 0 0 0 0 0 ofrsmlog ( 11) RDY 0 0 0 0 0 obmjmsvr ( 12) RDY 0 0 0 0 0 obmjschd ( 13) RDY 1 0 0 0 0 obmjinit ( 14) RDY 2 0 0 0 0 obmjhist ( 15) RDY 0 0 0 0 0 obmjspbk ( 16) RDY 0 0 0 0 0 ofrpmsvr ( 17) RDY 0 0 0 0 0 obmtsmgr ( 18) RDY 0 0 0 0 0 obmjtimr ( 19) RDY 0 0 0 0
3. Uninstallation
Batch can be uninstalled by using the uninstallation utility provided by the installer.
The following are the Batch uninstallation steps.
-
Run tmdown command to close OpenFrame before starting uninstallation process.
$ tmdown
-
Check if the following ending message is printed without errors.
Do you really want to down whole Tmax? (y : n): y TMDOWN for node(NODE1) is starting: TMDOWN: SERVER(TPFMAGENT:36) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(ofrdsedt:40) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(ofrsasvr:37) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(ofrcmsvr:41) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(obmjhist:56) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(ofrdmsvr:39) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(obmjtimr:60) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(ofrlhsvr:38) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(obmjspbk:57) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(obmjmsvr:53) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(ofruisvr:43) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(ofruisvr:42) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(obmjschd:54) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(ofrpmsvr:58) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(obmtsmgr:59) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(obmjinit:55) downed: Mon Mar 15 19:15:03 2021 TMDOWN: SERVER(ofrsmlog:52) downed: Mon Mar 15 19:15:03 2021 TMDOWN: CLL downed: Mon Mar 15 19:15:03 2021 TMDOWN: CLH downed: Mon Mar 15 19:15:03 2021 TMDOWN: TLM downed: Mon Mar 15 19:15:03 2021 TMDOWN: TMM downed: Mon Mar 15 19:15:03 2021 TMDOWN: TMAX is down -
After checking if OpenFrame is properly ended, run the Uninstall_Batch file under the ${OPENFRAME_HOME}/UninstallerData directory from the Unix console.
$ ./Uninstall_Batch
-
All files created during the Batch installation are deleted by the uninstallation program and any Batch-related contents in Tmax configurations are entirely removed.