This appendix describes the installation of PXS254. Several modes of installation are available. The choice of installation method depends on site requirements and existing PXS software.
| D.1. | Pre-conditions | |
| D.2. | Choice of installation mode | |
| D.2.1. | First time users | |
| D.2.2. | PXS200, 252 and 253 users upgrading to PXS254 | |
| D.2.3. | Scheduler permissions | |
| D.3. | Installing LIVE mode | |
| D.3.1. | Installation | |
| D.3.2. | Regression | |
| D.3.3. | Checking the JXS limits | |
| D.4. | Installing DEMO mode | |
| D.4.1. | Installation | |
| D.4.2. | Converting DEMO to LIVE | |
| D.4.3. | Regression from LIVE to DEMO | |
| D.5. | Installing UPGRADE mode | |
| D.5.1. | Installation | |
| D.5.2. | Using UPGRADE mode | |
| D.5.3. | Converting UPGRADE to LIVE | |
| D.6. | CUSTOM mode | |
| D.7. | Operating test schedulers | |
| D.7.1. | Starting the scheduler | |
| D.7.2. | Closing the scheduler | |
| D.7.3. | Changing the pool concurrency | |
| D.7.4. | Scheduler permissions and PXS_TELL / PXS_PATHWAY (CONTROL) | |
| D.7.5. | Other operation | |
| D.7.6. | Restoring the ABC work definitions | |
The upgrade/installation routes described here make several important assumptions about the current system. These are:
If these are not true, then the installations described here might need additional work. Please contact your PXS support for advice.
Each installation mode has been designed for a specific type of site. The modes available are as summarised in the table below:
| Mode name | Tag | Software held in | PXS Software assignment | Scheduler startup | Scheduler restart |
|---|---|---|---|---|---|
| LIVE | JXS | ICLSTDSW | Automatic | Automatic | Automatic |
| DEMO | PXS | ICLSTDSW | Automatic | PXSSTDS() | Manual |
| UPGRADE | PXS | own libs | PXS_ENV() | PXSSTDS() | Manual |
| CUSTOM | any | own libs | PXS_ENV(tag) | PXSSTDS(tag) | Manual |
The choice of mode depends primarily on existing PXS software.
First time users normally evaluate PXS in DEMO mode and then switch to LIVE once testing has finished. Existing batch, (work run with J, RJ or RIJ), is unaffected by any PXS mode.
The change from DEMO to LIVE is easy and work developed while in DEMO mode will run in LIVE mode without alteration.
A DEMO mode test scheduler can be installed and running in about ten minutes but requires some manual control.
Sites that wish to test PXS254 before upgrading any live work, should use UPGRADE mode. This uses a test scheduler and takes software from private libraries, so existing work is unaffected. PXS254 is selected when testing by using the new command PXS_ENVIRONMENT, (PXS_ENV).
Invokes using profile BATCH are diverted to profile PXSBATCH by the testing environment, and so can be tested unmodified against PXS254. In the same way PXS254 work defined while testing can be run LIVE without changes.
Appendix C gives details of PXS200 compatibility.
The suggested strategy using UPGRADE mode is:
If no test period is required then PXS254 can be installed in LIVE mode from the outset.
At PXS254 both PXS_TELL and PXS_PATHWAY can send commands to the whole scheduler e.g. PXS_TELL(JXS, HOLD). This facility requires a dummy definition file, :MASTER.[scheduler tag], to be set up; the permissions to which control access to the scheduler.
On some sites the task permissions to JXS will have to be modified before control facilities can work. The change required, which applies to JXS only, is CTSKP(JXS,ACC=S). This change does not affect the normal operation of the scheduler.
LIVE mode is the supported method for full production workloads and runs PXS as part of the VME batch scheduler, JXS.
This mode is set-up by first installing the software and then adapting JXS to use PXS254. Please note that installing product I8LBPX will delete earlier versions from that loadset, but that Product I8LBPB is release specific.
Before starting you will need:
The following should be called under the first load set owner:
Use <Send> then CTRL+. to save the changes.
If PXS254 is to be removed from JXS then repeat step 4 setting "Version" to the required version.
If full regression to PXS200 is required on any loadset then PXS254 must be deleted and PXS200 re-installed on that loadset.
Depending on the JXS setup, the maximum workload can vary from 240 to 3000 entries, and since PXS schedules work in larger chunks, the existing JXS limits might be need to be re-examined.
Details can be found in Appendix F.
New users of PXS often test it in DEMO mode before going LIVE. In DEMO mode PXS is used normally but the stand-alone test scheduler is started manually, (as described in section D.7 Operating test schedulers).
The instructions below assume that any PXS software found in the loadset libraries can be deleted.
Before starting you will need:
Under the first loadset owner call the following:
The test scheduler can now be controlled as in section D.7 Operating test schedulers. Please note the section on privacy and scheduler control.
When required, the demo system can be made live as follows:
Use <Send> then CTRL+. to save the changes.
Repeating steps 1,2 and 3 above but specify PXS for scheduler tag in step 2, and NONE for version in step 3. The demo scheduler can then be used and JXS will run without calling PXS.
UPGRADE mode allows sites to test PXS254 while running live work on earlier versions of PXS. In this mode PXS_ENV is called to select PXS254 software and the test scheduler is operated as in section D.7 Operating test schedulers.
Upgrade mode avoids clashes with older versions like this:
Using this layout all user commands are loaded from the library containing I8LBPX, which then loads the shareable code using release specific names such as I8LBPB254ACR9. PXS_ENV then assigns the required library for the version selected.
Important: UPGRADE mode installs a new version of I8LBPB into a live system which still needs the old version. The instructions below prevent INSTALL_ISSUE deleting live modules by diverting product definition files into library EMPTY. The instructions should be followed exactly.
Before starting to install in UPGRADE mode you will need:
To install in UPGRADE mode on the first loadset owner:
INTRLB( EMPTY )ULB( EMPTY, SEA=ICLSTDSWSO )INSTALL_ISSUE( LOAD=<loadset>, REL=<tape>, PRO=ALLBUTI8LBPX)XLB( EMPTY )The use of library EMPTY is very important.
This will install I8LBPX into its own libraries.
The test scheduler can now be used as in section D.7 Operating test schedulers. Please note the section of scheduler permissions and control.
Some code is loaded from loadset libraries even in UPGRADE mode, so the remaining loadsets should have the shareable PXS254 code installed:
The modules installed will be deleted and replaced, with the correct definition files, when converting to LIVE running on the new release.
In UPGRADE mode PXSENV must be called before any PXS254 software is used. For example:
PXSENV() PXS_PATHWAY()The scheduler itself is operated as described in section D.7 Operating test schedulers.
UPGRADE cannot be converted directly to LIVE, but must be reinstalled using the instructions in section D.3. Installing LIVE mode
The CUSTOM mode is provided for users who require one of the following variants:
Custom mode runs in one or more test schedulers which must be operated as described in section D.7 Operating test schedulers. Users must call a specific version of PXS_ENV before the customised software can be accessed. If CUSTOM mode is required please contact your PXS support for details.
The test scheduler set up in DEMO and UPGRADE modes is not controlled by VME's System Task Watchdog, (STW), and must be started manually.
The startup command, which should be called with system manager privilege, is:
PXS_START_DEMO_SCHEDULER or PXS_STDS.
By default this sets up a pool of tasks called PXS_BATCH with a concurrency of one. This can be changed at startup time using the NUMBER_OF_JOBS parameter. Where n is the number required:
PXSSTDS( NUMBER = nn )
The other parameters to PXS_STDS should only be changed as advised.
The test scheduler must be started after every system reload or scheduler break. Startup and recovery will be automatic when in LIVE mode.
The ZBOOJUM command is used to close the test scheduler. This can be issued from PXS_PATHWAY or from an OPER.
T( PXS, ZBOOJUM)
If issued from an OPER a result code of 42173 will be returned, this is normal and can be ignored.
If the number of PXSBATCH tasks is to be altered the following TELL command can be used from PATHWAY or OPER. Where n is the number required:
T( PXS, POOL, PXSBATCH & n & n )
It is possible to send commands to the whole scheduler using the above commands. This is done by creating a dummy definition file under :MASTER with the same name as the scheduler tag, e.g. :MASTER.PXS. The permissions to this definition, changed using PXS_CHANGE_PERMISSIONS, then control access to the scheduler.
The test scheduler is otherwise operated in the same way as in LIVE mode except that where a tag of JXS is given in the manual, PXS should be used.
The work definitions for the ABCDAY system referred to in the manuals are supplied together with the associated SCL procedures.
The work definitions are supplied in a file created using PXS_BACKUP and can be restored to any username. The file is installed into a library with search key ICLSTDSWSO, normally *SYSTEMOWNER.ICLSOURCE or *SYSTEMOWNER.STANDARD.ICLSOURCE. The commands to restore the definitions to user PXSDEMO are:
INTRGR(PXS) @ If no PXS work has yet been defined @
PXS_RESTORE(libraryname.ICL8LBPTABCWORK, NEW=:*.*>:PXSDEMO.*)