Supervisor Software Changes 500.44 - 520.99

If the TT function was invoked for a PD context request which failed because the user-provided file or directory request was invalid, the calling WHEN slot would remain indefinitely active,

  marked as 'WAIT TT'.

Similarly, if a PD context DO or EVAL request failed because the file or directory was invalid, SUPERVISOR would correctly return an appropriate error message to the caller. However, if another PD DO or EVAL then subsequently executed in the same WHEN slot, but this time with a valid file/directory, SUPERVISOR would erroneously fail the request with a similar error.

For standalone PD DO requests that use a DO limit modifier, SUPERVISOR would not stop processing the DO when the limit was reached if the FLEX search type was :FLAT. This problem is now fixed and as part of the change, extraneous 'Bad Send_Ary Call' display messages seen for DO limit requests are prevented.

Lastly, when SUPERVISOR is now QUIT, any active *OBJECT/FLEX utility currently linked to SUPERVISOR will be terminated immediately. Previously, an active FLEX task could have delayed the QUIT by up to 2 minutes.

Improve error displays in FLEX PD requests. Allow a blank as separator for level for FLEX calls.

Implement PDSUBKINDLIST.

Previously, SUPERVISOR would not issue a TL command when an AFTER activity set to 'TL' or 'TL 0' was executed. Other TL variants such as 'TT TL', 'TT TL 0' or 'TL 1' would correctly force the SUMLOG release so the problem is easily detoured. This fault has now been fixed.

Contrary to the description of the VL command in SUPERVISOR's on-line HELP, the VL- command was previously unable to volume delete FLEX CD Image or Disk Farm volumes. This anomaly has been corrected and the VL syntax has been modified to allow these types to be deleted:

  -- VL --+- + -+--+- MT --- < unit list > --------------------+----|
          |                                                    |
          +- - -+--+- MT --- < unit list > --------------------+
                   |                                           |
                   +---- -+- SN -+--<serialno> -- <vol.name> --+
                   |      |
                   +- DK -+
                   |      |
                   +- MT -+
                   |      |
                   +- PK -+

By default, any VL - SN command requires both serial number and volume name and, if a volume kind is not specified, MT is assumed. If a VL- of a PK or DK volume is attempted and the specified volume has non-zero backup references then the volume delete will be rejected.

   VL - MT 80
   VL - SN HP0001 TAPEVOL
   VL - MT SN HP0002 ANOTHERTAPE
   VL - SN PK CI0001 FLEXCDIMAGE

SUPERVISOR now returns appropriate error messages for all failed VL- tape unit operations. Previously, SUPERVISOR would have always returned a successful notification in all situations; this long-standing problem is now fixed.

A new priced feature on Supervisor allows wildcards, very fast searches and unlimited results for OPALS in the PD context. The feature is free to those sites with a FLEX licence.

If a wildcard, a file list, a search option, or large (>255) eval limit is detected, Supervisor will fire off a copy of FLEX Inquiry to execute it and pass the results back to the OPAL program.

Supervisor windows have an associated usercode (The one used to log on to the system). To use this usercode to start a WHEN or Define an Opal there were two possibilities. 1. Enter Term User + , then your command and then Term User -. 2. FOR <user>/<password> followed by your command.

Neither of these options were ideal.

It is now possible to use a prefix of FOR <user> without a password, if the <user> matches the logged on usercode or if the logged on usercode is the ODT Security usercode.

SUPERVISOR would fault with a STRING PROTECT @ 800018000 when handling a very large wildcard AF ? interrogation which was greater then 500 characters. Typically, this would have occurred if a page of screen data was accidentally sent with the AF ? command. SUPERVISOR will now handle this situation correctly and also limit the wildcarded command content to 255 characters.

In order to make session logon and Logoff records easier to process the station name of 'SUPERVISOR/SESSION' is now added to these Log records.

This change addresses several issues with EVAL or DO requests that passed to an Opal TT function but subsequently rejected by SUPERVISOR because of certain unusual syntax errors or restrictions. This would leave the originating slot active, left marked as WAIT TT.

In particular, however, the use of TT with the new PD context (see DNote 520.85) caused several issues with EVAL requests that failed. If the requested file or directory passed to the PD context was was not present, the above scenario could occur.

In certain other PD cases called by TT, where the directory parameter passed to PD was invalid, SUPERVISOR would not only leave the originator marked as WAIT TT but also a partially established new slot for the intended EVAL. This slot would remain occupied indefinitely, marked as 'Pending' and could then only be cleared by a SUPERVISOR restart.

Both the above problems are now resolved.

A rare timing window existed where SUPERVISOR could have died with a DIMENSION SIZE ERROR @ 98259556 fault when attempting to FS a scheduled CONTROLCARD call in the GRINDER process, initiated by certain types of WFL job requests from OPAL scripts. The attempted FS could have caused inadvertent corruption of certain MSG event notices leading to the fault. Although the FS SETSTATUS error was initially fixed by DNote 520.86, this change did not successfully address all cases of the problem which are now addressed.

The PRINT modifier may now prefix any MAIL command, directing the output to a print file. This is useful for generating reports using the recently revised LOG comamnd enhancements. Some formatting issues with printed command reports for destinations considered to be MAIL-compatible by SUPERVISOR have been addressed.

This change supports the new WRITE method for OPAL string variables as described in OPAL DNote 520.64. Please refer to this note for more details.

The change made in Version 520.71 would cause a 'setstatus error' when attempting to FS Supervisor housekeeping jobs. This problem has been corrected

PD is a new context to access file directories. It is the same as the implicit Directory context in FLEX. At this stage, PD context OPALs can only be invoked by a Do, Test, /, or Eval. The directory to be searched is placed after as a parameter, e.g.

TT DO SAFEREM A/B ON C TT EVAL (PD:SEGMENTS > 1000) DISP (TITLE,,SEGMENTS) SYMBOL/=

If no '/=' is present, Supervisor assumes that it is a single file, as in the MCP's PD ODT command. If the '/=' is used, a maximum of 255 objects will be returned. This restriction may be lifted in future implementation.

Just as in the MCP PD ODT command, an unsigned integer can be placed after to restrict the depth of the search: e.g.

TT / PD (META)OBJECT/= ON SYSPK 3

Flex Inquiry Reports and ODTSequences are compatible with Supervisor and can be used directly. However, some of the intrinsic reports for :CAT and :CAT,ATT are badly formatted due to the differences in ODT and CANDE screen handling.

In the future, clients with a FLEX Inquiry licence, will be able to use the full power of FLEX from Supervisor, including wild cards, high speed searching, and unlimited returned objects.

Previously, commands such as 'AF - <time> ON DATE < dd/mm/yy:@=' would have caused all activities to be deleted for the time given on ALL days regardless of any ON DATE specification associated with the activity. The correct behaviour is to only delete activities that have a specific ON DATE LESS than the target date provided. This behaviour has been corrected.

SUPERVISOR will now give an error if an attempt is made to delete all ON DATE activities for a date in the future. For any '< ON DATE' activity deletions, a specific time or time range is always required for the command to be actioned; the Supervisor manual incorrectly shows an example command without this requirement.

The new SHOW PERM command displays an unsorted list of all Magus Permanent configuration variables and their values. Both string and real values will be displayed separately in their own list. Note that any CR (carriage-returns) embedded in a permanent string variable will be shown as the '^' character to allow easy identification. This change also affects strings contents shown in a SLOT or SHOW GLOBALS command.

This change supports the new TRIM log file implementation described in OPALTAPELIB DNote 520.08.

The change discussed in DNote 520.77 did not correctly handle basic Windows Telnet clients. After transferring to the window and the WS splash screen displayed, commands would be accepted but no responses would be returned. This problem has been fixed.

Previously, on 5.2 DMSII systems, it was possible for SUPERVISOR's DBSHANDLER task to hang on a NO FILE condition on a database CONTROL file when handling a DBS function call or a VDBS context request. This occurred because the CONTROL file family was incorrectly returned to SUPERVISOR by MAGUS when providing the necessary information to allow linkage to the database. This problem is now fixed.

This change will now cause any such NO FILE conditions associated with the DBSHANDLER task to be automatically NF-ed by the maine SUPERVISOR stack.

The TT USE SILO DSI_SERIALNO now correctly sets the configuaration variable TL_SILOKIND to DSI_SERIALNO instead of DS_SERIALNO.

The StateTime attribute would often return the wrong value for freeze control libraries which were in a wait state.

This problem has been corrected.

SUPERVISOR will now automatically detect the screen page height and width from the session properties of a T27-compatible emulator when a SUPERVISOR COMS window is activated. This means that T27 settings larger than 24x80 will have SUPERVISOR's TERM settings for that station set automatically. Previously, TERM would have to be manually entered.

If an HTTP WHEN is started without a UserCode, the UserCode associated with the HTTP Request is assumed by the WHEN. If an HTTP WHEN is started with a UserCode, then only HTTP Requests with a matching UserCode will be sent to the WHEN.

A security restriction in the use of TT function calls from OPAL scripts running under the ODT Security usercode has been relaxed. This change provides consistency with certain actions issued by the ODT Security usercode from both a COMS windows (using TERM USER) and the TT function.

Also, this change resolves inconsistencies in the use of USER context OPAL scripts; it should be emphasised that such scripts can only be executed by SECADMIN-capable usercodes and the ODTSECURITY usercode (as seen in the TT USE response).

On MCP 47.1 systems, SUPERVISOR would have faulted with the following fault during closedown after attempting to use the OPAL WFL function:

  SUPERVISOR:Object DELINK_EVENT_FROM_QUEUE: Not provided in Interface

