B.3 Changes from Previous Releases
This section summarises the major changes since previous
releases PXS251 and PXS252. For full details refer to the entries
above.
- PXS_COPY and PXS_RESTORE now include option ADJUSTALL.
- Use of virtual store segments is now better controlled
with re-use of deleted segments.
- PXS_PATHWAY has synonyms of PXSP and PXS.
- PXS_PATHWAY(CONTROL) issues commands by tag with
consequent performance improvements. Permissions are
still checked.
- PXS_PATHWAY(CONTROL) subset (N)ormal doesn't show Omitted
work. A new subset (F)ull is provided to show all work.
- PXS_PATHWAY(INVOKE) checks for and warns of duplicate
names.
- NOPROMPT suite and invoke option introduced.
- New command PXSF_WAIT_FOR_NAME.
- New command PXS_RETRO_INVOKE.
- IGNORE, WAIT command. IGNORE with no data defaults to IF
in Omit and WAIT in Waiting, and is available in control.
- Full implementation of negative conditions, e.g. NOT
DAY_IS().
- Full support for conditions such as FILE_EXISTS( VAL NAME
) with full re-check if the variable changes.
- PXS_CONTROL needs no permissions to simply see display
lines.
- FINISHED now works like AFTER.
- ALLWORK in PXS_CP is now *ALLWORK.
- *ALLWORK permissions now apply to Network jobs without
local definitions.
- New time format for time BIFs and new BIFs TIME_IN and
WAIT_UNTIL.
- Default PERIOD for time BIFs now depends on TIME.
- Many BIFs now callable for testing in SCL.
- Usernames not now needed in FINISHED, FAILED and RUNNING.
- UNIQUE option replaces the unique name check made in
PXS_INVOKE.
- BIFs are now loaded in internal block in ADMIN.
- Better default account handling.
- Improved handling of cross user definitions in ADMIN.
- Create job from suite and vice versa.
- Formal support for Jobs as work owners via sub-invoke.
- Faster implementation of SKIP. Also SKIP JOBS option.
- BIFs can now be tested in SCL.
- Thirty second "Timer tick" removed.
- OCF browser from PXS_PATHWAY.
- INVOKEID can now be used in conditions.
- New system options FORCE USER SUBSET and OCF BROWSE
LEVEL.
- New diagnostic options INITIAL and RUNNING trace.
- PXS job level commands callable in OSCL as for batch.
- PXS_DELETE
- New PXS (CONTROL) with 18 lines
- SUBSET USER Option
- CHECK ACCESS Option
- PXJ OCF SUBSET Option to subset operator displays
- Re-packaging of ICLBPD
- New PXS(CONTROL) selection screen
- New PXS(CONTROL) TELL command overlay
- Trace files are now controlled by a new option which, if
set to YES, will cause a trace file to be placed and
connected during scheduler initialisation.
- A second option controls the number of old trace files
which are to be retained. The default is five old
generations.
- Trace files will not be opened during CHECKPOINT
sessions, even if requested by the option setting.
- As issued the Diagnostic Trace OCF is suppressed, and so
will not be used. If no trace file is selected then no
tracing will be done.
- A new trace type, ACTIONS, is provided. When requested
this will trace all PXS message types which relate to the
normal operation of work and work commands. If this is
combined with 97/D then all prompts are also logged.
There is now an option to restrict the use of selected
commands. Commands can be restricted in two ways:
- Privileged commands can only be sent by jobtag using the
VME TELL command, and not via PXS_TELL or from
PXS_PATHWAY.
- Suppressed commands cannot be used even by jobtag.
Each list also has a corresponding list of override users who
can continue to use the commands even if suppressed or
privileged. If a command cannot be used a new result code,
217467, is returned.
PXS_MAINTAIN has been upgraded to handle the new trace and
command options. This has required a new screen, called CONTROL
OPTIONS, to be used. This screen now also contains the OCF BROWSE
LEVEL, USER SUBSET and CHECK ACCESS options. The following new
options have also been added:
- PXAI006 forced INVOKE ID to be alphanumeric when
invoking. This is now implemented as an option which
selectably performs the same checks. This option is set
ON as issued and should be left that way unless there is
a good reason not to. It is likely that future versions
of PXS will require alphanumeric invoke ids.
- The optional rep which allowed RJ parameter names to be
given as, for example, RJRERUN instead of RERUN, is now
implemented as an option. It is recommended that this
only be used to avoid PXS200 compatibility problems.
Source clearance of all PXS253 reps: PXAA012, PXAA014,
PXAA015, PXAI006, PXGF009, PXGF101.1, PXSA001.1, PXSS006 and
PXSW002. NORMAL can now be used as a synonym for NORM in
PXS_TRACE and in the ZTRACE command. The loop detection has now
been improved so that looping suites and jobs will be slowed down
even if the loops take more than one scheduler interaction within
one minute. The OCF subset option now works correctly. See Appendix C - Release compatibility. The PXS
compatibility strategy aims to simplify parallel testing and ease
regression. It does this by:
- Allowing PXS254 to run existing work without altering
existing SCL or work definitions.
- Requiring PXS254 to produce PXS200 compatible definitions
where possible.
This means that until PXS254 facilities are actively used,
PXS200 work is not at risk for any reason. This is achieved with
the following design principles:
- All work defined on PXS200 must run on PXS254 without
amending the definition file in any way.
- Calls to PXS from SCL compiled under PXS200 will work,
(with warnings), on PXS254 even if the templates have
changed.
- PXS254 will mark work which cannot be read by PXS200, and
optionally give a warning. PXS200 will reject such work.
- Where possible, PXS254 will produce definition files that
can be used by PXS200.
- Scheduler queue file format is not compatible. On restart
all releases will delete work invoked from other
releases.
- PXS_BACKUP and PXS_RESTORE will have the same
compatibility as definition files. PXS_RESTORE and
PXS_COPY will always produce files in PXS254 format.