Each GT.M message is identified by a name, e.g., ACTLSTEXP. Quoting from the Messages and Recovery Procedures Manual:
ACTLSTEXP, Actuallist expected
Run Time Error: This indicates that the DO command, without an actuallist of parameters, failed because its entryref argument specified a label that has a formallist of parameters.
Action: Review the interface between the DO and the subroutine. Add the actuallist to the DO, remove the formallist from the label, or identify another subroutine to invoke, as appropriate.
Messages can be compile time or run time (informational, warnings as well as errors), and indeed, since M code can be dynamically compiled and executed, all errors can occur at run time.
During the course of the development of GT.M V5.0-000, it was observed that VMS truncates these names at 15 characters, whereas UNIX does not. The majority of message names are at or below 15 characters in length, and for any new messages, we will ensure that the names are 15 characters or less. However, of the hundreds of conditions that GT.M V4.4-004 can report, six that are currently longer than 15 characters. These are:
COMMAORRPARENEXP, Comma or right parenthesis expected but not found
*
GTMSECSHRSHUTDOWN, GTMSECSHR process has received a shutdown request. Shutting down.
*
GTMSECSHRSRVFFILE, xxxx: yyyy; Attempt to service request failed. Client ID: zzzz, mesg type: aaaa, file: bbbb
*
GTMSECSHRSTARTUP, xxxx - yyyy; GTMSECSHR failed to startup
*
ISOLATIONSTSCHNG, Error changing NOISOLATION status for global xxxx within a TP transaction from aaaa to bbbb
*
NEWJNLFILECREATE, Journal file xxxx nearing maximum size. New journal file created.
*
Of these, only COMMAORRPARENEXP and ISOLATIONSTSCHNG may be encountered by an error trap in application code; the rest are reported in the operator log. Of these, only NEWJNLFILECREATE will occur during normal operation, and the rest are obscure and likely to be infrequently encountered (indeed, two, GTMSECSHRSRVFFILE and GTMSECSHRSTARTUP are likely to be encountered primarily when GT.M has not been installed correctly).
Effective GT.M V5.0-000, scheduled to be released in mid May, we propose to replace these message names as follows:
COMMAORRPARENEXP --> COMMAORRPARENEX
* GTMSECSHRSHUTDOWN --> GTMSECSHRSHUT
* GTMSECSHRSRVFFILE --> GTMSECSHRSRVFIL
* GTMSECSHRSTARTUP --> GTMSECSHRSTART
* ISOLATIONSTSCHNG --> ISOLATIONSTSCHN
* NEWJNLFILECREATE --> NEWJNLFILECREAT
*
If you feel strongly that we should not take this course of action (since it does have the potential for changing the behavior of existing code and shell/DCL scripts), please let me know ASAP. Thank you very much.
Regards
-- Bhaskar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Each GT.M message is identified by a name, e.g., ACTLSTEXP. Quoting from the Messages and Recovery Procedures Manual:
ACTLSTEXP, Actuallist expected
Run Time Error: This indicates that the DO command, without an actuallist of parameters, failed because its entryref argument specified a label that has a formallist of parameters.
Action: Review the interface between the DO and the subroutine. Add the actuallist to the DO, remove the formallist from the label, or identify another subroutine to invoke, as appropriate.
Messages can be compile time or run time (informational, warnings as well as errors), and indeed, since M code can be dynamically compiled and executed, all errors can occur at run time.
During the course of the development of GT.M V5.0-000, it was observed that VMS truncates these names at 15 characters, whereas UNIX does not. The majority of message names are at or below 15 characters in length, and for any new messages, we will ensure that the names are 15 characters or less. However, of the hundreds of conditions that GT.M V4.4-004 can report, six that are currently longer than 15 characters. These are:
COMMAORRPARENEXP, Comma or right parenthesis expected but not found
*
GTMSECSHRSHUTDOWN, GTMSECSHR process has received a shutdown request. Shutting down.
*
GTMSECSHRSRVFFILE, xxxx: yyyy; Attempt to service request failed. Client ID: zzzz, mesg type: aaaa, file: bbbb
*
GTMSECSHRSTARTUP, xxxx - yyyy; GTMSECSHR failed to startup
*
ISOLATIONSTSCHNG, Error changing NOISOLATION status for global xxxx within a TP transaction from aaaa to bbbb
*
NEWJNLFILECREATE, Journal file xxxx nearing maximum size. New journal file created.
*
Of these, only COMMAORRPARENEXP and ISOLATIONSTSCHNG may be encountered by an error trap in application code; the rest are reported in the operator log. Of these, only NEWJNLFILECREATE will occur during normal operation, and the rest are obscure and likely to be infrequently encountered (indeed, two, GTMSECSHRSRVFFILE and GTMSECSHRSTARTUP are likely to be encountered primarily when GT.M has not been installed correctly).
Effective GT.M V5.0-000, scheduled to be released in mid May, we propose to replace these message names as follows:
COMMAORRPARENEXP --> COMMAORRPARENEX
* GTMSECSHRSHUTDOWN --> GTMSECSHRSHUT
* GTMSECSHRSRVFFILE --> GTMSECSHRSRVFIL
* GTMSECSHRSTARTUP --> GTMSECSHRSTART
* ISOLATIONSTSCHNG --> ISOLATIONSTSCHN
* NEWJNLFILECREATE --> NEWJNLFILECREAT
*
If you feel strongly that we should not take this course of action (since it does have the potential for changing the behavior of existing code and shell/DCL scripts), please let me know ASAP. Thank you very much.
Regards
-- Bhaskar
Please excuse the formatting hiccups in my post.
-- Bhaskar