SUPERVISOR and FLEX will now both support OPAL strings up to a maximum size of 2,000,000 characters; previously this limit was 393,209. All string operations are supported by this change except for storage into PERM and CONFIG variables and this limit remains at the previous value.

The PRINT statement will now correctly print strings up to the new size specified above. Previously, only the first 65536 characters of the string would have been printed. Also, the PRINT modifier may now be used with all varieties of the SHOW command.

SUPERVISOR will now correctly delink the MAILLIB library after a MAIL QUIT command; previously this did not always behave as expected.

Specifying a maximum evaluation limit of zero for any EVAL or WHEN command will now cause that EVAL or WHEN to be checked for syntax only and will not be invoked. This has special relevance for "in-line" OPAL commands passed to the TT function, allowing them to be verified before use. For example:

     $A:= TT("EVAL " & $SITUEXP & " [0] DO LOGOPAL");

If the above statement is accepted by SUPERVISOR, compiling the in-line SITUation specified in $SITUEXP, then "OK" will be returned to TT (and therefore stored in $A). The TTLASTERROR flag will be also set to ON if EVAL has failed.

Also, on fast MCP systems running with the SO AUTOFS option set, it was possible for SUPERVISOR to fail to FS certain of its housekeeping tasks if the system schedule was held (HS). This could cause SUPERVISOR to stop responding until the scheduled entry was manually FS-ed. This problem is now fixed.

SUPERVISOR will now correctly report all global variables in the response to a SHOW GLOBALS command. Previously, the list would have been shortened by one entry.

The OPAL DUMP response has been changed slightly to improve the presentation layout. Any in-line OPAL that generates a DUMP or faults with a slot dump will now show the original in-line command in the analysis.

In addition, a SLOT command used for an active in-line OPAL will also now show the original in-line command that was used. For example:

  EV ? #5
                   ----- SUPERVISOR WHEN STATUS FOR SLOT 5 -----
  W 211*22665 WHEN INLINE_LOGEOJ_5   DO   INLINE_5    RUNNING
                                   TIMES:CPU=00:00:00,IO=00:00:00,ET=00
        0 evals
        Original IN-LINE Opal:
        WHEN (LOGEOJ:TRUE) DO (SHOW(LOGMAJOR,",",LOGMINOR,/,LOGTEXT))

Previously, SUPERVISOR will trigger housekeeping of released SUMLOG files but only after a TT TL command had been used. After the TT TL, SUPERVISOR would copy all SUMLOGS on the DL LOG family to that specified by USE FAMILY FOR LOGS and, optionally, execute a WFL job to process each log in turn. However, this mechanism did not handle other released SUMLOGs created between TT TL commands.

Now, a new SUPERVISOR SO variant called AUTOTL has been implemented. If AUTOTL is set then SUPERVISOR will automatically detect all SUMLOG file releases (by ODT TL, TT TL and log size limit) and initiate housekeeping on that file; any earlier missed log files will additionally be processed. The TT TL command still causes any active WHEN sessions to be split prior to the TL and the optional parameter is passed to the USE JOB AFTER TL job. Usage of the TT TL command now does not cause SUPERVISOR to pause unconditionally for 6 seconds.

If AUTOTL is reset or USE FAMILY FOR LOGS and DL LOGS is the same family, then the SUMLOG(s) will not be copied or removed.

The SO option NOLOGREADER has been deimplemented.

Internal change.

The MYSELF attribute has been extended to provide information about EVAL log-based requests, as configured by the user. New parameters include EVSTARTDATE, EVSTARTTIME, EVENDDATE and EVENDTIME for user-specified date and time ranges; EVLOGNO for a specified SUMLOG number and EVMAXLOGS for the MAXLOG modifier. Note that DOLIM and EVALLIM have been added for all WHEN and EVAL options.

This change supports the new LOG context attributes, such as LOGRAW, LOGTITLE, LOGSEQNO, as discussed in OPAL GSTABLEGEN DNote 520.36.

SUPERVISOR will now automatically detect any SUMLOG release, either by all TL commands or because the SUMLOG file was full. This allows SUPERVISOR to keep track of log sequence number changes for the LOGSEQNO attribute, as described above, and now offers a mechanism for automatic processing of all released SUMLOGS, not just those created by a TT TL command. Further enhancements enhanced are planned in this area.

For log-based EVAL requests, the user can specify the SUMLOG start and end criteria for the search, using the '@' modifier. This syntax has been extended to allow a differential time value instead of a fixed date or time by using the keyword 'BACK', followed by an integer value and optional units of time. This value is then used to calculate a log start time, using the current date and time as base, and scan log(s) to the end of the current SYSTEM/SUMLOG. As with other EVAL requests, multiple SUMLOGs will be traversed if required.

The full syntax for '@' date and time assignments is shown below:

  -/1\--- @ -+- <datetime> -+--------------------------+-------+
             |              +-- TO ---+-- <datetime> --+       |
             |              +--  -  --+                        |
             +------------------------+-+----------------------+
             +- BEFore -- <datetime> -+ +- AFter -- <datetime> +
             +- BACK ---- <integer> ----+--------------+-------+
                                        +--- DAYs -----+
                                        +--- HOURs ----+
                                        +--- MINutes --+
                                        +--- SEConds --+

Some examples:

   EV LOG [@BACK 2 HOURS]           Start time set to 2 hours earlier
   EV LOG [40 @BACK 90]             Max 40 evals, start time 90 seconds
   EV LOG [@BACK 3 Days MAXLOGS 2]  Start time 72 hours ago, scan 2 logs

The maximum integer value that can be used with BACK, for all time units, has been arbitrarily set to 9999;

Note that SUPERVISOR always expects an EVAL limit to be the first modifier in any EVAL log specification and that any @BACK time specification with a LOGNO or TITLE modifier may return indeterminate results.

The DEFINED attribute has now been modified to provide better checking for program existence when the caller is running under a TERM USER setting or FOR <USERCODE> modifier. Previously, DEFINED would only check the global dictionary and not attempt to search the local usercode set.

Thus, if DEFINED("ODTS TEST") was called from an Opal program running under the META usercode, the function will only return OFF if the program entry cannot be found in neither the local usercode directory or the global (*) directory. Note that the DEFINED attribute will now accept an usercode prior to the program name e.g.

   DEFINED("SITU (META)EX_SITU")
   DEFINED("(FLEX)EX_NAME")

If the DEFINE ? command is issued from any SUPERVISOR interface which has an associated usercode (i.e FOR <USERCODE> or TERM USER setting), SUPERVISOR will now search its global OPAL dictionary as well as the local usercode directory. Previously, only the usercode dictionary would have been searched; if a usercoded search finds a global dictionary entry but not a local item then SUPERVISOR automatically inserts the text 'FOR *' prior to the DEFINE content. These rules also apply to the TT function but not KEYIN, since the latter function does not inherit the usercode for any of its commands.

Previously, any EVAL, DO or WHEN command that was process by an Opal program using the TT function would not have inherited any usercode, accesscode or chargecode from that slot. This problem has been resolved; SUPERVISOR will automatically confer the originator settings to the new WHEN slot.

Also, an Opal DUMP and SLOT response will now show any USERCODE, ACCESSCODE and CHARGECODE associated with the active slot.

The syntax is now the same for the FILE and DIRECTORY variant of the Respond function,

    Respond(<filekey>,<mimetype>,<filespec>,<url>)
      <filekey>::=FILE | DIRECTORY

The TTLASTERROR self-knowledge attribute has been implemented to allow callers of the Opal TT function to know whether the command was successfully processed by SUPERVISOR. Please see TT HELP TTLASTERROR for more information.

The OPAL DUMP statement could have caused an INVALID INDEX at 26457000 during the printing phase of the dump. This problem, caused by certain unsolicited messages being handled by SUPERVISOR prior to the printing of the DUMP, is now fixed.

SUPERVISOR will now correctly terminate EVALs and WHENS with limits imposed on the number of evaluations or ODTS entries. Previously, certain EVALs and WHENs would only have terminated after the limit had been exceeded.

The CALL COMMAND feature discussed in DNote 520.33 would only work correctly for OPALs running under a FOR usercode. For non-usercoded calls, SUPERVISOR would have erroneously invoked a CALL DO instead of a CALL COMMAND. This problem is now fixed.

In addition, inconsistencies in the error-reporting for failed CALL variations have been addressed.

A new OPAL function, called TT, has been implemented for SUPERVISOR only. This string function, similar to KEYIN, permits the user to process any TT command (without the prefix) and cause the calling OPAL to wait until the command has been completed. The difference from KEYIN is that special slot commands such as WHEN, ONCE, EVAL and DO will also cause the caller to wait, instead of processed indepoendently. Like KEYIN, TT returns the response of the SUPERVISOR command as the function string result.

      ---   TT ( <string expression> ) -------------------------

Previously, sharing variable information between OPALs in this way was only possible using GLOBAL variables and then continuously checking for any called OPAL programs to complete. The TT mechanism gives much greater control to the caller.

All SUPERVISOR commands passed with the TT function will always return a response. If the command is an in-line OPAL or DEFINE that fails syntax, the error list will be returned. THE TT function can *only* be used in ODTSEQUENCES.

The following example would display the response from a TT FP command:

    DEFINE + ODTS FP:
       $R:= TT("FP");
       SHOW($R);

    DEFINE + ODTS EVALTEST(MSG):
       $R:= TT ("EVAL (LOG:TRUE) DO LOG [50]");

