Text preview for : NOS_VE_Build_P_Helpful_Hints_Nov81.pdf part of
| Home
1
NOS/VE Build P helpful hints
12122/81
BUILD P HELPFUL HINTS
\
This paper describes helpful hints on hOM to use build P of
NOS/VE. It is intended to supplement, rather than to replace,
the standard NOS/VE documentation. If you have any qustions or
suggestions, please see Tom McGee or Bonnie Swierzbin. Appendix
A lists background documents and how to obtain them.
To obtain additional copies of this document white running on
SNIOI at Arden Hills, please type l
SES,OEVl.lISTPH C= To obtain a copy with revision bars against the Helpful Hints of
the previous build, please type:
SES,OEV1.lISTPH REVS C= The C parameter is optional and defaults to one.
Date Changes
12/22/80 Revisions for NOS/VE Phase C
2/12/81 Additional revisions for NOS/VE Phase C
6/9/81 Revisions for NOS/VE Build N
6/19/81 Additional revisions for NOS/VE Su tid N
8/Z8/81 Revisions for NOS/Ve Bu II d 0
1116/81 Revisions for NOS/VE Build P
Build p, November 1981
1-1
NOS/VE Build P helpful hints
12122/81
1.0 MAJOR CHARACTERISTICS OF THIS BUILD
o Atl existing commands have been updated to Revision 8 of the
ERS. In addition, parameter abbreviations have been added for
all commands. This Involved some renaming of parameters from
what was previously implemented, and In some cases, from what
was described in the ERS.
A description of the parameter names that have been changed
and the algorithm for deriving the abbreviations can be found
in the COMMAND INTERFACE STATUS section of this document.
o The 'ong aMaited message generator is available! Henceforth,
In most cases, rat~er than a condition code and raw status
record text, you will see formatted messages and their
designated severity. The exceptions will be for any remaining
HCS condition codes and, of course, conditions for which no
message templates have been defined. Feedback Mith regard to
the Intelligibility and usefulness of the messages YOU
encounter would be greatly appreciated. comments on this
subject should be given to e.G. Nelson (ARH263, X2750)
preferably in writing.
When a Job is initiated, the message mode is set to brief.
This means that the Identifier and condition code for a
message Mill not be shown; I.e. you M'.I only sees severity
designator and a formatted message; the severity designator
for informative messages Is omitted. If you really want to
see the condition code, use the SET_MESSAGE_MODE FUll
command. In full mode the severity designator for informative
messages is included.
o Interactive Usage Restrictions: When logging in to NOS/VE
(I.e. HEllO,TAF etc.) do not enter a terminate break (CTRl
t) or a pause break (CTRl p) before the 'welcome message'
appears at the terminate A pause or terminate break entered
before the Interactive NOS/VE Job has completed It's
Initialization may crash the system.
A REQUEST_TERMINAL command In a batch Job wil' crash the
system. This can happen accidently through a REQUEST_TERMINAL
command in a user prolog when the user runs a batch job since
the prolog is executed for both interactive and batch jobs.
The problem can be avoided by making the REQUEST_TERMINAL
Build p, November 1981
1-2
NOS/VE Sulld P helpful hints
12/22/81
1.0 MAJOR CHARACTERISTICS OF THIS BUILD
command in the prolog conditional on the job type as fotlows:
IF SJOB(MODE) <> 'BATCH' THEN
REQUEST_TERMINAL
IFEND
o The LOGIN and LOGOUT commands have been implemented. This
Includes the processIng of system and user proloQs and
epilogs. Since prolog processing Is now done automaticalty at
fogln, the SETUP command has been deleted. The default for
the FAMILY_NAME parameter is Inherited from the submitting job
rather than set to an operator provided default as specified
in the ERS.
The system prolog consists of processing the SSYSTEM.SYSPROF
file as was done previously by SETUP. If any errors occur
during system prolog processing, the user Job is aborted in
both Interactive and batch modes.
User prolog processing consists of attempting to attach a file
called PROLOG in the $USER catalog. If unsuccessful, an
attempt Is made to Qet the file PROLOG from the user's 170
catalog; if this is successful, the file is saved in the $USER
catalog for subsequent accesses. If the file PROLOG is now
available, it Is INCLUDEd; otherwise nothing further is done.
If any errors occur during user prolog processing, batch Jobs
are aborted and interactlye Jobs continue.
User epilog processing consists of the same steps as user
prolog processing except that the file involved is EPILOG and
If errors occur, processing continues with the system epilog.
The system epilog Is an empty procedure for the time being.
LOGIN automatlcal'y issues a LINK_USER command for the user
logging in. In addition, LINK_USER now works as documented In
the ERS, that is issuing a LINK_USER after login changes the
Job setting rather than aborting.
o TAe contents of the SSYSTEM catalog can be displayed using the
DISPLAY_CATALOG SSYSTEM command.
o Up untIl nOM If an error occurred at the "first leve'" In
batch Jobs (I.e. the command came from the file COMMAND) the
error was reported and the j6b continued processing commands.
This Is no tonger true; an error at the first level witl cause
batch jobs to be aborted.
The fife SRESPONSE is no longer connected to the file OUTPUT
Build p, November 1981
1-3
NOS/VE 8ulld P helpful hints
12/22/81
1.0 MAJOR CHARACTERISTICS OF THIS BUILD
In batch jobs. The CONNECT_FILE command may be used to make
this connection If desired.
The "Welcome to NOS/VE