Installing the Job Monitor
This Techdoc contains information on how to install the Remote Job Monitor server on the host system. This information includes a list of files to upload to the host system, as well as a description of these files.
The Remote Job Monitor is not required for the TPF Toolkit to function. It is provided as an optional tool to enable better access to JES from a workstation running the TPF Toolkit. The same job monitor is shipped with WebSphere Studio Enterprise Developer. If you installed that job monitor, you do not need to install the one supplied with the TPF Toolkit.
The job monitor server should be installed by the administrator or system programmer; it should not be installed by each user.
All of the files that are required to upload the job monitor to the host system are in binary format on the install image. In the TPF Toolkit install image, it is located in C:\Program Files\IBM\TPF Toolkit\Config\Host, where C:\Program Files\IBM\TPF Toolkit is the location where you installed TPF Toolkit. Upload the following files to the host system:
This is the load module for the job monitor server. Since this file was created using XMIT, you must upload it to a fixed format blocked file with a logical record length of 80. To upload this file, do the following:
1. Ftp to your zSeries machine.
2. Position to the correct local directories using lcd. For example, from a command prompt, type:
lcd c:\Program Files\IBM\TPF Toolkit\config\host
2. Type binary to set the transfer mode to binary.
3. Type quote site recfm=fb lrecl=80 blksize=3120 to set the file creation attributes.
4. Type put JMONITOR 'TPF.TEMP.JMON' to put the file into TPF.TEMP.JMON.
5. From TSO, type receive inds('TPF.TEMP.JMON') . The load module is received and you can move the member to an APF authorized load library.
This file is stored in binary format on the installation image and contains the sample JCL to start the job monitor. Ftp this file to the host in binary format and customize as appropriate.
This file is stored in binary format on the installation image and contains the configuration information. Ftp this file to the host in binary format and customize as appropriate.
When customizing this file, modify the following fields:
- SERV_PORT - to indicate the port on which the job monitor listens for connections. This port must be set in the JES subsystem properties for each user.
- JES - to match the level of JES that you are running (should be JES2 or JES3).
- HOST_CODEPAGE - to reflect a different code page. Do not change the CODEPAGE from UTF-8. This function may be supported later.
The other fields in the configuration should be used as the defaults unless there are performance problems or dropped connections. These fields are used to handle the number of concurrent connected users. Currently, the job monitor can manage up to 200 connections. If you want to have more than 200 users, start another job monitor listening on a different port, and then have users connect to that job server.
To allow users to issue operations via the job monitor, issue the following commands:
RDEFINE CONSOLE JMON UACC(READ)
RDEFINE OPERCMDS JES2.** UACC(NONE)
PERMIT CLASS(OPERCMDS) JES2.** ID <userid or groupid> ACCESS (CONTROL) WHEN(CONSOLE(JMON))
Note: < userid or groupid> is your actual user ID or group ID.
This restricts the use of JES commands so that users can only use these commands when running the job monitor.