W 218 65145 WHEN MSG DO EVALTEST (WAIT TT #5) 04

                                  TIMES:CPU=00:00:11,IO=00:00:00,ET=00:0
       16 evals, 16 ODTS entries

                                  TIMES:CPU=00:00:00,IO=00:00:00,ET=00:0
       44 evals Limit 10000 @ 17:08:01 18/01/07 (0% of #000296), 44 ODTS

NOTE: The WHEN command may only be used inside a TT function if there are limits imposed on the number of user-specified evaluations and/or ODTS entries. If neither of these limits are provided, the WHEN will be rejected. For example, the following WHEN will be permitted:

    $Z:= TT ("WHEN MSG [50] DO MSG");
    $Z:= TT ("WHEN MSG DO MSG [100]");

The response to a TT ENTER command had the word compiled miss-spelt as complied and some singular values were reported as plurals. Ex. 1 commands

The error messages printed by the Enter command for programs which did not compile now include the program name.

Ex.

    ERROR : ERRORS FOUND IN ODTSEQUENCE DEFINITION BOB_DAYSTAPES

    ERROR : ERRORS FOUND IN ODTSEQUENCE DEFINITION

The CARTSCRATCH TAPEDB attribute, used to determine if a tape is assigned to an ACSLS scratch pool, now returns the correct value in the silo software. This setting can be change in the Unisys StorageTek software using the TK <serialno> + SCRATCH command.

Internal Change in HTTP Context.

Previously, using the DBS Opal function would cause the DBSHANDLER process to E-DS if the database being interrogated received a fatal database error. For example, a DMSII OPENERROR #72 could occur when the database was undergoing an exclusive DMSII reorganization.

SUPERVISOR will now detect such failures when accessing the selected database and return a meaningful error message back to the DBS caller:

   ERROR:DBS #1234 DMSII OPENERROR DETECTED

   ERROR:DBS #1234 UNEXPECTED MONITOR_SUPPORT ERROR

On certain recent MCP and PRINTS levels, it is possible for SUPERVISOR to receive a PRINTDEFAULTS ATTRIBUTE INCORRECT SYNTAX error when switching to a new USE DESTINATION setting. Although SUPERVISOR was generating an incorrect PRINTDEFAULTS assignment, earlier Unisys releases seemed to ignore the error and set DESTINATION correctly. This problem is now fixed and USE DESTINATION should work on all releases.

Internal change only.

Modify Respond Directory function.

Printed slot dumps will now list all Global variables with their values.

A message from a task started from a Supervisor window could cause the Supervisor/Window task to fault with a .message size error'. The problem would happen if TERM MSG was set to True and TERM User was active.

Add new HTTP Context.

This change corrects a bug introduced in version 520.42 which caused lookup functions used in the Show ODTS statement to fail.

SUPERVISOR will now attempt to send a QUIT to the active RECORDER process when a USE TASK .. FOR RECORDER command is processed. This will ensure that the Metalogic RECORDER process will automatically terminate should a site-customised RECORDER be assigned.

SUPERVISOR will now deactivate any USE BDNAME assignment if a PRDEF print statement is detected in the output generated by any OPAL program. The PRDEF allows the caller to tailor his own PRINTDEFAULTS requirements which would normally be overridden by a BDNAME setting.

SUPERVISOR now supports a mixed tape robot environment and both DSI and Unisys-StorageTek hardware can be simultaneously supported. Tape requests to use the DSI robot are identified by the specification of job SCRATCHPOOLs whereas all other robot requests will be routed to the Unisys hardware, if applicable.

To support the above environment, the USE SILO command has been extended to allow an additional modifier to the the DSI variants:

   -- USE -- SILO --+-- UNISYS -------------------------+------|
                    |                                   |
                    +-- DSI -----------+---  + UNISYS --+
                    |                  |
                    +-- DSI_SERIALNO --+
                    |                  |
                    +-- DSI_NOTM ------+

   -- USE -- SCRATCHPOOL --+-------   -  --------+------------|
                           |                     |
                           +---+-- <pool id>--+--+
                               |              |
For example:                  +<<--- ,  ---- +

       USE SILO DSI
       USE SILO DSI+UNISYS
       USE SILO DSI_NOTM+UNISYS
       USE SCRATCHPOOL DLT35POOL, DSIPOOL
       USE SCRATCHPOOL -

This change supports the extension to lookup functions described in Opal Dnote 520.34

If a SUPERVISOR-invoked WFL job failed syntax or was unavailable then the GRINDER process would handle the failure correctly and display GRINDER FAULTED whilst trying to provide an information message. This problem is now fixed.

A new USE variant, BDNAME, has been implemented to help control SUPERVISOR and TRIM printed reports. If BDNAME is set, all print files generated by SUPERVISOR will be held under SUPERVISOR's usercode and prefixed by the BDNAME setting. The second level of all print files will be set to the current date in YYYYMMDD format.

   --- USE  ---  BDNAME  ---+---   -      -------+----------------|
                            |                    |
                            +--- <identifier> ---+

     (SUPERVISOR)SUPBD/20061004

The BDNAME setting should only be used by those sites that do not want SUPERVISOR's print files to be automatically handled by the PrintSystem. Any current BDNAME assignment can be cancelled using the '-' modifier.

The OPAL print statement will now handle empty lines of text inside an OPAL string expression. If the following string fragment was printed by the PRINT statement:

   ... /,"ABC",/,/,"DEF" ....

This change provides enhancements in the way that TRIM handles tapes created by the Unisys TAPESTACKER utility. Although TRIM will not track the contents of a stacked volume, both APPEND and UNSTACK operations will be recorded in the METATAPELIB database.

SUPERVISOR now limits the logging of tape usage by a task to its first use. Previously, activities such as TAPESTACK append operations caused excessive logging to the TAPELOG and unnecessary updates to the tape's usage count.

When TAPESTACK unstacks a tape volume, the unstacked tape is an exact copy of the original volume, except for the destination tape serial number. Because of this, these tapes are written as UNLABELLED tapes and will appear as such in the METATAPELIB4 database. There is no additional notice provided by the MCP to help TRIM to detect the new tape so SUPERVISOR has been changed to detect all tape VOLUME ONLINE records.

If a VOLUME ONLINE entry is seen for a tape that is marked as UNLABELLED in the database, the tape record will be updated with the correct volume id and file id and the UNLABELLED status is turned off. The ACCESSTIME and ACCESSDATE attributes of the tape are changed to reflect the timestamp of the VOLUME ONLINE. Please note that, at this time, because the created tape is potentially very old, no TRIM rules will be applied unless a manual SR is performed. We may change this behaviour in future releases of the software.

Typically, if AUTOUNLOAD is OFF for the unit, the VOL ONLINE is detected immediately. If AUTOUNLOAD is ON, the database will only be updated when the tape is reloaded.

The tape log entries appear as:

  12:38:00 Evt: Unlabelled update [HP3009] STACK1/FILE000
  12:38:00 Evt: Created [HP3009] UNLABELLED by #159
  12:35:19 Evt: New Vol [HP3009] UNLABELLED by #159

Various printed SUPERVISOR reports, with headings on separate pages, would generate an additional heading lines consisting of null characters. Although not evident if the print file was physically printed, these lines would be seen if the printfile was saved to a PC or emailed. This behaviour has been corrected.

If a VL Opal faulted, such as DIVIDE BY ZERO, SUPERVISOR would fault with an INVALID INDEX when taking an OPAL environment dump. This problem is now fixed.

Under certain circumstances, it was also possible for a SUPERVISOR PRINT process to fault with INTEGER OVERFLOW at 26484110 whilst SUPERVISOR was handling a MCP notice. This problem is also fixed.

The on-line help for the VL command has been updated to reflect the revision applied in SUPERVISOR Dnote 520.12.

The mechanism supporting custom versions of the RECORDER program, deleted by SUPERVISOR change 520.18, has been re-implemented. This allows old, customised RECORDERs to be established using the TT USE TASK.. FOR RECORDER command. Note that any customised RECORDER cannot be named *METALOGIC/SUPERVISOR/RECORDER since this is the default Metalogic program name. SUPERVISOR supports the new RECORDER library interface, described in Dnote 520.18, if no USE TASK is specified.

Supervisor 'Command' Opals can now be called from either Commands or ODTSequences using CALL COMMAND <command Id>.

This change also corrects the error message displayed when recursive Calls go more than 16 levels deep. Previously if a string expression had been evaluated after the first call, the error message was corrupted.

A bug where a large Log event could cause Supervisor to fault has also been corrected.

This change fixes a cosmetic problem which could happen when an active stand-alone Do was recompiled. A WHEN ? command would correctly show a "t" as a prefix to the name, indicating that the new code would not be used until the slot was restarted. The problem came if the ODTs subsequently performed a CALL DO. In this case the "t" was incorrectly cleared and the 'code changed' count was incorrectly incremented. The original ODTS code continued to run correctly. This problem has been corrected.

If an active Situation was redefined and the most recent Situation to be started was an 'inline' Situation, Supervisor would fault. This problem has been corrected.

A similar problem existed if an ODTS executed a WHEN statement and the last Situation to be started was 'inline'. This has also been corrected.

Previously when entering commands from a Supervisor window the TT prefix was required for some commands but not all. DEFINE did not need TT but DO did.

Now all Supervisor commands can be entered without a TT prefix. For commands which conflict with MCP commands the ODT prefix can be used. So to use the MCP DO (Diagnostic Option) command use ODT DO.

The HELP command list all of Supervisor's top level commands. Any command which conflicts with an MCP command has an exclamation mark (!) in front of it.

MCP commands which now require an ODT prefix are: DO;HO;HS;OK(*);PR(*);QUIT(*);REMOTESPO;RESTRICT;SV(SAVE);SH(SHOW);SS; TL. Commands marked (*) do not require a prefix of ODT if preceding a mix number.

Ex. 1234Pr 50 or ODT PR 1234 50

Any MCP command can be prefixed by ODT from a Supervior window.

The change applied by DNote 520.27 caused the use of SUPERVISOR's HS command to generate an INVALID OPERATOR fault at 63770500; this problem is now fixed.

DEFINE + is now able to define routines which are in use in an active Slot. The new code will not be used until the slot is stopped and restarted. Setting a new Supervisor Option NoDefActive will restore the previous behavior. The WHEN ? command will add a prefix of 't' to the name of any Opal routine which has been redefined in this way.

A new Define variant DEFINE * has been introduced to allow the redefinition of active Situations or routines linked to Situations. If DEFINE * is used then the new code will be used on the next evaluation for Situations, or Entry for other routines. Until the new code has been loaded, a WHEN ? will show a prefix of 'a' before the name of any routine where the code will be replaced. This command allows the code of an active event based SITU/ODTS to be replaced without having to stop and start the routines which could cause some events to be missed.

Since changing the code of an active slot may raise security concerns, the change will be logged. If the change is made from the ODT or a Supervisor window, a message is displayed for each affected slot. If the change is made from an Enter file, a message is logged to the Supervisor Log session. (TT WS lists this session number). A message is displayed after the Enter specifying how may slots were affected and also show the Log command which could be used to see the detail. When the new code is actually loaded (on the next Eval or Enter) an 'Situ reloaded' or "ODTS reloaded" message is displayed, indicating

  that either new Situation or new ODTSequence code has been loaded.

In order that Enter files can be created with DEFINE * instead of DEFINE +, a new modifier of * has been added to the SAVE command. TT SAVE * DEF <pattern> or TT SAVE * SCHEDULE AS ..... will create a file which has DEFINE * instead of DEFINE +

Previously, SUPERVISOR used an internal mechanism to generate its own formatted system messages instead of calling DISPLAY. This process has been changed; the SUPERVISOR codefile has now been assigned an MP IDENTITY of "SUPERVISOR" and all internal messages are now generated by the DISPLAY statement.

This will affect any MSG-based WHENs that track internal SUPERVISOR messages since such messages will now have the following characteristics:

    MSGCAT = MSRDISP          (was  MSRPREFMT)
    MSGNO  = 13               (was  34)
    IDENTITY = "SUPERVISOR"   (not set previously)

However, DISPLAY messages generated by OPAL code will continue to use the original mechanism and retain the identifying characteristics of MSGCAT=MSRPREFMT and MSGNO=34.

In previous versions of Supervisor the 'Last Used' date and time returned for ODTSequences which had only been used in a CALL DO statement could seem inaccurate.

To avoid excessive overhead in writing to the Schedule file , when updating the 'last Used' details, the time was only updated the first time the routine was called.

Subsequent improvements to how 'called' code is loaded have allowed the improvement of this mechanism. The 'last used' details will now report the last time the called code was loaded.

If ODTS A is running a slot and Calls ODTS B every minute for an hour then 'last used' will be the time of the first call. If ODTS C is started and calls ODTS B then 'last used' for ODTS B will be updated to the time of that call. If ODTS B is redefined then 'Last Used' will be set to 'never' until it is called again.

The display for a TT DEF ? ODTS <pattern> command adds a prefix of 'c' to the 'Last Used' detail if the most recent load of the code was for a 'Call Do'.

This change adds help for the TT REC SNMP command. See TT HELP REC for details.

This change supports the OPAL TDADDRESS enhancement that permits screen addressing greater than 24 rows and 80 columns, as described in OPAL DNote 520.27.

Previously, a DEF ? dictionary response could be corrupted if a SITUATION with a long context (e.g. PER=PK,MT,LP,DK,HY..) was displayed. Now, SUPERVISOR will truncate such long contexts in the display and will indicate as such with trailing text "..".

The SPECIFY handling by INPUT described in DNote 520.21 has been changed. The row and column values have been transposed so that row is now the first 3-digit field followed by column. Also, the values returned are now 1-relative instead of 0-relative i.e. specify in the 'Home' location now returns "SPCFY001001" instead of "SPCFY000000".

The above changes make INPUT align with the row and column requirements of the TDADDRESS function.

The OPAL INPUT function can now be used to detect the use of SPECIFY for a script waiting on user input. Transmitting SPECIFY causes the screen location, where Specify was pressed, to be returned to the caller. When INPUT receives a Specfiy location result, INPUT constructs a special string value with the prefix "SPCFY", followed by a pair of 3-digit string values. These decoded values indicate the column and row position on the screen where SPECIFY was used.

For example:

    $ZZ:=INPUT;
    If $ZZ HDIS "SPCFY" Then              % SPCFY000000 means HOME
    Begin
       $ZZ:=DROP($ZZ,5);
       #COL:=DECIMAL($ZZ.SPLIT(3));
       #ROW:=DECIMAL($ZZ);
       SHOW("SPECIFY COL=",,#COL,,"ROW=",,#ROW);
    End;

The change described in DNote 520.15 caused SUPERVISOR to enter a CPU loop if a VL context EVAL was issued stand-alone (i.e. no DO or DISPLAY action). This problem is now fixed.

Additional diagnostics information will be provided by the OPAL DUMP mechanism and is of relevance to Metalogic personnel only. Slot dumps printed via the MAILLIB library will now not show unexpected '?' characters in the emailed attachment.

The SUPERVISOR implementation of the RECORDER program has been changed. RECORDER is now initiated by SUPERVISOR using a library linkage instead of direct initiation. SUPERVISOR links to the RECORDER library via the RECORDERLIB SL which is automatically established by the INSTALL utility. The USE TASK.. FOR RECORDER command will be deimplemented.

This change allows RECORDER to be more freely avail;able for other Metalogic software; FLEX Inquiry has now been extended to support its own version of the OPAL RECORD statement. Please see FLEX LIBRARY DNote 510.22 for more details.

Previously, changing the USDATES option using the SO command required a TP CLOSE command to be issued, or TAPELIBUPDATER to be restarted, for the change to be recognised by TRIM. This behaviour has been changed so that any USDATES changes are immediately advised to the TRIM software.

SUPERVISOR will no longer assign arbitrary internal chargecodes to the various tasks that are processed for its housekeeping and command functions. By default, all internal processes will be assigned an empty CHARGECODE unless a global setting has been applied using the TT USE CHARGE command:

   ----------- USE ----  CHARGE ---+------  -  --------+-----------|
                                   |                   |
                                   +-- <destination> --+

If a site wishes to assign custom CHARGECODE to SUPERVISOR's processes, this is possible by using the source SUPERVISOR/ASSIGNCHARGE that is available in the Metalogic release container. This file can be modified, recompiled and then replacement-bound into the SUPERVISOR codefile. More instructions on this procedure may be found in the Metalogic SUPERVISOR Reference manual.

An OBJECTS call using the VL context will now correctly return a list of matched volume serial numbers. The implementation change described in SUPERVISOR DNote 521.13 causes the OBJECTS list to be corrupted. Also, an extraneous display shown during a VL EVAL has been removed.

The HI998 mechanism for terminating looping OPALs has been removed as its effect did not improve on the usual HI999 alternative.

On recent MCP versions for both 51.1 and 52.1, it was possible for SUPERVISOR to continuously fault in the MCP STACKSWAP procedure (INAVLID INDEX at 24180000) or, on more recent MCP versions, generate a STACKSWAP FAULT memory dump and killing SUPERVISOR with an ILLEGAL SWAP. This problem has been identified as an MCP issue but Unisys have provided a suitable detour which has been applied by Metalogic.

SUPERVISOR now handles VL context OPAL scripts using the EVALREADER mechanism for scans of the system catalog. Previously, SUPERVISOR scanned the catalog directly in its main stack and could be very CPU intensive if the Volume Library was large. The revised process allows processor control to be passed back to the system at regular intervals.

SUPERVISOR will now permit VL - commands for volumed tapes that are not currently loaded or available on the system. The extended syntax requires the serial number of the volume and the volume name, as specified in the Volume Library otherwise an error will be returned.

The full syntax for VL is shown below:

  ----- VL --+-- + --+--+-- MT --- < unit list > ---------------+----|
             |                                                  |
             +-- - --+--+-- MT --- < unit list > ---------------+
                        |                                       |
                        +-- SN -- <serialno> -- <volume name> --+

Changes to an ODTS which is in use by one or more slots, via 'CALL DO', will now be correctly reflected in the running slots. Previously the new version would not be used until the calling ODTs was restarted.

Attempts to delete an ODTS which is being called by one or more slots will be rejected. The slots where is being used will be reported.

Error messages due to attempts to redefine or delete and active ODTS will now report the slots where it is active.

Previously, every DBS call or database processed by the VDBS context would have caused an unnecessary programdump for the DBSHANDLER task, even though the DBS call was successful. This problem has now been fixed.

A new SUPERVISOR option called NOENTERLIST (37) has been implemented. If set, the taskfile listing generated by an ENTER command will be inhibited. This allows sites to readily syntax check large ENTER files with the SYSTEM/OPAL compiler and thus prevent the generation of even larger printfiles from the OPAL compiles when the file is finally ENTERed.

This behaviour can also be controlled using dollar ($) options in the ENTER file. If a listing is required with the NOENTERLIST option set, the inclusion of a text line consisting of '$SET LIST' or just '$LIST' will force a listing to be generated after that line. Similarly, a '$RESET LIST' will inhibit a taskfile print file if NOENTERLIST is not set. Using multiple SET or RESET directives within the ENTER file will control the content of the generated print file.

By default, the NOENTERLIST option is RESET. Note that $SET LIST or $RESET LIST will not be recognised by SUPERVISOR if they are used inside a DEFINE block.

Previously, DO commands initiated from a MARC session using the TTINTERFACE Directive could cause the MARC station to be unresponsive for 60 seconds if the script took longer than this to run. The MARC user sees "No response from SUPERVISOR after 60 seconds' appended to the response. Typically, such DO files would contain various WAIT statements.

Now, when the first WAIT statement is executed by a MARC-initiated script, SUPERVISOR will automatically signal the TTINTERFACE directive to return any queued responses to the MARC session. This prevents the non-responsiveness problem and any display output generated after the WAIT (such as SHOWs) will be discarded, as before.

This change addresses several important issues with OPAL WAITS and internal fault handling.

1. An OPAL WAIT(0) statement will now allow the processor to be released so that pending SUPERVISOR events and commands can be processed. Previously, very tight OPAL WHILE or DO blocks with WAIT(0) statements would have been very difficult to abort.

2. SUPERVISOR will now gracefully go to EOJ should a major fault occur in certain critical code blocks. Previously, SUPERVISOR would have attempted to resume after the fault, possibly causing an infinite loop repeating the same error. Such problems are very rare.

3. A HI999 to SUPERVISOR will attempt to abort any running OPAL code that appears to be looping. Now, if a HI 998 is sent to SUPERVISOR then the currently active OPAL program will be unconditionally aborted, even if it is NOT looping. This is a last resort option to deactivate looping WHENs that may not have been policed by SUPERVISOR.

If an OPAL SHOW statement was passed the maximum string length of 393,210 characters, it was possible for SUPERVISOR to enter a hard processor loop that could not be interrupted. This problem is now resolved.

The TT SHOW GLOBALS will display a list of all global variables, with their current values.

This change also fixes a bug where the use of MYSELF(HeapIds) could cause a fault if no variables had been used)

SUPERVISOR will now terminate any OPAL script that uses TAPEDB cartridge attributes (such as CARTSLOT, CARTLIBRARYID) when its USE SILOKIND has not been established. Previously, SUPERVISOR would have displayed the following erroneous message for each call, potentially flooding the system:

   SUPERVISOR:SILO ATTS UNAVAILABLE:NEEDS OP+SILO

If USE SILO is not correctly set, any attempt to reference these attributes will now cause the OPAL to be terminated:

This change supports the PRINTS records formats for 5.1 and 5.2 MCP levels and allows for several new PRINTS context attributes to be implemented.

Version 510.62 introduced a bug in 'SAVE SCHEDULE AS ...'. In certain circumstances, when Supervisor was busy, the task DECOMPILE/SCHEDULE could fail with an invaild index. This problem has been corrected.

The OPAL KEYIN function will now inherit any usercode, assigned to the slot using the FOR modifier, prior to executing the KEYIN command. Previously, any FOR assignment would have been ignored.

In addition, using the FOR modfier will now permit usercodes, with SYSADMIN and SYSTEMUSER attributes assigned, to inherit these privileges automatically for SUPERVISOR activities such as AFTER, WFL, DO and WFL.

On Supervisor versions prior to 510.66, setting backtrack mode to verify would cause the backtrack process to fault.

On version 510.66 backtrack mode was always treated as automatic, no matter what the setting.

In Previous versions moving the clock forward would only be recognised instantly, if a situation of type LOG was active. If no Situ of type LOG was active it could take in indeterminate time before backtrack would be invoked.

Backtrack schedule now works as intended.

SUPERVISOR will now provide more comprehensive schedule information for an AF ? ON DATE interrogation. Previously, such commands would only show activities explicitly assigned by an ON DATE modifier and all other activities that might have executed in that date were not displayed.

This behaviour has been changed. An ON DATE interrogation will now show all activities that should be executed on that date, including actions such ON NTH DAY, ON <DayofWeek>, ON WORKDAYS, IN WEEK etc. and housekeeping activities such as SAVE SCHEDULE, PRINT SCHEDULE.

On earlier versions of SUPERVISOR, the following might be returned:

  AF ? ON DATE 11/3/2006

    ----- PENDING SCHEDULE after 23:59 ON SATURDAY 11/03/2006 -----
   1: ON DATE 11/03/2006 TT DO SATURDAY

  AF ? ON DATE 11/3/2006

   ----- PENDING SCHEDULE after 00:03 ON SATURDAY 11/03/2006 -----
  1: SAVE SCHEDULE
  2: PRINT SCHEDULE (EXECUTED LAST)

   ----- PENDING SCHEDULE after 00:30 ON SATURDAY 11/03/2006 -----
  1: TT DO 0030

   ----- PENDING SCHEDULE after 08:00 ON SATURDAY 11/03/2006 -----
  1: SAVE SCHEDULE

   ----- PENDING SCHEDULE after 17:00 ON SATURDAY 11/03/2006 -----
  1: TT DO SATURDAY
  2: ON 2ND SATURDAY TT DO SECOND_SATURDAY

   ----- PENDING SCHEDULE after 23:59 ON SATURDAY 11/03/2006 -----
  1: ON DATE 11/03/2006 TT DO SATURDAY

This change allows the user to make complex AFTER changes to the SCHEDULE and easily see all scheduled actions for a particular date. The 'testing' of AF dates give confidence that the activity has been correctly assigned whereas before, it was not possible to verify many qualified activities. All possible AFTER combinations are supported by this change.

Also in this change, the following enhancements have been applied:

1. AF ? ON DATE may be used without a military date. All activities

    with *any* ON DATE assignment will be returned for the specified
    time range (or 0-2359 if not present). A military date is now
    permitted without a year e.g. AF ? ON DATE 3/9.  If a year is
    absent, the current year is assumed.

2. The above command may be used with the wild-card filtering

    described in SUPERVISOR DNote 510.62 e.g.

    AF ? ON DATE : =TEST=

    A colon is mandatory to ensure that a pattern is detected
    instead of a date.  Note that AF ? ON DATE mm/dd/yyy with wild-cards
    is permitted.

3. AF ? TOMORROW will now correctly return the next days schedule;

    previously, either NULL SCHEDULE or the listing for TODAY was
    incorrectly returned.

The AF ? wild card interrogation enhancement described by DNote 510.62 did not correctly handle AF ? ON DATE queries unless a wild-card pattern was supplied. This problem is now fixed.

The change described in DNote 510.03 could have caused some corruption of email headers passed to the QUICKMAIL entrypoint when using the MAIL function. This problem has been fixed.

SUPERVISOR will now use the QUICKMAIL entrypoint, as described in MAILLIB DNote 510.11, for any OPAL scripts using the MAIL function. No other functionality has been affected by this change.

Two changes have been made to the AF ? command. If no time specification is supplied then 0-2359 is assumed.

   AF ?    is equivalent to     AF ? 0-2359 Today

A wild card pattern may now be used with the AF ? command. Ex.

   AF ? :SAVE=
   AF ? DAILY:=START=

This change also fixes several bugs in the 'Save' and 'Enter' commands.

The Save command now saves the state of the REC NAMES command.

The USE SILO command generated by a save is now correctly terminated.

The SO command for the option USERNOFOR(2) is now handled separately from other options since it need a 'FOR <usercode>' prefix.

An 'ENTER ODTS <name> REFERENCE <file> will no longer cause all commands other than 'DEFINE ODTS' from being ignored when the <file> is not resident.

In a TT ENTER ODTS <name> FROM ... command, using a <name> which starts with FROM,REF or REFERENCE, no longer causes problems.

It is now possible to run TAPEDB EVALS from a slave TRIM system; this was previously only permitted from MASTER systems. This means that there are now no restrictions on the use of TAPEDB programs running from a slave, though it should be noted that due to the latency of network connections, such EVALS may take some time to complete.

The change described in DNote 510.59 had the side-effect of passing SUPERVISOR's PRINTDEFAULTS specification to WFL jobs started via the GRINDER process (e.g. AF+ START). This behaviour has been corrected.

On rare occasions, the GRINDER process can be DS-ed by SUPERVISOR if it is recognised that GRINDER has taken too long (more than 120 seconds) to process a request. SUPERVISOR will now force a full programdump for both itself and GRINDER to help try and identify the causes of such anomalies.

The change described in DNote 510.56 could have caused SUPERVISOR to mistakenly force terminate a WHEN after being asked to restart by a TT QUIT SUPERVISOR command. This would only have occurred if SUPERVISOR's task history had been changed by an internal fault that had been successfully recovered.

On systems running a small number of WHENs, it was possible for SUPERVISOR to fail to handle increases in the system setting of MAX STACKS. In such circumstances, SUPERVISOR could give multiple INVALID INDEX program dumps until the change was detected. This problem has now been fixed and SUPERVISOR's detection of MAX STACKS changes has been improved.

Since SUPERVISOR has been recently released as a library codefile, it has not been possible to RUN the codefile from the ODT or a REMOTESPO without using PROCESS or ?? (ODT only). Attempts to RUN SUPERVISOR in this way would fail with:

FREEZE FAILED: TASK TYPE NOT PROCESS, RUN OR POSIX

Although only needed when SUPERVISOR must be manually restarted, this is inconvenient and the code has now been changed to automatically re-run SUPERVISOR as an independent task.

Previously, executing OPAL COMMAND scripts of the MESSAGE context did not correctly handle any message parameter that was longer than 15 characters. This problem is now fixed.

Also, if a COMMAND DEFINE has been used to substitute an existing MCP command, the original command may still be used by prefixing it by the keyword 'ODT'.

ODT MSG

Where MSG is a compiled OPAL COMMAND script. As with the general COMMAND implementation, this feature is only applies to Supervisor COMS windows sessions.

If an OPAL lookup expression (e.g. #[MX=SYSTEM/CANDE]) was used in an ODTSEQUENCE or directly in an AFTER executed during SUPERVISOR's AFTERHALTLOAD process, the task would fault with an INVALID INDEX @ 21530800. This problem occurred because SUPERVISOR's mix handling routines were set up after the AFTERHALTLOAD process had been run instead of before and is now fixed.

Internal Metalogic change.

A LOG EVAL command with a specific SUMLOG specified by the TITLE modifier will now not be limited to 10,000 log records. As with the LOGNO modifier, such EVALS will not be restricted in the number of log records scanned.

The recent COMMAND program type discussed in SUPERVISOR DNote 510.19 had several outstanding issues with its first implementation. First, most COMMAND messages confusingly used the term 'ODTSEQUENCE' or 'DO' instead of 'COMMAND'. New messages have been introduced to resolve this anomaly.

Secondly, SUPERVISOR's usual protection preventing the deletion of active DEFINEs was not correctly applied to COMMAND definitions. This meant that deleting or redefining an existing COMMAND that was still in use could have caused validation problems with the SCHEDULE file. This problem has been fixed.

Previously, if a DMSII user program was waiting on the following database condition:

ACCEPT:(TEST)DB: CORRECT VERSION = INVALID "AX RETRY OR OVERRID".

Then any attempt to use an OPAL script that used the VDBS context or the DBS and VDBS function against this database would cause SUPERVISOR's GRINDER process to hang, after linking to the database DMSUPPORT library, until the waiting condition was resolved. If the waiting entry persisted, SUPERVISOR would attempt to DS and restart what he believed to be a hung GRINDER.

However, in these circumstances, the GRINDER process is non-DSable while it is waiting in a DMSII procure lock routine. Since the GRINDER process is responsible for many activities such as starting jobs and the KEYIN and COMS functions, this problem can have a detrimental effect on SUPERVISOR running. Note that this non-DS behaviour is a feature since the same will occur running Unisys utilities such as DMUTILITY and DMMONITOR.

To limit the effect of the this, the handling of VDBS and DBS requests have been off-loaded to a new SUPERVISOR process called DBSHANDLER. This also relieves the load on the GRINDER process.

If an OPAL DBS or VDBS request is hung for 2 minutes, SUPERVISOR will detect this and cycle warning messages:

DBSHANDLER TASK HUNG DURING DBS REQUEST FOR DATABASE nnnnn

If DBSHANDLER is hung for more than 4 minutes, an additional message is displayed:

CHECK FOR ANY WAITING TASKS USING DATABASE (SEE 'TT LU nnnnn')

SUPERVISOR will not attempt to DS the DBSHANDLER task in these circumstances so the condition must be manually resolved. Any attempts to QUIT and restart SUPERVISOR in this state will cause the QUIT sequence to hang until the DBSHANDLER process has been reactivated.

SUPERVISOR will now only copy SUMLOGS that were created for the host system (i.e. by system serial number) after a TT TL has been issued. Previously, SUPERVISOR would have copied and processed any SUMLOG found on the DL LOG family.

Occasionally, the SUPERVISOR PRINT process could have faulted with an I/O ERROR: END OF PAGE fault when printing certain lines of text with non-printable graphic characters e.g. printing the contents of some stream files. This problem is now fixed.

The OPAL INPUT function will now only be permitted from a Supervisor COMS window running a stand-alone DO. Previously, INPUT was generally available from another ODTSEQUENCE that may be running as a WHEN or EVAL; this would cause a potential collision if another INPUT was invoked to the same window from another ODTSEQUENCE.

Now, if a second INPUT function is request for a COMS windows that is already waiting on an INPUT call, the calling DO will be terminated:

BAD INPUT FUNCTION:ALREADY WAITING ON INPUT,NO WINDOW OR ??END ENTERED

A new error condition, called GRINDTIMEOUT, has been added to the various SURE attributes available in SUPERVISOR. This condition signifies that a SURE request has been timed-out whilst waiting for a response in the SUPERVISOR GRINDER process. A timeout condition may occur if the SURE request has faulted, the GRINDER process has been DS-ed or the has timed out due to other system conditions. Typically, GRINDTIMEOUT occurs because of a SURE database access problem or a networking issue, if the request emanates from a SURE slave system.

As before, SUPERVISOR will DS and restart the 'hung' GRINDER process. Previously, a DS-ed SURE request returned the incorrect attribute value DISALLOWED.

This error will only be seen in a SUPERVISOR environment. SUPERVISOR will now wait 120 seconds instead of 60 for a GRINDER request (e.g. SURE, COMS, KEYIN, USERFN) to complete successfully.

If a Put,Get,Store ..Etc was used in a Situ compiled using an Opal version older than 490.22 and was linked using When or Eval to an ODTS newer than 500.05 then it could fail with an invalid index.

This problem has been corrected.

Previously, the GRINDER process could fault with a SEG ARRAY ERROR @ 41188400 when processing a WFL job request (e.g. AFTER or WFL function) that had failed with a SYNTAX ERROR. This problem is now resolved.

The WFL function will now recognize most WFL keywords such as WRAP, COPY, UNWRAP, RESTORE when they are seen at the beginning of the command. Previously, a 'BEGIN JOB;' heading would have been needed.

The change described in SUPERVISOR DNote 510.42 did not consistently handle JOBREJECT log entries and find their corresponding EI records when tracked by a JOBREJECT WHEN. This could occur on quiet systems with low SUMLOG activity because SUPERVISOR was not always able to retrieve the appropriate EI record from the log (it may not have been written by the MCP yet).

When a JOBREJECT WHEN is invoked, SUPERVISOR will now track EI log record activity and cache the last EI record seen. Due to the close proximity of the Job Rejected and its matching EI record, most of the time the EI record cached by SUPERVISOR will match. If no match is available, SUPERVISOR will search the SUMLOG for the appropriate EI record as before.

The JOBREJECT context will now return correct values for attributes such as NAME and USERCODE. These attributes are not normally available in a Job Rejected log record and are retrieved from the associated EI record that appears in the log prior to a Job Reject entry. Due to changes in the way that SUPERVISOR now processes all log records, the EI records were not being retrieved correctly causing NAME, USERCODE, CHARGECODE to return null values. This behaviour has been fixed.

This change implements SUPERVISOR as a system library. Currently, only one entrypoint has been implemented and is used by the SYSTEM/OPAL compiler to automatically enter compiled DEFINES from CANDE or a WFL job. This change means that SUPERVISOR will now appear in a LIBS response as well as active entries.

It is intended that SUPERVISOR will be installed as an SL-ed library allowing external access to certain restricted facilities ie. only available to privileged is system users. All other aspects of SUPERVISOR functionality is unchanged and there are no other operational effects. More information will be made available soon.

A new OPAL program type called COMMAND has been implemented for SUPERVISOR. COMMAND is a variant used in the DEFINE command and has the same syntactical implementation as that command.

A COMMAND program allows the OPAL programmer to write ODTSEQUENCES under a program name that can be executed from a SUPERVISOR window without prefixing by 'TT DO'. One advantage of this is that a COMMAND program can be used to replace an Unisys operator command. For example:

DEFINE + COMMAND C:
SHOW(KEYIN("C FULL"))

The above simple COMMAND program allows the the usual Unisys 'C' command to be superseded by the SUPERVISOR equivalent; when C is entered from a SUPERVISOR window, *all* system COMPLETED entries will be shown since a 'C FULL' is processed instead. Note that any 17 character identifier can be assigned to a COMMAND program not just Unisys commands allowing specialised sequences to be assigned a shortcut.

Mix number related commands e.g. 1234Y may also be replaced by a COMMAND equivalent. So:

DEFINE + COMMAND Y(MX):
$Y:= KEYIN(#(MIXNO,"Y"));
$Y:= &#(/,KEYIN(#(MIXNO,"TI")));
$Y:= &#(/,KEYIN(#(MIXNO,"FI")));
SHOW($Y);

With Y defined as a COMMAND program, any <mixno>Y command issued from a SUPERVISOR window would give a more detailed status response including time and file information.

Once a COMMAND program has been compiled, it will immediately be available for use from any SUPERVISOR window. COMMAND programs can also be executed by the COM command e.g.

TT COM C

Extensions to the DEFINE, ENTER and SAVE commands have been applied to accommodate the new program type. For example:

SAVE COM T= AS ZZ
ENTER COMMAND FROM ZZ

A small set of example COMMANDs will be made available for download from the Metalogic website. Enhanced commands will be C, MSG, DBS, Y and NET.

If a job was started from the WFL function and the Controlcard task faulted, the ODTS which called the WFL funtion was left in a waiting state. The most likely cause of this would if the job to be started had a $INCLUDE of a private file.

WFL will now return an error of -5 (BADWFL) in this case.

When defining Opal on screens wider than 80 characters any character on row 80 would be recognised when compiling but would not be stored. A subsequent DEF ? would not show the character in column 80. This problem is now fixed.

If Multiple new lines were specified in a show statement which started with the 'Transparent indicator' #[FF} then only the first would be displayed but all would be counted when calculating the number of lines to be displayed. This could result in the unexpected truncation of a page.

Ex. SHOW("#[FF]Line1,//,Line3");

would not give a blank line between Line1 and Line2.

This change fixes the problem and supports the new MYSELF(CODEVERSION) attribute.

If the CHARGE modifier was required for a FOR assignment with SUPERVISOR commands such as AFTER or DO, the charge code validation performed by SUPERVISOR would fail with 'INVALID CHARGECODE'.

If a scheduled AFTER fails for any reason, SUPERVISOR will now provide additional information about the activity that failed instead of only the reason. This message will be generated by the GRINDER process.

If Supervisor faulted while the NOSTATS option was set it would enter a tight loop.

The processing of Completed notices has been streamlined.

The change to the HELP ATTR command, described in DNote 510.33, caused a conflict with the VL and SYSTEM VL contexts such that it was not possible to examine attributes from the VL context. To address this, the keyword SYSVL should be used to filter attributes in the SYSTEM VL context; HELP ATTR <pattern>:VL will now operate as before.

A new subset of attributes, called METERING, has been added to the SUPERVISOR SYSTEM context. These attributes apply only to COD metering systems and are retrieved using SYSTEMSTATUS call type 31. Nearly 200 attributes have been implemented. It is likely that a similar attribute set will be implemented to support COD Log Major type 2 Minor type 29.

To facilitate searching for METERING attributes, SUPERVISOR will now accept certain SYSTEM variants as contexts when using the HELP ATTR command. The permitted variants are PD, NAP, METER and VL; these are all subsets of the SYSTEM context. Previously, it was not possible to get attribute information for these subsets.

For example:

HELP ATTR =:METER
HELP ATTR =DISK=: PD

The revised syntax of the HELP ATTR command can be seen in the HELP HELP ATTR command response.

SUPERVISOR or EVALREADER tasks will no longer give a programdump when encountering an unknown MCP message during a MESSAGE-based WHEN or EVAL. These messages are decoded by LOGANALYZER as (for example, seen on MCP 49.1 IC 149):

MSRIPC106:MESSAGE NOT FOUND -- PARAMETER(S):<1>=800, <2>=1484

The raw message is now written to SUPERVISOR's taskfile instead of taking a programdump.

Previously, SUPERVISOR would give the following MCP warning during MCS initialisation:  

"Warning 146: MCS may not be able to handle data returned in MCS" 

This warning has now been eliminated; SUPERVISOR functionality and operation is unaffected by this change though some CONTROLLER message handling has been changed to accommodate new message formats. 

If a running OPAL WHEN or DO faulted with a non-recoverable error such as certain mathematical function errors, SUPERVISOR would not be able to stop that slot from being restarted after reinitiating itself (as described in see DNotes 510.07 and 510.12). This caused a continuous cycle of faulted DO/WHEN caused by each restart. These situations are very rare; such failing in-line DO or WHENs are unaffected as they are never reinitiated during a restart.

SUPERVISOR will now attempt to detect WHENs or DOs that might generate non-recoverable program faults and ensure that the faulting DO cannot restart. An appropriate FAULT TERMINATION error message, detailing WHEN slot information, will be displayed before the faulting SUPERVISOR terminates.

This change has been applied in parallel with a fix for a serious problem where SUPERVISOR would fault with INVALID ALOG ARGUMENT when the OPAL NUMBER function was passed certain non-zero arithmetic values.

Version 510.16 introduced a bug which caused any Situ or ODTS of context User to fault. This has been corrected.

A new OPAL context called VDBS is available to SUPERVISOR users. This context allows comprehensive database information such as OVERLAYRATE, ALLOWEDCORE and CURRENTCORE (as seen in a SM STATUS RESPONSE) to be directly available as attributes. The full set of attributes are visible with the command:

TT HELP ATTR =:VDBS

The VDBS context is available in the following ways:

1. The EVAL and WHEN commands using DEFINES assigned to the VDBS context.

DEFINE + SITU VDBS(VDBS):
OVERLAYRATE GTR 20

DEFINE + ODTS VDBS(VDBS):
SHOW("MIX ",MIXNO,,"Name: ",DBNAME,/,
"ALLOWEDCORE = ",,ALLOWEDCORE,/,
"CURRENTCORE = ",,CURRENTCORE,/,
"OVERLAYRATE = ",,OVERLAYRATE 4.4 );

Using EVAL allows a 'one-off' evaluation of all active databases. Using WHEN causes a cyclical evaluation of all active databases, defaulting to 60 second cycles, but controllable using DELAY. For example:

EVAL VDBS DO VDBS
WHEN VDBS DO VDBS DELAY 5

2. VDBS and VDBSSTR may be used via the VIA function, as in the following example expressions:

VIA(VDBS(12345):OVERLAYRATE) GTR 20
VIA(VDBSSTR("34567"):CURRENTCORE)

3. As a method for real or string variables, similar to the MX method:

#MIXNO.VDBS(ALLOWEDCORE)
$MIXNO.VDBS(#(ALLOWEDCORE,,INUSECORE))

In the above example, the values held in #MIXNO and $MIXNO must be valid database mix numbers.

The VDBS context is implemented using the same interface as the Opal DBS function that the values are returned in encoded form allowing attribute mapping to occur.

If many databases are being regularly monitored, usage of the VDBS context should be used carefully as the mechanisms used by SUPERVISOR are expensive. However, VDBS does provide a very simple method to observe multiple databases over time. SUPERVISOR employs an internal caching mechanism to protect against unneeded database linkages.

The SAVE SCHEDULE AS command, when processed from an AFTER command, did not include any decompiled DEFINES in the output file. A normal SAVE SCHEDULE AS Is unaffected; this problem has now been fixed.

Under certain circumstances, it was possible for incorrect string variable labels to be displayed in an OPAL DUMP response. This problem has been fixed.

When using the Input function it was possible for the ODTS to fault if a large number of characters were transmitted. The number of characters which would cause the fault varied depending on the size of the previous string used. In fact adding the line $X:=Repeat(" ",8316) before any Input function would avoid the problem.

If such a fault occurred Supervisor would incorrectly retry the code which failed. This could lead to ODTSs being left in the when slots, marked WAITING or QUEUED. The only way to get rid of these was to quit and restart Supervisor. In the unlikely event of Supervisor faulting in an Input function then the ODTS will be terminated. (As if the user had entered ??END).

Version 510.07 introduced the ability for Supervisor to restart itself after a catastrophic failure. If Supervisor FDSed it would not be restarted. This minor omission has been corrected.

On MCP 51.1, SUPERVISOR would get an MCP SETSTATUS warning when FS-ing his own tasks that had become scheduled. This warning has been blocked.

If the KEYIN function was used with commands such as TT WHEN ?, any embedded highlighting characters in the reply would cause problems during subsequent parsing. Now, all such characters will now be replaced by a single space (" ") for all KEYIN calls.

If OPAL functions such as KEYIN, COMS, DBS or TRIM slave requests were called inside a VL EVAL or OBJECTS call, SUPERVISOR would fault with an ILLEGAL SWAP. This problem has been resolved.

Previously, if the HO command was used with a memory disk unit family, the command would fail with a BASE UNIT NOT FOUND error. This problem has been fixed.

SUPERVISOR maintains internal statistics tracking CPU usage in various areas throughout the program visible with the SHOW UTIL command. Although this information is useful, there is an overhead associated with the maintenance of the data and, on metering systems in particular, this facility may now be controlled.

A new SUPERVISOR option called NOSTATS has been implemented, its default setting is FALSE. If NOSTATS is set using SO+NOSTATS then SUPERVISOR will discard all CPU statistics information and disable usage monitoring. The option may be turned on and off at any time as deemed necessary but some of the statistical percentage values in a SHOW UTIL response (plus the value for 'Unaccounted CPU time') will be incorrect. On busy systems, turning NOSTATS on may save significant CPU seconds over a long period of time.

This patch also addresses some spurious CPU accounting that could have caused certain values in a SHOW UTIL response to be incorrect. This typically occurred when SUPERVISOR's accounting routines were used on internally run processes causing some CPU values to be skewed. This behaviour has been corrected.

The SUPERVISOR GRINDER process is meant to run under no usercode i.e '*' during normal processing. However, when using the DBS function, GRINDER switches its usercode to that of the database stack whilst linking to the DMSUPPORT library. After processing the DBS request, GRINDER was mistakenly switching back to the SUPERVISOR usercode instead of '*'; this caused other unexpected effects particularly with subsequent KEYIN usage. This problem is now fixed.

Since Version 510.01 Job stacks in a 'to be continued' state were not shown in an OBJECTS(MX=A,... COUNT(MX=A,... or an eval of a Situ of type MX=A. This problem has been corrected.

After a TT TL, all active SUPERVISOR WHENs have their current sessions 'split' causing MCS LOG-OFF session entries to be written into the SUMLOG. These entries are meant to show accumulated CPU, Elapsed and I/O times but both CPU and I/O times were always set to zero. This problem is now resolved.

Also, attempts to use EVAL.. DO on a SITUATION that was already active as a WHEN would have returned the error 'THE SITUATION IS ALREADY IN USE'. This restriction has been relaxed.

SUPERVISOR will now internally maintain SUMLOG log records in Unisys Sumlog Version 1 instead of Version 0, affecting the layout of attributes that are mapped onto the first 4 words of the record. Such attributes include the generic LOGMIXNO, LOGJOBNO, LOGMAJOR etc. This change has been applied to correct handling for individual records greater than 1023 words (maximum allowed in the Version 0 layout) particularly seen with various Log Major Type 2 Maint entries. Previously, the LOGTEXT and LOGPRINT attributes would have returned 'NO LOG TEXT: MAINT RECORD TOO LARGE' for log records greater than 1023 words; this restriction has now been removed.

Although OPAL attribute definitions have changed in the LOG context, the effect is transparent on older compiled OPAL code and scripts will continue to run without recompilation. However, since there is a small overhead associated with the support of the older formatted and a recompile of any LOG-based scripts is recommended at some stage.

The SO option LPLOCASE has now been deimplemented and the option will not appear in a TT SO command response. All printing functions will assume devices have lower case capabilities.

If the MEMORYCEILING command was entered from a Supervisor window or Supervisor RemoteSPO, it was interpreted as MEMO RYCEILING and was therefore not passed to the MCP as expected.

This behaviour has been corrected but it means a space must be used after a Supervisor MEMO command.

I.e. MEMO ? not MEMO? and MEMO NOTES not MEMONOTES

Previously, because of a missing string operation in the OPAL machine, continuous usage of the PDSURECHECKCOMPILE attribute in a WHEN or EVAL could have caused the slot to eventually fault with LOGICAL ASSERTION UNTRUE. This problem is now resolved.

The change described in DNote 510.07 did not allow SUPERVISOR to re-run itself if a restart was required because SUPERVISOR had been originally run as a dependent task (i.e. with a parent job). This problem has now been fixed.

If the Metalogic TTINTERFACE Marc Directive was installed and first used whilst SUPERVISOR was still running, it would not be possible to issue Supervisor commands from MARC stations, using the Directive, until SUPERVISOR had been restarted. This occurs because SUPERVISOR only determines the MCS number of TTINTERFACE during initialization and, because its MCS name and number are only created once TTINTERFACE has first run, it was not possible for SUPERVISOR to know if a command came from MARC. This problem is now fixed; SUPERVISOR will now automatically check the MCS number of unknown external commands to see if it might be a new TTINTERFACE installation.

Previously, very large SUMLOG records passed to a LOG-based WHEN or EVAL could have caused various SUPERVISOR faults during extraction of the log entry or generation of the LOGTEXT attribute. These faults included 'FAULT #4 IN EVREADER in SITUATION' in the EVALREADER process, seen during log analysis, or PROCESSOR LOOP and INVALID INDEX @ 97033275 generating the LOGTEXT attribute. The problems occurred because the extracted log record, in the current implementation, must be a maximum of 1023 words and truncated records were often being handled incorrectly.

These longer records are primarily Major Type 2 (MAINTENANCE) and in particular, Minor Types 17 (Hardware Config), 18 (Software Config) and 23 (Mainframe Report). Instances of Mainframe records in excess of 2000 log record blocks have been seen, causing severe problems in the log file processing. Now, when any Major Type 2 records longer than 1023 words a extracted, the SUMLOG is correctly scanned and the LOGTEXT attribute will now return the text 'NO LOG TEXT:MAINT ENTRY TOO LARGE'. This feature is a temporary detour until the log handling routines can be changed to accommodate larger long records.

Version 510.08 introduced a bug where defining a situation of type Log with no major type specified, would cause Supervisor to fault. This problem has been corrected.

Changes in MCP 5.1 caused several Prints attributes to fail. This change corrects the problem.

SUPERVISOR will now automatically restart itself after major program failures that cannot normally be recovered e.g. array RESIZE errors. Although such fatal errors are rare, SUPERVISOR will now show a waiting entry indicating that a problem has occurred. If the fault occurred during SUPERVISOR initialisation, SUPERVISOR may NOT be restarted.

Metalogic should always be advised immediately if such a problem occurs.

Previously, if a WHEN or DO issued more than 10,000 WFL function calls in the same slot, SUPERVISOR would fatally S-DS with an ARRAY TOO LARGE error. This problem has now been fixed; as a consequence of this change, only the most recent 100 WFL function calls can be tracked using user-identified WFL attributes such as WFLELAPSED, WFLJOBNO etc.

Version 510.01 introduced a problem in Wait(<name>,C) and Wait(<name,Not <state>). Using such waits could give the wrong result, and on some cases cause the Odts to fault. The problem has been corrected

On MCP 5.1, SUPERVISOR would display the following warning messages during initialization and other occasions during normal running:

WARNING 169:SETSTATUS 0 CALLS WILL BE DEIMPLEMENTED

These warnings have been eliminated.

The dump analysis generated by the SLOT command or by a failing OPAL program has been improved; more accurate time info and better fault analysis are now shown.

The PDT command help screens has been updated to provide additional information about searches using CopyWrite to inspect wrapped containers, BLPack tapes/archives and CD images. Note that SUPERVISOR will only allow any PDT process to run for 120 seconds; the process will be terminated if the elapsed time execeeds this value, so it is NOT suitable for very large archives, BLPack tapes and archives.

MCP 5.1 introduced a bug which stopped Evals of MX=DBS Situations from working. This change detours that problem.

Previously, ODTSEQUENCEs that used the WAIT statement may not have always correctly waited for the appropriate time, often suspending for a much longer time than expected e.g. WAIT(n) might randomly suspend up to 20 seconds. This problem, which would only occur when DELAY-driven WHENs were running in a higher WHEN slot than that executing the WAIT, is now fixed.

The TT PRINT TP command was not being correctly handled because of the change applied by DNote 500.55. This problem, that caused TP prints to be truncated, is now fixed.

Also, PRINT TP commands caused an additional message, 'TP COMMAND OUTPUT PRINTED' to be displayed that caused a 'TT +' to appear on the originating station. This message is now suppressed and only the 'REPORT nnnnn PRINTED' display will be shown.

The fix applied in DNote 500.55 erroneously caused non-SUPERVISOR commands passed to the OPAL KEYIN function to fail with UNRECOGNISED REQUEST. This problem has been fixed.

Command will return the error 'TK KEYIN NOT ALLOWED'.

Previously, the use of the OPAL KEYIN function with special Supervisor commands such as TK, REC and TM did not work correctly. In these cases, the calling OPAL program would be marked indefinitely as '(WAIT KEYIN)' and would require manual termination.

Now, KEYINs of the REC and TM commands work correctly but it is not currently possible to return responses to the TK command (available only to Unisys-StorageTek configurations). Any attempt to KEYIN a TK command will return the error 'TK KEYIN NOT ALLOWED'.

The TP, REC and TM commands may be used without a TT prefix in a KEYIN command.

An internal security loophole has been closed.

Previously, if the WFL function was used from an active WHEN without an ON JOBMESSAGE code block, any further events for that WHEN would be ignored leaving the Eval count for the WHEN stuck at 1. This problem is now fixed.

Further, if WFL function calls are used without any associated ON JOBMESSAGE code blocks, SUPERVISOR will now automatically deactivate the job tracking when the current ODTSEQUENCE is exited. This helps to prevent unnecessary event build-up for WFL calls that do not process job messages.

If a START command was issued using a DO modified with a FOR prefix and the command had any lower case characters e.g.

TT FOR TEST/PW DO (ODT("Start j on dev"))

The job would not inherit the TEST usercode nor, in this case, even find the file if it was held under the same usercode. This occurs because SUPERVISOR did not recognise the text 'Start' as a WFL command.

This problem is now fixed.

Any compiled OPAL programs using attributes from the special subset of WFLELAPSED, WFLEOJREASON, WFLJOBSTATUS and WFLJOBNO (only valid if a WFL function has been called with an identity) will cause the calling program to fault with INVALID CODE. This problem, caused by the changes applied from DNote 500.46, has now been resolved.

If an 'ON JOBMESSAGE' block is executed inside an ODTSEQUENCE that is linked to a WHEN, SUPERVISOR will now abort the WHEN with the error:

'ON JOBMESSAGE' NOT ALLOWED FROM ODTS LINKED TO WHEN

For WHENs, any WFL function and 'ON JOBMESSAGE' handling must be invoked by a separate standalone ODTSEQUENCE using ODT("TT DO ..."). The same restrictions are not in force with EVAL.

This change also addresses a problem where 'ON JOBMESSAGE' blocks executed from certain types of EVAL (e.g. LOG) would only work for the first entry found; all other records would be ignored leaving the EVAL inactive under certain circumstances.

Version 500.29 changed the format of TT TK messages which caused TK messages to Unisys or StorageTek silos to be ignored. This change fixes the problem.

Previously, if the DL JOBS location was changed and SUPERVISOR was then restarted prior to the halt-load, SUPERVISOR would hang on a NO FILE JOBDESC condition requiring an ILPK to the current location. This is now fixed; SUPERVISOR will always be able to determine the live DL JOBS location.

When defining a Log Situation using the Major and Minor type syntax, some minor types were not accepted. Supervisor now validates Minor types against the running MCP.

When the system time was advanced it was possible for the next action scheduled by supervisor to be delayed for up to the number of minutes the time was advanced. This behaviour has been corrected.

SUPERVISOR change 500.46 caused execution of the GETSCRATCH function to ignore the setting of the INSILO parameter. This caused GETSCRATCH requests to return tape serial numbers that were not resident in the silo. This problem is now fixed.

This internal Metalogic change improves the handling of OPAL attribute functions by the OPAL compiler and has no effect on customer usability. Attribute function information is now more detailed in a code listing and SUPERVISOR's handling has been redesigned allowing the retirement of some existing OPAL operators.

This change supports the new mix subset of FI attributes, allowing the retrieval of file information currently used by an individual task or job. The OPAL machine has been optimised to specifically handle the way these attributes are retrieved to limit CPU overhead.

The FI attribute subset can easily be viewed using the HELP command:

HELP ATTR FI=:MX

The FIFILECOUNT attribute returns the number of files in-use by the process and all other FI attributes must be indexed to get information about the selected file.

Example, to show the title and I/O transaction count for each in-use file for a selected mix entry:

  DEFINE + ODTSEQUENCE GETFI(MX):
   SHOW("MIX ",MIXNO," HAS ",#A:= FIFILECOUNT," FILES OPEN");
   #B:=-1;
   WHILE #B.SUM(1) LSS #A DO
     SHOW(FITITLE(#B) 50,"Transactions = ",FITRANSACTIONS(#B));

By default, SUPERVISOR will now unconditionally consider all systems as having the OP MORETASKS option set. This simplifies the mechanisms used to extract mix information both internally and for OPAL program usage instead of special handling when MORETASKS was set or reset.

During the compilation of ENTER files, if a '\' termination character (used to separate DEFINEs) was found anywhere other than the first character of the text then the OPAL compile of that DEFINE would fail. This problem is now fixed, the '\' termination character may be used in any character position.