---------------------------------------------------------------------------- HELMSMAN AMENDMENT NOTICES SINCE PRODUCT ISSUE This file contains a summary of all Helmsman 2.5 Amendment Notices published since Helmsman 2.5 was issued. The most recent notices are described first. Most of these notices include a software amendment. ---------------------------------------------------------------------------- Amendment number: 085/3 Date: 16 December, 1998 This is an enhancement to the Helmsman JSVM that will cause it to call the end hook whenever a job fails to queue. A job can fail to queue for the following reasons: 1) The job is already active (Result: 80807). 2) There was an overflow when performing global parameter substitution, see below for an explanation of this (Result: 80851). The end hook will be called with a "CODE_TERMINATION" value of 10 and a "FINAL_RESULT_CODE" value of either 80807 or 80851. The "RUNNO", "TAG", "VME_JOB_NAME" and "HSN" parameters will be undefined. PARAMETER SUBSTITUTION OVERFLOW: When the JSVM prepares a job for queueing, it attempts to perform any required global parameter substitution. If an expanded field exceeds its maximum allowed value then the job fails to queue and an error message is written to both the JSVM journal and the current log file. The field limits for parameter substitution are: Procedure Line 240 characters File Name in dependency 160 characters UON Name in dependency 160 characters UON Text in dependency 255 characters Text in an installation dependency 40 characters Text in an event dependency 40 characters Variable parameters 1992 characters ---------------------------------------------------------------------------- Amendment number: 088/2 Date: 3 August, 1998 This amendment corrects various problems within the Helmsman job harness that are caused by the COBOL runtime libraries and OPEH not being fully initialised after the Harness initialisation has been completed. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 089. ---------------------------------------------------------------------------- Amendment number: 120 Date: 9 June, 1998 This amendment corrects a problem with the Helmsman job harness that can cause a "Fixed Point Overflow" during a job's termination. This is due to "SEVERITY" containing a value greater than 4294967295 i.e. 2^32-1. ---------------------------------------------------------------------------- Amendment number: 119 Date: 27 May, 1998 This amendment is an enhancement to alter the default value of the "Are Parameters Reusable" field on the Helmsman Variable Parameter Setup Job Selection screen, from "Y" to "N". ---------------------------------------------------------------------------- Amendment number: 116 Date: 18 March, 1998 If a job is amended that has an "Add To Schedule" schedule change with a suite action of "O", the job amend process changes the suite action to "C". This amendment corrects this error. ---------------------------------------------------------------------------- Amendment number: 115/1 Date: 17 March, 1998 If a job is force queued using the QUE and RER tell commands or is added the schedule using the schedule change commands, then the job's last issue time is ignored by the Helmsman JSVM. This is not an error, it is how these functions were designed. This amendment alters this by forcing the JSVM to check the last issue time for all jobs that have been queued due to a schedule change. However, it does not affect any jobs that have been queued due to the Helmsman tell commands QUE and RER, the last issue times of these jobs will still be ignored. This is a replacement for version 0 in which there was an error that caused the last issue time to be ignored if the Helmsman schedule change time was not set to the default of midnight. ---------------------------------------------------------------------------- Amendment number: 108/1 Date: 17 March, 1998 This amendment corrects an intermittent problem with the Helmsman date routines that can cause a date, which has been input with a 2 character year, to be either rejected as invalid or to be treated as the wrong year. This amendment corrects an intermittent problem with the Helmsman date routines that can cause a date, which has been input with a 2 character year, to be either rejected as invalid or to be treated as the wrong year. The following date formats are no longer classed as valid within Helmsman yy/mm/dd e.g. 98/01/01 yymmdd e.g. 980101 yymmmdd e.g. 98jan01 This amendment is a replacement for version 0 which caused the following problems: * A date in the format yyyymmdd was rejected as invalid. * The HPI command UCJ_SELECT_VJ_PARAMS failed with an "invalid date" error message. ---------------------------------------------------------------------------- Amendment number: 065/3 Date: 02 March, 1998 This amendment corrects a problem with the Helmsman JSVM that can cause it to ignore any changes made to the suspension indicator within the JSVM control screen. This amendment is a replacement for version 2, in which there was a problem that caused the JSVM to ignore the "Auto Suspend on Reload" setting. ---------------------------------------------------------------------------- Amendment number: 110 Date: 19 November, 1997 RE: Ultracomp VME Products and the ICL Year 2000 Enabling Kit Ref: ICL PC-Paris SKE 93697 Describes a problem caused by the ICL Year 2000 enabling kit and proivides a solution. ---------------------------------------------------------------------------- Amendment number: 109 Date: 17 July, 1997 There is a discrepancy between the Helmsman screen interface and the Helmsman programming interface (HPI) when changing a job to a system procedure. The screen interface will automatically clear the runjob details, but with the programming interface , one has to call UCJ_CHANGE_RJ_DETAILS and set all parameters to spaces. This amendment corrects this, by forcing all runjob details to spaces following a successful invocation of UCJ_CHANGE_BASIC_DETAILS to change the current job to a system procedure. ---------------------------------------------------------------------------- Amendment number: 050/1 Date: 7 July, 1997 There is a problem with the Helmsman JSVM when running as a system task, that can cause it to loop if an error is encountered when accessing the Helmsman system files. This amendment, along with amendment 096, corrects this problem. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 096. ---------------------------------------------------------------------------- Amendment number: 098 Date: 30 January, 1997 When a job is amended within Helmsman, the job dependencies are checked to ensure that they do not loop. This check takes place even when the job dependencies have not been amended, this increases the processing time of a job amendment. This amendment removes the dependency loop check if the job dependencies screen, within Job Maintenance, has not been entered during the amend process. ---------------------------------------------------------------------------- Amendment number: 097 Date: 21 January, 1997 There is a problem with the Helmsman history extract that causes the header record to be written with the first field set to "0000", when it should contain "00000000". This amendment corrects this. ---------------------------------------------------------------------------- Amendment number: 096 Date: 21 January, 1997 When the Helmsman JSVM is running as a system task, any errors that occur when accessing the Helmsman system files do not cause the JSVM to terminate. This can cause the JSVM to carry on processing using potentially corrupt information. This amendment corrects this by calling END_VM from within the JSVM after any processing errors that are considered to have potentially fatal consequences. This amendment is a complete replacement for Helmsman 2.50 amendment 047. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 050. ---------------------------------------------------------------------------- Amendment number: 056/1 Date: 5 December 1996 This amendment is an enhancement to alter the default value of the "Clear Parameter Buffer Area" field on the Helmsman Variable Parameter Setup Job Selection screen, from "Y" to "N". ---------------------------------------------------------------------------- Amendment number: 095 Date: 16 October, 1996 If UCJ_SELECT_NEXT_JOB is called following a failed call to UCJ_SELECT_JOB, then the first job in the job details file is returned. This is incorrect, as it should return the next job which has a higher job-id than the job specified in the failed UCJ_SELECT_JOB call. ---------------------------------------------------------------------------- Amendment number: 094 Date: 14 October, 1996 In Helmsman version 2.0 access to Helmsman events was controlled by VME user names, but this was replaced in version 2.5, which now controls access via the system_id and event_number range specified in the Helmsman User Class. This amendment, and accompanying SCL procedure, reintroduces the original VME User Name check, which will now be performed along with the system_id and event_number range checks. ---------------------------------------------------------------------------- Amendment number: 015/5 Date: 29 November, 1996 This amendment corrects the following problems with the Helmsman JSVM: 1. Jobs queued within VME being marked as "ISSUED NOW LOST" 2. Jobs caught in a system break, not being cancelled when VME and the JSVM is reloaded. 3. Jobs which terminate abruptly without going through the Helmsman termination code not being cancelled by Helmsman for over an hour. Accompanying this amendment is an SCL procedure, which must be placed in the Helmsman package loadset ICLRSISOURCE library, and compiled into the Helmsman package loadset ICLRSIOMF library. ---------------------------------------------------------------------------- Amendment number: 093 Date: 9 July, 1996 If an action of "V" is specified when setting up a job's variable parameters individually, then the global parameter validation procedure is not called. ---------------------------------------------------------------------------- Amendment number: 092 Date: 8 July, 1996 A Tell CQT command allows the current schedule date/time to be specified, which can cause the job to be ignored by the JSVM. This amendment ensures that the date/time specified for a Tell CQT is at least 2 minutes later than the current schedule date and time. ---------------------------------------------------------------------------- Amendment number: 048/1 Date: 30 July, 1996 This amendment causes jobs that are running under Helmsman control to release all assigned Helmsman files after the Helmsman initialisation has completed. This will enable old generations of the Helmsman files, following a reorganise, to be deleted. Without this amendment, jobs will hold on to the Helmsman files thereby inhibiting their deletion. This version replaces version 0, in which there was an error that could cause the Helmsman JSVM to abort with a UCG dump when calling CTM_TAG_LOCATION. ---------------------------------------------------------------------------- Amendment number: 007/2 Date: 4 July, 1996 During the upgrade from Helmsman release 2.0 to Helmsman release 2.5, the first parameter of the event handling procedures: UCJ_READ_EVENT UCJ_UPDATE_EVENT UCJ_WRITE_EVENT changed from type "SPDI" to type "STRING", this was to allow a Helmsman event number to be prefixed with a system id. The above procedures function correctly with both old and new parameter types as long as they are called from a compiled module, but will fail if they are called with the old parameter type from within a SCL WHENEVER statement or from the procedure line of a job within Helmsman. The amendment produces a new module which contains the above procedures which have the release 2.0 template and renames the existing procedures to: UCJ_READ_EVENT_ID UCJ_UPDATE_EVENT_ID UCJ_WRITE_EVENT_ID The amendment also removes the write-back status of the 'DATE' parameter for UCJ_WRITE_EVENT, UCJ_WRITE_EVENT_ID, UCJ_UPDATE_EVENT and UCJ_UPDATE_EVENT_ID. ---------------------------------------------------------------------------- Amendment number: 091 Date: 2 May, 1996 When the Helmsman JSVM is reloaded following a change to the machine date and time, it reacts as though there has been a system reload. This is due to the VME meters that contain the system load time changing whenever the machine date/time is changed. This amendment stops the JSVM from treating the change in system time as a machine reload. ---------------------------------------------------------------------------- Amendment number: 090 Date: 30 April, 1996 When an action of "J" is entered within Helmsman Active Jobs Control, an internal rebuild of the active jobs index is performed after quiting from BrowseFile. This rebuild is unnecessary and is removed by this amendment. ---------------------------------------------------------------------------- Amendment number: 089 Date: 10 April, 1996 This amendment corrects various problems within the Helmsman job harness that are caused by the COBOL runtime libraries and OPEH not being fully initialised after the Harness initialisation has been completed. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 088/1. ---------------------------------------------------------------------------- Amendment number: 087 Date: 15 March, 1996 This amendment notice has been issued in order to clarify Helmsman's use of variable parameters when a mixed parameter job is rerun using Tell job,RER. ---------------------------------------------------------------------------- Amendment number: 026/3 Date: 26 February, 1996 This amendment replaces existing messages and introduces new messages within the Helmsman Message Text modules. ---------------------------------------------------------------------------- Amendment number: 072 Date: 26 February, 1996 There is a problem with System Id maintenance that allows a system id to be deleted when it is in use by an event. This can cause corruptions in the Helmsman Event records. This amendment corrects this problem by checking for the existance of an event record using the system id that is to be deleted. If an event exists then a result code of 80159 is returned. In order to convert this new result code to a text string Helmsman amendment 026, version 3 or later, is required. ---------------------------------------------------------------------------- Amendment number: 086 Date: 7 February, 1996 This amendment forces the Helmsman job harness to perform a CTM_SCHEDULE in the termination code, prior to assigning and locking the Helmsman system files. This will attempt to satisfy all outstanding requests before allocating locks on the Helmsman files. ---------------------------------------------------------------------------- Amendment number: 084 Date: 24 January, 1996 This amendment corrects a problem with the UCJ_IMPORT_JOBS function that can cause an excessive amount of loads to be performed on the job name suffix procedure. ---------------------------------------------------------------------------- Amendment number: 083 Date: 23 January, 1996 When the Helmsman import procedures, UCJIMPORTJOBS and UCJIMPORTSYSTEM, are used against an export file that is held on tape, the following message is written to the journal: ERROR 60690 ON REAL FILE filename RESULT CODE -34483 RETURNED BY MAMPHY This message, which is output by the serial file RAM when a skip to end of file is performed on a tape serial file, can be ignored. ---------------------------------------------------------------------------- Amendment number: 069/1 Date: 8 January, 1996 This amendment corrects the following problems in the Helmsman JSVM: 1. If a system break occurs whilst the JSVM is queueing a set of suite jobs, then when the JSVM is restarted any suite jobs, which hadn't been queued prior to the break, are ignored. 2. If a suite header job is force queued prior to it's normal run time, but the associated suite jobs are not requested, then when the suite's normal run time is reached all the underlying suite jobs are ignored. This amendment replaces version 0 in which there was an error. ---------------------------------------------------------------------------- Amendment number: 080 Date: 20 December, 1995 This amendment causes a warning message to be displayed by the Helmsman job harness if the product checksum is going to expire within the next 30 days. ---------------------------------------------------------------------------- Amendment number: 079 Date: 20 December, 1995 This amendment causes a warning message to be displayed by the Helmsman JSVM if the product checksum is going to expire within the next 30 days. ---------------------------------------------------------------------------- Amendment number: 078 Date: 20 December, 1995 This amendment causes a warning message to be displayed by the Helmsman MAC interface if the product checksum is going to expire within the next 30 days ---------------------------------------------------------------------------- Amendment number: 066 Date: 18 October, 1995 When Helmsman is used in a VME/X environment, the file name validation that is performed for a job's file dependencies is not appropriate. This amendment corrects this by removing the file name validation that is performed when inserting/amending file dependencies for a job. This amendment is optional, but if it is applied then Helmsman 2.5 amendment 063 must also be applied. ---------------------------------------------------------------------------- Amendment number: 063 Date: 17 October, 1995 When Helmsman is used in a VME/X environment, the file name validation that is performed for a job's file dependencies is not appropriate. This amendment corrects this by removing the file name validation that is performed when inserting/amending file dependencies for a job. This amendment is optional, but if it is applied then Helmsman 2.5 amendment 066 must also be applied. ---------------------------------------------------------------------------- Amendment number: 077 Date: 11 December, 1995 This amendment corrects a problem with the Helmsman job harness that can cause a recursive invocation of the WHENEVER RESULT found in the ICL8_UCJ_0_RUN_JOB procedure. ---------------------------------------------------------------------------- Amendment number: 076 Date: 8 December, 1995 This amendment gives the JSVM timer hook the capability to suspend the JSVM. This is achieved by the timer hook setting the returned result code to 80824 In order for this amendment to function correctly, Helmsman amendment number 065 must also be applied. ---------------------------------------------------------------------------- Amendment number: 075 Date: 6 December, 1995 This amendment corrects a problem with the Helmsman history update process that can cause a run record to be generated for a job, with no associated "Whole Job" statistics record. This only occurs if the running job is caught in a system break or is abandoned by an operator. ---------------------------------------------------------------------------- Amendment number: 074 Date: 1 December, 1995 There is a problem with the "N"ext and "P"revious actions in Helmsman Variable Parameter setup that causes the current parameter value to be discarded. This is contrary to the description of these commands documented in the Helmsman User Guide. This amendment corrects this problem. *---------------------------------------------------------------------------- Amendment number: 073 Date: 30 November, 1995 This amendment enables variable parameters to be inserted/amended for a date on which a job is not scheduled to run. A warning message is displayed and the user is asked to confirm the action prior to the insert/amend continuing ---------------------------------------------------------------------------- Amendment number: 071 Date: 21 November, 1995 There is a problem with the Helmsman history update process that causes redundant job step records to be retained in the history file. This occurs if job setps are removed from jobs that already have history data. The problem has a side-effect that causes incorrect data to be returned by history viewing/reporting and history extract. This amendment corrects this problem. ---------------------------------------------------------------------------- Amendment number: 070 Date: 10 November, 1995 This amendment introduces a new facility which enables the result codes returned at the end of a running job to be amended prior to the job being marked as finished by the Helmsman termination code. In order for this amendment to function correctly, a new SCL procedure is required. The source for this procedure, which can be found in this amendment notice, must be placed in the Helmsman ICL_RSI_SOURCE library and then compiled into the Helmsman ICL_RSI_OMF library. The SCL procedure will be called at the end of every running job which has a termination code of either: 1 Job completed OK 2 Job finished with a positive result code 12 Job finished with a negative result code If the procedure alters the result code, then the job's termination code will be altered accordingly. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 026/2 OR LATER. ---------------------------------------------------------------------------- Amendment number: 061/1 Date: 31 October, 1995 This amendment corrects a problem in Helmsman active job control that can cause an OPEH dump in area E$BUILD$xxx, where xxx can be any of QUE, PRO, CON, FIN, RUN, DEP or NOT. The problem occurs when an active/completed job is currently showing and one of the following is performed: 1) A tell command is issued and then rejected by the caller. 2) A tell command is issued for a job that the caller does not have access to. 3) A tell command is issued for a job that is not in the required state. In order for this amendment to function correctly, amendment UCJP250_034 must also be applied. ---------------------------------------------------------------------------- Amendment number: 068 Date: 24 October, 1995 There is a problem with the Helmsman HPI tell procedure, UCJ_TELL, that causes extraneous internal builds of the active jobs index (index 9). This results in a poor response time when calling UCJ_TELL, particular if called from within a TP AVM. This amendment corrects this problem by removing these unnecessary internal builds of index 9, when using the UCJ_TELL HPI procedure. These builds will still be performed if the Tell command is called via the screen interfaces. The Active Job Control Tell command from within the screen interfaces is not affected by this amendment. ---------------------------------------------------------------------------- Amendment number: 067 Date: 23 October, 1995 There is a problem with the HPI procedure UCJ_HISTORY_EXTRACT that occurs if the F_DATE parameter is set to the date of the last history update run and the F_TIME parameter is defaulted. The problem causes the procedure to fail with a result code of 80667. This amendment corrects this problem by setting the default for F_TIME to the time of the last history update run, as stated in the Helmsman SCL Reference manual. ---------------------------------------------------------------------------- Amendment number: 064 Date: 17 October, 1995 If the Helmsman JSVM performs a file dependency check on a file that is in the process of being deleted, then the job will be marked as cancelled with an invalid dependency and a result code of 38893 will be reported. This amendment corrects this problem. ---------------------------------------------------------------------------- Amendment number: 062 Date: 21 September, 1995 If the current Helmsman user class does not permit permanent jobs to be amended but does permit amendment for stored jobs, then it is possible to amend a permanent job to a stored job using Helmsman job maintenance. This amendment corrects this problem. ---------------------------------------------------------------------------- Amendment number: 060 Date: 23 August, 1995 The main store occupancy, of jobs running under Helmsman control, reported by Helmsman is incorrect. The value reported within Active Job Control, History Viewing and History Reporting has been calculated using the elapsed time of the job instead of the OCP existence time. This patch corrects this problem. The text describing OCCI on page 4-6 of the Helmsman SCL Reference Manual (Ed 1.2) should also be amended as follows: OCCI Mainstore occupancy integral. To obtain the average mainstore occupancy, divide this value by OCCE. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 059. ---------------------------------------------------------------------------- Amendment number: 059 Date: 22 August, 1995 The main store occupancy, of jobs running under Helmsman control, reported by Helmsman is incorrect. The value reported within Active Job Control, History Viewing and History Reporting has been calculated using the elapsed time of the job instead of the OCP existence time. This patch corrects this problem. The text describing OCCI on page 4-6 of the Helmsman SCL Reference Manual (Ed 1.2) should also be amended as follows: OCCI Mainstore occupancy integral. To obtain the average mainstore occupancy, divide this value by OCCE. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 060. ---------------------------------------------------------------------------- Amendment number: 058 Date: 16 August, 1995 This amendment corrects the following two errors that occur when building the Helmsman schedule jobs index, index number 5: 1. Jobs which are part of a suite and have been force queued fail to appear. 2. Mixed parameter jobs occasionally marked as Variable. ---------------------------------------------------------------------------- Amendment number: 057 Date: 8 August, 1995 If a job running under the control of Helmsman fails with a positive result code and there is a Helmsman supplied value in the jobs' Last Message field, e.g. "JOB USING HELMSMAN PRIORITY 1", then the failure message associated with the terminating result code is not written to this field. This amendment corrects this error. ---------------------------------------------------------------------------- Amendment number: 055 Date: 7 August, 1995 There is a problem in Helmsman date validation that causes a date with an obviously invalid year, such as 01APR9595, to be accepted as valid. This amendment corrects this by only allowing dates in the range 01JAN1900 to 31DEC2099. Any dates outside this range are treated as invalid. ---------------------------------------------------------------------------- Amendment number: 054 Date: 7 August, 1995 This amendment enhances the defaults action within Variable Parameter setup to ask the user whether parameters that do not have a specific default are to be space filled or retain their existing values. ---------------------------------------------------------------------------- Amendment number: 053 Date: 1 August, 1995 This amendment is an enhancement to the way the Helmsman JSVM handles the required finish time (RFT) of a job. With this amendment, a job's RFT is always calculated regardless of the circumstances under which the job was queued. This enables the late hook to be actioned for jobs which have been force queued using a Tell QUE, RER or ATS command. Without this amendment, only jobs which are queued due to their first start time being reached will be included in the late jobs check. ---------------------------------------------------------------------------- Amendment number: 052 Date: 18 July, 1995 This amendment corrects a problem within Helmsman that occurs when the Helmsman code is run at a less privileged ACR level than which it has been loaded. This causes the following error messages to be displayed in the job's journal, followed by a UCG dump: FAILED OPENING FILE :HELMSMAN.UCJFILENAMES FOR FILE NAMES ****ERROR 10002 INVALID REFERENCE (PARAMETER VALIDATION) ---------------------------------------------------------------------------- Amendment number: 051 Date: 12 July, 1995 This amendment corrects an error in the Helmsman JSVM, that can cause jobs scheduled for midnight to be delayed until the following JSVM wake up time. This only occurs if the schedule change time is not midnight. ---------------------------------------------------------------------------- Amendment number: 049 Date: 5 July, 1995 This amendment notice introduces a new HPI command UCJ_SET_JSVM_CLOSE_DOWN. This can be used to set the next JSVM close down date and time from a MAC or BATCH job that is currently signed on to the Helmsman Programming Interface. ---------------------------------------------------------------------------- Amendment number: 046 Date: 20 April, 1995 This amendment increases the maximum allowed estimated run time for a job, from 23 hours 59 minutes to 71 hours 59 minutes. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 045. ---------------------------------------------------------------------------- Amendment number: 045 Date: 20 April, 1995 This amendment increases the maximum allowed estimated run time for a job, from 23 hours 59 minutes to 71 hours 59 minutes. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 046. ---------------------------------------------------------------------------- Amendment number: 040 Date: 24 February, 1995 This amendment corrects a problem with printing the schedule jobs index from either the MAC interface or via the HPI command UCJ_SCHEDULE_REPORT. The problem causes mixed parameter jobs, that are to use their default parameter values, to be reported as not being set-up. ---------------------------------------------------------------------------- Amendment number: 039 Date: 15 February, 1995 This amendment corrects a problem with the Helmsman log file viewing and audit file viewing that causes the current session to fail to recognise when a new log file or audit file is created. ---------------------------------------------------------------------------- Amendment number: 038/2 Date: 10 August, 1995 This amendment enables the late hook "UCJ_SIGNAL_JOB_LATE" to ascertain why it has been called. The reason for the late hook being called is provided in a job space variable: ICL8_UCJ_LATE_REASON. The amendment also makes the additional late hook check, that was introduced in Helmsman 2.50, optional. ---------------------------------------------------------------------------- Amendment number: 037 Date: 10 February, 1995 This amendment corrects a problem that can cause a wrong id to be given to a job if a target job id is specified when calling the HPI procedure UCJ_INSERT_JOB. ---------------------------------------------------------------------------- Amendment number: 013/1 Date: 2 February, 1995 The Helmsman job details file (UCJ_JOB_DETAILS_FILE) has an internal limit of 16000 2K blocks, which therefore limits the number of jobs that can be defined in Helmsman. This limit varies between 5000 and 15000 jobs depending on whether jobs have variable parameter keywords and/or dependencies. This amendment increases the block allocation limit to 64000 2K blocks, which in turn increases the job limit to between 20000 and 60000 jobs. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 014. ---------------------------------------------------------------------------- Amendment number: 036 Date: 24 January, 1995 The following problems have been identified with Helmsman history file viewing when producing a concurrency report: a) The report produces a listing in three different sort sequences, but there is no heading on the report identifying what sort sequences have been used. b) The report produced is not restricted by the current user class. This amendment corrects both these problems. ---------------------------------------------------------------------------- Amendment number: 035 Date: 19 January, 1995 This amendment allows a sort sequence to be specified when printing the scheduled jobs index, index number 5, from the Helmsman MAC interface, or via the HPI command UCJ_PRINT_INDEX. The sort sequences allowed are: TIME Lists records in queue time order USER Lists records in VME username order ID Lists records in job id order spaces Produces a listing for each of the above ---------------------------------------------------------------------------- Amendment number: 034 Date: 18 January, 1995 This amendment corrects a problem in Helmsman active job control that can cause the wrong screen to be shown following a Helmsman Tell command. ---------------------------------------------------------------------------- Amendment number: 033 Date: 17 January, 1995 This amendment corrects a problem in Helmsman Schedule Dates Maintenance that causes the cursor to be misplaced if an invalid category name is supplied. ---------------------------------------------------------------------------- Amendment notice: 032 Date: 16 January, 1995 This amendment corrects a problem in the Helmsman JSVM that causes a mixed parameter job, that uses global substitution parameters within its default values, to be cancelled with the message: OVERFLOW DURING V.P. GLOBAL SUBSTITUTION ---------------------------------------------------------------------------- Amendment number: 031 Date: 5 January, 1995 Helmsman users which have a user class that inhibits use of a system id of spaces are not able to access Helmsman events that are not associated with a system id, i.e. all events that have been created in Helmsman release 2.0. This amendment allows all Helmsman users to show/print/amend all Helmsman events that do not have an associated system id, but only users that are allowed access to a system id of spaces will be able to insert new events that do not have an associated system id. ---------------------------------------------------------------------------- Amendment number: 030 Date: 5 December, 1994 This amendment corrects a problem in the Helmsman JSVM that can cause jobs jobs to be marked as "ISSUED NOW LOST" along with a message in the Helmsman log file containing the result code -34885 (ACC_NO_ACCOUNT_WARNING). ---------------------------------------------------------------------------- Amendment number: 029 Date: 2 December, 1994 This amendment corrects a problem in Helmsman that can cause a job, which is running under Helmsmans control, to report one of the following errors in jobs journal: 1) UCUOPENLOG: FAILED TO EXTEND INTERNAL BUFFER AREAS UCUOPENLOG: RESULT CODE 33735 ****ERROR 33735 INVALID OR INACCESSIBLE SEGMENT NUMBER SPECIFIED 2) UCUOPENLOG: FAILED TO EXTRACT GENERATION NUMBER OF LOG FILE UCUOPENLOG: RESULT CODE 39458 ****ERROR 39458 ATTEMPT TO TRANSLATE A CURRENCY HAS FAILED 3) FAILED OPENING FILE "helmsman file name" ****ERROR 31863 INVALID CURRENCY These errors can occur if a job switches ACR levels inbetween calling Helmsman commands. ---------------------------------------------------------------------------- Amendment number: 028 Date: 21 November, 1994 This amendment corrects a problem that can cause a mixed parameter job that has been added to the schedule to be treated, by the JSVM, as a rerun. This causes the job to wait for variable parameters to be supplied. ---------------------------------------------------------------------------- Amendment number: 027 Date: 21 November, 1994 This amendment corrects a problem in Helmsman, when viewing the current user class, that causes the event id range and job id range values to be mixed up. ---------------------------------------------------------------------------- Amendment number: 014 Date: 21 September, 1994 The Helmsman job details file (UCJ_JOB_DETAILS_FILE) has an internal limit of 16000 2K blocks, which therefore limits the number of jobs that can be defined in Helmsman. This limit varies between 5000 and 15000 jobs depending on whether jobs have variable parameter keywords and/or dependencies. This amendment increases the block allocation limit to 64000 2K blocks, which in turn increases the job limit to between 20000 and 60000 jobs. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 013/1. ---------------------------------------------------------------------------- Amendment number: 010 Date: 25 August, 1994 This amendment stops the history update process from logging a message in the Helmsman audit file whenever it alters a jobs estimated run time. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 009. ---------------------------------------------------------------------------- Amendment number: 009/1 Date: 25 August, 1994 This amendment stops the history update process from logging a message in the Helmsman audit file whenever it alters a jobs estimated run time. THIS AMENDMENT MUST BE APPLIED WITH HELMSMAN 2.5 AMENDMENT 010. ----------------------------------------------------------------------------