Software_Rel_Bulletin_NOS_VE_Cycle_17_Feb84 Software Rel Bulletin NOS VE Cycle 17 Feb84

Software_Rel_Bulletin_NOS_VE_Cycle_17_Feb84 Software_Rel_Bulletin_NOS_VE_Cycle_17_Feb84

User Manual: Software_Rel_Bulletin_NOS_VE_Cycle_17_Feb84

Open the PDF directly: View PDF .
Page Count: 55

Download
Open PDF In Browser	View PDF

1
84/02/10

SOFTWARE RELEASE BULLETIN
NOSIVE (CYCLE 17)

DISCLAIMER:

NOS/VE Is intended for use as described In this
document. CONTROL DATA CORPORATION cannot be responsible
for the correct operation of features or parameters not
described.

LAST UPDATED fEBRUARY q, lQS4

- COMPANY PRIVATE -

- COMPANY PRIVATE -

2

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)

l ...Q_ltilaOQut.IlllH
1)

The NDS/VE Cycle 11 system consists of the
operating system and product set features outtined
in the NOS/VE 1.0 Software Availability Bulletin (SlB).
The NDS/VE Cycle 17 system must be Installed using
the release materials. (Se~ the NOS/WE 1.0 SAB, pages 11
and 12, for the list of the release materia's.)
NOS V2.2 Level 5q6 Operating System and lovel 587
for the Common Products must be Installed on the
computer hefore tostl"ing NOS/VE Cycle 17 to complete
the dual state system confIguration.

2)

It is necessary to understand this document, the NOS/Ve
1.0 SAR, the NOS/VE Installation and Upgrade Manual
(60463913), and the NOS 2.2 Level 596 Operating System
and Level 587 for the Common Products and related
documents before installing NOS/VE Cycle 17.

3)

After installing NOS V2.2 Level 596 Operating System
and Level 581 for the Common Products system and the
NDS/YE Cycle 17 system, the NOS and NOS/VE
systems may be deadstarted and placed into operation.

4)

PSR numbers are Included wIth some of the Items In this
document. These PSRs are outstanding as of the date of
the reJ ease.

- COMPANY PRIVATE -

3

SOFTWARE RELEASE BULLETIN
84/02/10

NOS/VE (CYCLE 17)

Z... tl_ffAIU&fs'_Ati.tl_fROllUC.IS

A complete description of OperatIng System and Product Set
features may be found in the NOS/VE 1.0 Software
Availability Bul1etln. Please refer to that document for
NOS/VE Cycle 11 system feature information.
All references in the NOS/VE 1.0 SAB to the CYSER 170-835
and CVaER 170-855 shou1d be updated to Include the CY8ER
170-815, CYBER 170-825, and CYBER 170-845. All references
In the NOS/VE 1.0 SAB to NOS 2.1 level 588 should be
modified to NOS 2.2 Operating System leve' 596 and Common
Product level 587.

- CDMPANY PRIVATE -

4

SOFTWARE RELEASE BULLETIN
84/02/10

NOS/VE (CYCLE 17)

1)

PASSON and IRHF both run out 01 the SYSTE"X account. 8ecause
af this, the password must be set to SYSTEMX and the resource
validations must be set to their maximum.
PSR 1#

2)

NVO~)OOZ

The tUN=. parameter on the *SETVe* command must have Its
resource validations set to the maximum. failure to do
this can cause the deadstart Job to fail with 'PRU LIMIT'
or 'SRU LIMIT'.
PSRt NV00002

1)

There is a timing problem/data sensitive bug that may
occassionally cause the RESTORE_PERMANENT_FILE command to
abort. If this ocours, the operator should restart RESTORE
with the failing reel. If the problem does not re-occur,
onl, one file Is lost. If the problem still occurs, restart
RESTORE again but with the reel that follows the falling
reel. In the second case, all fltes on the tape following
the point where the failure occurred are tost.

2)

Automated vatldat10n performed during an Installation
Deadstart creates a SFAMILY_USERS file for the NVE 'amlly.
If you subsequently reload permanent files to family NVE from 8
BACPF ftle, catalogs which were not defined In the automated
validation cannot be accessed. likewise, any catalog Information
whIch has not been updated In the automated validation file Is
incorrect for the catalogs restored using BACPF. The recommended
sequence of events In which an Installation Deadstart can be
performed, and the family NVE permanent files restored from a
prevIous .evel Is as follows:
1. BACPF all NVE catalogs and files (except
uuu.$fAMIlY_USERS) to tape (uuu is the FAMILY_USER
Adm i n Is tr ator).
Z. BACPf the flte uuu.SFAMIlY_USERS.
This Is done by bracketing the commands associated with
the backup with TASK, TASKEND commands. The ring number
Is established by using the RING parameter of the TASK
command. For example:
TASK RING=3
COPY_fILE Input=alpha output=omega
- COMPANY PRIVATE -

5

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)

TASKENO
causes the COPY_FILE command to execute In ring 3.

NOTE:

The task command can be specified only in an
interactive Job or In 8 batch Job running under

SSYSTEM.
3. Perform an Installation Oeadstart of NOS/VE, but enter the
command nETF VAlIOATE/OFAMILY/ONVE prior to entering the
NEXTOSTAPE response to the request for the first product
tape. This command wlll disable automated validation.
4. Restore the SFAMILY_USERS file that was backed up In step 2.
(Ir you tailed to disable validatIon prior to this step, you
must 'ogln as the NVE famlfy user administrator, and change
the name of the $FAMIlY_USERS file using Change_Catalog_Entry.)
5. Restore the remainIng NVE famity files which were backed UP
in step 1.

6. Execute the Create_famIlY command from the operator console
PSR NV0001Q
3)

The procedure Verify_Instal led_Software which Is documented In
the NOS/VE Installation and Upgrade manual (Publlcation number
60463913 A) Is not available at this time.

4)

The NOS User Neme creation described in the NOS/YE Installation
and Upgrade Manual implIes that the default MDOVAl OS value is
adequate. DSa5 Is the appropriate value.

5)

Multiple NOS/VE upgrades using the CREATE_JOB_TEMPLATE command
result In a large number 01 files being created on the deadstart
disk. Each successfut execution of the CREATE_J08_TEMPLATE command
creates a directory file and severa. uniquely named segment files.
The d1rectory flte name Is specified by the TEMPLATE_NAME
parameter, and contains the name of every segment 'lie which
constitutes the Job template. Whenever a Job template is no longer
being used, the DELETE_JOB_TEMPLATE command should be used to
remove the directory file 'rom the deadstart disk. Segment 'lies
are removed by this command whenever the directory file
removed.
The console entry for this command ist

.S

K.DELETE/OJoa/QTEMPlATE TN=nsme
6)

Online manuals are released on a NOS/VE Backup_Permanent_FIJes tape
at this release. This is an interim process that Mill be
replaced by a process being generated by PublIcations and
Integration. To installed the online manuals, you must
reload the fltes on thIs tape into the SSYSTEM.MANUAlS
subcatatogs of the SSYSTEM family. Create the following
NOS/VE Job to accomplished this task:
JOB
request_magnetic_tape file=backup type=mt9$1600 rlngano evsn-nve007

- COMPANY PRIVATE -

/
6

SOFTWARE RELEASE BULLETIN
84/02/10

NOS/VE (CYCLE 17)
display_value osv$status output=$response
reQuest_operator_8ctJon message·. RESTORE fAILED - CHECK TAPEt
logout

WHENEMO
RESTORE_PERMANENT_FIlES
restore_sll_files backup_fJle=backup

QUIT

JOBEND
The above Job may be created as a NOS or NOS/VE text file. This
text file Is then accessed from the operator console, using the
ATTACH_FILE or GET_FILE command, and the INCLUDE_FILE command is
executed to submit this Job as a SSYSTEM family batch Job.
7)

Upgrade installation specifying lOADFIlES (through
SET_SYSTEM_ATTRIBUTES) but not MULTD causes the deadstart
version of OCU rather than the standard version of
OCU to be generated. The SHIGH cycle must be DElf'd
after the system Is up.

8)

The operating system requires assistance at the console for
remote install~t'on and remote maintenance. The installation
and maintenance procedures are being modified to reduce the
need for assistance at the console but until Remote Deadstart
Is available, this need wit I not be total'y eliminated.

9)

Great care should be taken using the DELETE_USER subcommand
of the ADMINISTER_USER uti' ity. If more than 20 users
are deleted since Installation of the system, there .s 8
good chance All USERS WIll BE LOST.
PSRs HYOD896, NVOE061, MYOE062

1)

NOS/VE will not support ~ore than 10 tasks
concurrently defined per Job. The system does not
enforce this IlmJtJ users must be careful not to
exceed this limit or they may cause the system to fail.

2)

To successfully terminate a Job that has an action message
posted to assign a tape, the sequence must be as
rollows:

K.ASSIGN_OEVICE Alannnn STOP

K.TERMINATE_JOB •••
Failure to assign the devJce prior to terminating the

Job will cause the Job to hang.
PSR NVOE337
- COMPANY PRIVATE -

1

SOFTWARE RELEASE BULLETIN

84/02/10

HOS/VE (CYCLE 17)
l ... l_OIUl.c.AtQ.'-"iUllllln~.i
11

Restarting Up IRHF and IFEXC on the 180 SIde
IRHF should automatically restart It it aborts. There Is
a constant check to see if it has aborted. To bring up
IRHF manually, the operator must first bring down IRHf, then
bring It up again. The same holds true for PASSON.

To bring down IRHF,' type in 8t the 180 NOS/VE operator's
console:
K.DEACTIVATE_SYSTEM_TASKS TASK_NAMES=RHINPUl
K.DEACTIVATE_SYSTEM_TASKS TASK_NAMES-RHOUTPUT
Then to bring IRHF back up, type In at the 180 NOS/Ve
operator's console:
K.ACTIVATE_SYSTEM_TASKS TASK_NAMES-RHINPUT
K.ACTIVATE_SYSTEM_TASKS TASK_NAMES=RHDUTPUT

To bring down IFEXC, type in at the 180 NDS/VE operator's
console:

Then to bring IFEXC back up, type in at the 180 NOS/VE
operator's console:

K.ACTIVATE_SYSTEM_TASKS TASK_NAME-IFEXEC
PSR NVl0032

2)

Restarting IRHF and PASSON on the 170 Side

To make provisions for restarting IRHF and PASSON, a site
analyst or an operator should create tHO procedures and save
each one on an Indirect permanent fl'e that Is located ~nder
user Index 3777718.
Procedure 1.

The 'Ile name should be MSSIRHF and should look

like this:

• PROt, MSS IRHf.

COMMON,SYSTEM.
GTR,SYSTEM,NVElIB,U.UlIB/NVELIB
UNLOAD, SYSTEM·.

lI8RARY,NVElIB.
RUNJOBS(IRHFl
Procedure 2.

The file name should be MSSPASS and should took

I I k eth Is:

- COMPANY PRIVATE -

8

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)
.PROC,MSSPASS.

CDMMON,SYSTEM.
GTR,SYSTEM,NVElI8,U.ULIB/NVElIB
t I BRAR y, NVElIB.
RUNJOBS(PASSON)

Once these are In user index 317777B, IRHF Is restarted by
simply typing the following In at the 170 operator's console.

MSSIRHF.
PASSON Is restarted by typing in at the 170 operetor 1 s console:
MSSPASS.

PSR NV00016.
3)

The NOS application (VEIAF) that connects NOS/VE
Jobs to HAM will sometimes produce the flashing
console message:

"PASSnN ABNORMAL 18"
This message means PASSON Is discarding an unsolicited
message generated between VEIAF and the first read
request from NOS/VE.
This should be Ignored.

Clear the message with 'GO,Jsn. f

1)

The INITIALIZE_DEADSTART_DEVICE system-core command
and the IHITIAlIZE_MS_VOlUME logical Configuration
Utility subcommand do not warn the operator that the
volume has been previously initialized. This Is of
particular concern in INITIALIZE_MS_VOlUHE because the
operator may misspell the element_name of the device
and Inadvertently destroy permanent files.

2)

If the physical configuration consists of one channel,
one mass storage controller, and one mass storage
unit, one can describe this initially using
system-core commands. However, thjs configuration
needs to be redescrlbed using Physical Configuration
UtlJlty and Logical Configuration UtIlity subcommands
in order to get through an installation deadstart.

3)

For optima' system performance a'l NOS/VE disk units
should be defined during the Instal' deadstart. This
is important so that all of the logical configuration
Is available for allocating product set files.

- COMPANY PRIVATE -

9

SDFTWARE RELEASE BULLETIN

84/02/10

NDS/VE (CYCLE 17)
4)

During recovery rihen operator intervention bas been
specified, the logica' configuration utility (LeU) is
Invoked both before and after the configuration
transition. The fIrst invocation allows the operator
to change which elements In the physical configuration
are logically confi~ured. The second invocation alloMs
the operator to InItialize" and add volumes to the system set.
This Is useful if the first Invocation of the LeU happens
to add one or more volumes to the logical configuration.

5)

The ability to lnvoke the LeU during a continuation deadstart
as described In the previous bullet has been added.

6)

Thephystcal configuration utility subcommand,
INSTAll_PHYSICAL_CONFIGURATION has 8 new parameter,
PHYSICAL_CONfIGURATION. This p.rameter specifies
the name ot a loca' file that wIll receive Information
about the physical configuration being debugged. Use
of thIs parameter will cause the configuration to
NOT be Installed. The'i Ie produced by this command
can be used as Input to the INSTALL_LOGICAL_CONFIGURATION
subcommand of the logica) configuration utility.
The abbrev1atlon for PHYSICAL_CONFIGURATION Is PC.

7)

The 'oglcal configuration utility subcommand,
INSTALL_LOGICAL_CONfIGURATION has • new parameter,
PHYSICAL_CONFIGURATION. This parameter specifies
the name of a local 'tte that will provide Information
about the physical configuratIon beIng debugged. Use
of this parameter wi •• cause the configuration to
NOT be installed. The abbrevIation for

PHYSICAL_CONFIGURATION is PC.

1)

If any disk volume being used by NOS/VE becomes full,

the following message wll I perlodlca"y appear on the

MDD screen:

AAAAAA - volume out 01 space
(AAAAAA is the ysn of the volume)
Any task that is requesting space on a full volume
will h~ng waiting for space. Some space may be
obtained by asking users (If they are able) to defete
permanent 'ites and detach local files. If the disk
full condition persists, the NOS/VE system should be
taken down and brought back up. This action wilt
release most of the temporary flte space that was In
use. If the disk futl was caused by permanent files,
then the disk will be nearly fu" after the recovery,

- COMPANY PRIVATE -

SOFTWARE RELEASE BULLETIN

10
84/02/10

NOS/VE (CYCLE 11)
and some action--such as backing up permanent files
and deleting some flles--must be taken Immediately.

It is possible that a disk full situation will occur
that cannot be recovered. This will have happened if
the "volume out of space" message appears during a
deadstart before the system Is up. In this case
case permanent file volumes must be lnltlatized
and reloaded from a previous backup dump.
2)

If a continuation deadstart falls after disk tutl with
a 180 CPU monitor 'suit, it Is possible that the 'allure
Is due to unprinted fifes in the output queue, one or
more of which are no longer printable. The failure is
a Job mode software failure and does not leave the MeR
set In monitor mode. The message indicating this
failure is "HR - MONITOR FAUlTfl.

Corrective action:
On the next attempt at a continuation deadstart, enter
the folloNing command when the system asks for
operator supplied core commands:

This command wIlt allow deadstart to complete. If, at
this time, you fln1 that task RHOUTPUT has terminated
(by looking at the syste~ Job log by doing a DISSl), and
files exist in the Job output queue (DISPLAY_CATALOG
SSYSTEM_SJOB_DUTPUT_QUEUE) you can be reasonably sure
that you have encountered this problem.
Delete the contents of the Job output queue (OElETE
CATALOG_CONTENTS SSYSTEM.$JO~OUTPUT_QUEUE), terminate
NOS/VE, and do another continuation deadstart.
3)

When recovering "Ithout a memory image, the EOI for a
fite is set to the highest allocation-unit which has
bean lnitialized on the devIce. ThIs Is probably not
what the actual end-or-Information (EDt) shows In the
memory Image. The file's owner Is not informed that 8
different EOI has been chosen. This means that the user
cannot use BAM to read the fIle. The file needs to be
recreated.
PSR NVOE5Z4

1)

Tape support Is limited to and Intended for use onl, by
the permanent file backup and restore utility. Use of
tape 110 for any other purpose may produce undefined

- COMPANY PRIVATE -

SOFTWARE RELEASE BULLETIN

11

84/02/10

NOS/VE (CYCLE 17)
results.
2)

When preparing to mount a tape to be read by NDS/VE, the heads on
the drive should first be cleaned. This is recommended before
each tape mount due to the currently Incomplete Implementetlon of
error r eco ver.J.

1)

When using X25 to ~ccess NOS/VE, a terminal may
lntermlttent1y htno allowing no input or output. TIP
commands break (such 8S escape-CH) out of this problem.
This Is a CCP problem that has been PSRd and corrected
in cepe
PSR C'C5A230

- COMPANY PRIVATE -

12

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)

1)

A command that depends on the ·path name" for a ftle
is .ffacted if the fite has been explicitly attached
(attach_file, create_file commands).
The "path name" that such a command wlJI encounter Is
the "local path name" rather than the path specified
when the command was cafJ~d. For example:
ATTACH_fILE SUSER.X lF~=Y
REPLACE_FILE SUSER.X
will result In a file cal led Y being referenced In
real state rather than X. Users should not mix
Implicit and explicit attaching of a 'lIe.
PSR NV00153

2)

The $PRDGRAM function does not return the open
position designator for the LOAD_MAP file.
PSR NV00483

3)

The SET_SENSE_SWITCH (SETSS) command will not accept a
fluser supplied Job name" but will only work when given
a "system supplied Job name ft •
PSR NVOD611, PSR MVOOSeS

4)

The constants $MIN_INTEGER and SMAX_INTEGER have
values of -(2**48-1) and 2*.48-1, respectIvely,
rather than -(2**63) and 2**63-1.
PSR NVOD609

5)

A new display_option has been added to the display_catalog
and dJsplay_catalog_entry commands. for the former command
this dIsplay option is called CONTENT(S) or CJ and for
the latter command i t is called CYCLE(S) or C. Also, a
parameter called DEPTH has been added (following the output)
parameter) to both commands that works In conjunction with
the added display options. These options ShOM the aMount of
space occupied by catalogs, files, and cycles. The depth
parameter determines the leyel of detail that Is displayed.

DEPTH:l gives a 1 ,jne summary of the catalog (or tile).
DEPTH=2 (the defa'tl gives a breakdown of files and subcatalogs
contained directly In 8 catalog (or the cycles of 8 file).
A DEPT~ greater than 2 Is only applicable to catalogs and
specifies a further breakdown of the catalogs and ftles
contained withIn the subcatalogs of the catalog. To get
complete information about all subcatalogs, fates and cycles
- COMPANY PRIVATE -

13

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)
contained in 8 catalog, specify DEPTH-ALL.
did not make It Into the manuals.

These c

~&.l .... 1_Aaliit.lg,Q.al_C.Qmlt£D.di._1t!,Qt_itt_ttanulll~l

i ... l.&1 ...1_1l1SeLAl_'-OHSAtiO_fAI.!1!fIEll,S1_1JllSCfl

This command displays information about the parameters for
a
command.
The informatIon Inctudes the names of the
parameters, their types (IncludIng alloNed keYMord YBlues) and
their default vaJues (or an Indication that the parameter Is
required).

This command Is not Intended to be 8 replacement for
information in on-line manuals, but rather a "memory Jogger"
for any command. It will work for any command that could be
called at the point where thts comm~nd Is called (Including
system supplied commands, SeL procedures, user programs and
utility subcommands).
This command can be used to obtain InformatIon about the
parameters for any command that uses Set services to parse Its
par ameter s.

dlsplay_command_parameters commanda(commend)
[output=]
command : c: This parameter specifies the command for which
information about parameters is sought.
output: 0: This parameter specifies the fl'e to which the
parameter Information Is written. OmissIon will cause
SOUTPUT to be used •

. status: This Is the standard status parameter.
~£1£Z_Ad~111Qn.l_Eun~11~o~_iHg1_1Q_~aQYi!~1

i&l ...Z&l_lCa~HAUQ_SOU&CE
This function Is used to determine where the processor for
the requesting command was found.
The source (file or
cata1og) or the command is returned as 8 string.
Its nature, thls function Isn't particularly useful .hen
used in the expression for a parameter to a command, since, In
th;at case,
it
will :return the sour ceot' that command.
Therefore, this function Is normal I, used In an assignment
st atement.
By

- COMPANY PRIVATE -

nges

14

SOFTWARE RELEASE BULLETIN

64/02/10

NDS/VE (CYCLE 17)

Example: ftThe following proc resides on anfl
"object library in some catalog."
PROC sample_command
as = Scommand_source
cat = $path(Sfnamefcs), catalog)
execute_task Sfname(catll'.sample_program)
PROCEND

This funotion is used to obtain the
the pravlous command.

completion

<$previous_status> ::= SPREVIOUS_STATUS

[«) (»]

status

of

Example: collect_text display_status
PRDt display_status, dlss (
status: status = Sprevious_status)
display_value $value(status)
PROCEND display_status

**
create_variable

s kind=status
create_variable x status-s
display_status

NORMAL STATUS

create_variable x status=s
display_status
--ERROR-- X Is already declar~d as a variable.

This funotion is used to quote a string.

(Squote) ::= SQUOTE «() (string expr)

<»

Example: s = 'ABC·tDEF'
q= $quote(s)
dlsptay_values
ABC'DEF
display_value q
'ABCt'OEF'

This function is used to search a string tor anyone of 8
set of characters and return the index in the string of the
round character. If no character from the set appears In the
- COMPANY PRIVATE -

15

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)
string, zero is returned.
 <»


Example: dIgits = '0123456189'
s :'TEMP_32 t
display_value Sscan_any(dlglts,

5)

6

This function is used to search e string for any character
that is not In a set or characters and return the index In the
string of the found character. If only characters from the
set appear in the string, zero is returned.
($scao_notany) ::= SSCAN_NOTAMY «() (char set) <,:sp)
(string expr) <»
 ::= (string expr>
Exampte: digits:: '0123456789s = 'TEMP_32'
display_value $scan_ootany(diQits,
1

$)

This function is used to search a string for another
strIng, called the pattern, and return the index of the first
character of the pattern In the string. If the pattern Is the
null string, one is returned. It the pattern Is not found in
the string, zero Is returned.
($scan_strlnJ> ::= SSCAN_STRING  (pattern> <,:sp>
(string expr) <»


11=

(string expr)

Example: s = '123_abe_g.
p= 'abc'
display_value $scan_strlng(p, s1
5

- COMPANY PRIVATE -

16

SOFTWARE RELEASE BULLETIN

84/02/10

NDS/VE (CYCLE 17)

:t;a.l.a.Z...l_lI&AHSLAIE
This function Is used to change characters in a strIng
according to a translation table. The trans.atlon table Is a
string of 256 characters which is utilized according to the
following algorIthm.
result = '1
tor 1 » 1 to $strlen(string) do
J = Sord($substr(strlng, I)
result = result II Ssubstrftable, J+l)
forend
Two

standard

translation

tables

provided.
Use of
all .ower case
letters translated to their upper case counterparts. Use of
UPPER_Tn_LOWER (UTl) produces a string with all upper case
letters translated to their 'ower case counterparts.

LOWER_Tn_UPPER (LTU) produces a strIng

are

wtth

(Stranslate) ::= $TRANSLATE «()  <,:sp>
(string expr> <})

display_value '('II$trlm(s)II')'

or

I::

PUSH_COMMANDS

The purpose of this statement Is to cause the source ('lie
catalog) of the Issuing command to be pushed onto the top

- COMPANY PRIVATE -

17

SOFTWARE RELEASE BULLETIN
NOS/VE (CYCLE 17)

84/02/10

of the "dynamic command list". The entries In the dynamle
command list are searched after the commands belonging to any
active utilities and before the
command
lIst
entries
manipulated by the SET_CDM"AHD_lIST commend. The effect of
thIs statement Is removed (popped) when the Issuing command
terminates.

1)

2)

1)

The DISPLAY_CATALOG and OISPLAY_CATAlOG_ENTRY
commands, when used on a catslog or file owned by
another user, should only provide Information for
catalogs andlor ftfes that the requesting user Is
permitted to access. This restriction is not
enforced. The information erroneous'y provided,
however, does not include passwords and onl, contains
Jog entries and permit entries that appl, to the
requesting user.
NVOE251
NVQB133
Great care should be taken using the DELETE_USER subcommand
of the ADMINISTER_USER utility. If more than 20 users
are de1eted since Installation of the system, there Is a
good chance All USERS WILL SE LOST.
PSRs NVOD896, NVOE061, NVOE062

When the NOS/170 IRHf Is started via 8 DIS Job (for
debugging IRHf), It does not transmlt queue files to
NOS/VE. RUNJOBS is unable to acquire the queue file
from NDS/170.
PSR NVOE292
A method to work around the problem Is to start IRHF with
an unused "subsystem". An example would be to create the
following PROC within the SVSTEMX catalog:
.PROC,"subsystem"IRHf
COMMON, SYSTEM.
GTR,SYSTEM,NVElIS,U.UlIB/NVElIB
UNLOAD, SYSTEM.
RUNJOaS(IRHF}
REVERT.
The followIng command cou1d then be given to DSO.
"subsystem" IRHF

2)

When 8 bad LOGIN command is present In a batch Job,
the Job disappears and printout with the error is
received by the user to report the problem. This
- COMPANY PRIVATE -

18

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 11)

occurs when sending 8 Job from NOS to NOS/VE via
ROUTE,xx,DC-LP,FC-RH.
NVOE491
3)

Change Information is not transmitted 'rom NOS/VE
side to the NOS side.
PSR NV00019

4)

Changing passwords on NOS and NOS/VE.
In NOS 2.2, there are two passwords for each user.
One is the NOS Interactive Job password and the
other is the NOS batch Job password. Th~ NOS
interactive Job password Is used while working on
a terminal. It Is •• so used for NOS/VE login
processing - when logging Into NOS/VE on an
InteractIve terminal, there Is no check made' of the
NOSJVE password for validation purposes, Just the NOS
interactive Job password. Changing your NOS/VE
will affect only your NOS batch password. Your
NOS/VE password must match your NOS batch password
otherwise Remote Host wIt I not work since i t submits
batch Jobs to NOS.
Note: When using the SET_LINK_ATTRIBUTES command,
the NOS/VE password specified must match the NOS
batch Job password.
Note: The selection of passwords for NOS and NOS/VE
must conform to the definition as given In the NOS
Reference Manual for the NOS password and the NOS/VE
Command Interface Reference Manual for the NOS/VE
password. You have to take the common parts of both
definitions to make a password that Morks for both
NOS and NOS/VE.

To change your NDS/VE password, enter the SET_PASSWORD
command on the 180 side t
Setpw oldpw newpw

where oldpw is your current NOS/VE password and
newpw Is the new password.
To chanoe your NOS batch Job password, you will
have to submit 8 NOS batch Job. login to the
170 side and create a 'Ile to submit thIs job.
The ri Ie should contain the following:
JOBCARO.
USER(usernam,userpw)

CHARGE,·.

PASSWOR(userpw,newpw)

- COMPANY PRIVATE -

19

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)
END

where usernam is your username, userpw is your
current NOS batch password, and neMpw Is your
neN NOS batch password. Your original NOS batch
password Is set to your original NOS Interactive
Job passwords. AI. of the above commands In the
file created must be typed in capital letters.
To submit this job, type in :

where Ifn is the fiJe you created.
In order to change your ~OS Interactive Job
password, type In on the 170 side I

where oldpw is your current NOS Interactive
password and neHpw Is your new Interactive
Job password.

1)

loading files into multiple rtngs may cause improper
ring attributes to be assigned.
PSR NVOC789

2)

The fite poslt'on specifier is ignored when mentioned
on SETPA. For example, specifying SETPA DEBUG_OUTPUTa
SLIST.SEO! wltl cause debug to overwrite the $LIST
'ile from Its BOI posltlon (not EOI 8S expected).
PSR NVEA036

~£~_!b~~1~al_1LD_1I~2Al

1)

Tape support Is limited to and intended for use only
by the permanent ,. Ie backup and restore utility. Use
of tape 110 tor any other purpose may produce
undefIned results.

2)

When preparing to mount a tape to be read by NOS/VE, the heads on
the drive should first be cleaned. This Is recommended before
each tape mount due to the currently Incomplete Implementetlon of
error recovery.

- COMPANY PRIVATE -

20

SOFTWARE RELEASE BULLETIN
84/02/10

NOS/VE (CYCLE 17)

1)

The SET_WORKING_CATALOG (SETWCl command has no effect
upon fltes whose names are created wlthln
applications. for example:

SETWC aJ'
execute_task
task generates file name a
The path name of the file Is not .aJI.aJ It Is
$Iocal.a. Onty actual param~ters of a command are
subject to SETWC direction.
PSR NVEAOZ7
Z)

The preset_value fite attribute is not supported.
PSR NVOB204

3)

file attribute MIN_RECORD_LENGTH Is not set properly tor
record_type F fltes. MI~_RECDRD_LENGTH should be set to
MAX_RECORD_LENGTH if It is allowed to default, but It Is
currently defaulting to O. This affects SORT/MERGE when
the sort key Is omitted and the default Is taken.
PSR NVOD398

4)

If more than 100 Instances of OPEN exist concurrently
within a single task, an ame$local_flle_li~it message
Is issued. The message Indicates erroneousl, that
162025 focal files is the limit which Mas exceeded.
The message should say that only 100 instances of open
may exist concurrently in a task.
PSR NVOD856
PSR NV00632

5)

Skipping forward/backward by records and partitions
does not always report the encounter with boundary conditions
with the correct exception condition.
PSR NVOE044
PSR NVOD424

6)

If a FAP returns abnormal status to AMPSOPEN during an
OPEN (new), the file name Is stili registered within
the Job and implicitly created permanent files are not
purged. Recommend explicitly purging the permanent flte.
PSR NVOE150

7)

COPY_FILE does not work on index_sequential files when
executed from with a task.
PSR NVOE58a

8)

Fife attributes that can be changed cannot be

reassigned a NIL value.
- COMPANY PRIVATE -

SOFTWARE RELEASE BULLETIN

21
84/02/10

NOS/VE (CYCLE 17)
PSR NVEA003

9)

DETACH_FILE returns FATAL abnormal status when a file
Is not known and causes a batch job to terminate. Use
of the STATUS parameter to Ignore the error Is
recommended.
PSR NVOD618

10) The SET_FIlE_ATTRIBUTE command for an existing file
accepts the specification of a preserved attribute
even If It conflIcts with the present one. No error will
be seen and the preserved attribute wil' not be changed.
PSR NVOC839
PSR NVOD617
PSR NV00549
PSR NVOD536
PSR NVEA036
11) When processing a CDBOl READ REVERSE statement BAH
fails to set the file position to BOI and 85 a result the
COBOL statement wltl loop Indeflnltel,.
PSR NVOE044
12)

COPY_FILE does not detect a copy to itself via circular
file connections.
PSR NVOEZ86

13)

AmpSput_partlal, with term_option = amcSterminate,
at flte_posltlon BOI, gives 'unrecovered write error'

on a new f1le. Recommend using amp$put_partlal, Mlth
term_option • amcSstart.
?SR NVOD666

14)

Files imp'lettl, attached are not implicitly detached.

PSR NVOE32Z
PSR NVOEZ96

1)

If

t task adds 8 fibrary to the Job's object library
list dynamic loads within that task will be unable to
satisfy externals from the newly added library. This
especlall, affects the usability of commands packaged
in the Job monitor task because libraries added to the
object library fist by the system prolog cannot be used
to satisfy externals of these commends.

PSR NVOE175
2)

The default for the program .ttrlbute lOAn_MAP_OPTION
Is set to NONE. This means a load map will
not be generated by EXECUTE_TASK unless the lOAO_MAP_OPTION
parameter has been prevIously speclfted by a SET_PROGRAH_

- COMPANY PRIVATE -

22

SOFTWARE RELEASE BULLETIN

84102/10

NOS/VE  500

11 Intervals

21 Intervals
101 Intervals

- COMPANY PRIVATE -

30

SOFTWARE RELEASE BULLETIN

84/02/10

NDS/ve (CYCLE 17)
NOTES:

1.

The first and the last intervals on the X axis
one-half the width of the other X axis intervals.

2.

The X-ax's upper limit as dIsplayed may be slightly higher
than the value specified in the subcommand. The rules are:
11 intervals
21 Intervals

101 Intervals

~

t X_upper
X_upper
X_upper

(
(

X_lower
-- X_lower
X_lowe r

l modulus 10
modulus 20

)
)

are

..

0
0

::

modulus 100

::

0

...11 ... 1&3L;a_nl~eL6r_Ilt1E._DlSI&la.uIl!JH_S.l.IU="ClmmJlD51

POT distd_pdt(
metrlc, m: NAME = SREQUIRED
metric_limits, mit LIST 2 •• 2 of INTEGER

title, t: STRING

= SREQUIRED

)

This subcommand generates a graph which plots metric values
against time. The ~-axJs represents the time Intervals and the
V-axis
represents the element counts of the metric.
The
asterisks placed ~ithJn each time Interval represent the range of
element values seen in that interval. The report also generates
the number of elements wIthin the frame and the number of
elements which exceed the frame limits.
The METRIC parameter speclfl9S the metric name to be reported.

METRIC_LIMITS parameter specIfies the limits to be used for
the Y-.xls. The limits for the X-axis wil' come from the date
and time parameters given on the DEFINE_GROUP subcommand.

The

example: mt={O,500}

Y lower bound : 0
Y upper bound a 500

The TITLE parameter Is used to provide a title to be placed on
the top of the report page. If omItted, the metric name will be
used.

- COMPANY PRIVATE -

31

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 11)

!.t.ll£l&l... !t._JllS.e.LAY_llf~C&lfll~E_D.&IA_S.uh=l&QlmaQJI
POT disdd_pdt (
group, g: NAME = SREQUIRED
t i t Ie, t:
STR. ING
)

This sub_command processes the members of a group, rather than a
metric.
It displays values (up to 256 characters long) for the
descriptive data field of each statlstlc In the group, together
with t~e number of times each value was encountered.

The GROUP
required.

parameter

specIfies

the group to be scanned, and is

The TITLE parameter may be used to specify a character string to
be placed at the top of the first page or the report. If It Is
not included in the sub-command, then the name of the group is
used Instead.

POT dlUng_pdt (

group, g: NAME = $REQUIRED
counter_format, efl LIST 1 •• 63, 1 •• 2 range of INTEGER 1 •• 63

tlt'e, t:

STRING

)

This sub_command processes the members of a group rather than a
metric. Each statistic within the specified group Is lIsted In
full. This group dump is particularly useful tor debugging group
specifications and statIstic defInItions.
The GROUP parameter specifies the group
requl red.

to

be

dumped,

and

Is

The COUNTER_FORMAT parameter specIfies in what base the counters
will be displayed. The default base is 10.
example: c'=«(1 •• 8,lO),(9 •• 63,S»)
Counters 1 - 8 will be displayed in base 10.
Counters 9 - 63 will be displayed In base 8.
The TITLE parameter may be used to specify a character string to
be placed at the top of the first page ot the dump. If i t Is not
included in the DUMP_GROUP sub-command, the name of the group is

32

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE {CYCLE 17)
used instead.

POT gen!Jf_pdt (
group, g:
NAME = $REQUIRED
output, 0:
FILE = $OUTPUT
permanent, pI BOOLEAN = FALSE
)

This sub_command selects a group of statistics defined by
sub_command DEFINE_GROUP, and writes the statIstics to a legible
fi Ie in a format suited for machine processing.
The GROUP parameter specifies the group to be
requi'red.

selected,

and

is

The OUTPUT parameter specifies the local file name which contains
the selected statistics.
If It Is not Included
In
the
sub_command, the name SaUTPUT is used as the default fi'e name.
The attributes of the output file Mill bet

FILE_CONTENTS = LEGIBLE
FILE_ORGANIZATION = SEQUENTIAL
fILE_PROCESSOR = UNKNOWN
PAGE_FORMAT = CONTINUOUS
PAGE_WIDTH = 80
( Except 'or the file SOUTPUT, where the
SOUTPUT are used. )

default

attributes

of

If the same file name is used 'or OUTPUT parameter In severa'
GENGF sub_commands, the order of the group statistics Mil. be the
same as the order of the GENGF sub_commands.

The PERMANENT parameter Is a boolean value. If PERMANENT • TRUE,
then a permanent file with the same name specified in parameter
OUTPUT wl.1 be created under the catalog SUSER. If the permanent
file is an existing file, then 8 new cycle ( one higher) wttl be
created. The default value of this parameter Is FALSE.
There are
specified.
1.

some

restrictions when parameter PERMANENT: TRUE Is

Parameter OUTPUT can not be the default value or SOUTPUT.
The
confJlct of the file attributes
cause the
sub_command to be rejected.

w'f'

- COMPANY

P~IVATE

-

33

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)
2.

Parameter OUTPUT can not be the same as In any previous
GENERATE_ GROUP_FILE sub_commands.
The local 'ile name
conflict will cause the sub_command to be rejected.

3.

Parameter OUTPUT can not be the same as an existing focal
'ile name.
The local file name conflict will cause the
DISPLAY_BINARY_LOG to be aborted.

The PERMANENT parameter is not consistent with NOS/VE philosophy,
and may be removed In a future update. This Mill not deprive
users of any functionality.
Examples:

i II ega I usag·e )
defg g=open_lnput s=evlOOO
GENGF g=open_input PERMANENTaTRUE

CASE .1 (

CASE 2 ( J I 'ega I us age )
def~ g=opeo_input s:evlOOO
datg g=Clos8_lnput s=evlOOl
GENGF g=open_input nUTPUT=INPUT_GROUP
GENGF g=close_input OUTPUT~INPUT_GROUP PERMANENT-TRUE

CASE 3 ( leg'tlraate usage)

defg g=open_'nput s=evlOOO
defa g=Clos8_input saevlOOl
GENGF g=open_lnput OUTPUT=INPUT_GROUP PERMANENT-TRUE
GENGF g=closa_input OUTPUT=INPUT_GROUP
Each statistic is output 8S one or more text lines.
The first
lIne contains the header Information, Including the number of
counters and the size of the descriptive data string.
The
counters are output next. occupying as many lines as necessary.
The descriptive data string is output .ast, on a single tine.
The format of each statistic in the output fl Ie Is shown belowl
line

from Ch.

to Ch.

I

Z

:3

1

9

1

It
11

1
1
1
1

19
32
38
47

1
1

70
73

68
71
75

2
2
2
2

1

21)

21
41
.61

40
60

1

2\)

:3
:

..

•

17
30
36
45

8,0

.•

Conte nt.s

statistic_Identifier
stat I.s tl c_code
Julian date( YYJyddd )
tlme( hh:mm:ss.mltllsecond )
Job_name
global_task_id ( nnnn-mmm )
condensing_frequency
number_of_counters
descrlptlve_dats_slze
counter 1 ( right Justified,
counter Z
blank filled)
counter 3
counter 4
counter 5
:

- COMPANY PRIVATE -

34

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/WE (CYCLE 17)
I

n-1
n

.·•

••,.

2

fH)

·
•

·

:
:

desert ptlv8 data

This sub-command has no parameters. It ends acc.ptance of sub-commands, and
begins processing of the prior sub-commands to generate reports.

This command is used to establish and enable one or more statistics to a given
global binary log. It may be abbreviated as "ACTS". The PDT 1st

PDT acts_command (
statistic, statistics, s: lIST Of NAME = SREQUIRED
type, t: KEY statistic, statistics, accountIng, account, •••
engineering • statistic

STATUS )

The STATISTIC parameter specifies one or more statistics to be
established and enabled.
Each statistic Is specified as two
alphabetic characters followed by a decimal number. for examp'e,
AV260001.
A list of statistics, enclosed tn parenthesis as per
Set syntax, may be specified.
The TYPE parameter specifies the globa' binary log to which the
speci'ied statistics are to be enabled. Onl, one tOg may be
specified in each ACTIVATE_STATISTIC command. If It Is desired
to send a particular statistic to more than one log, multiple
ACTIVATE_STATISTIC commands may be used.

This command is used to disable one or more st9tistlcs that had
previously been enabled to a particular log. All statistics
remain establlshed# and If they are enabled to another log, that
connection
remains
undisturbed.
The command name may be
abbreviated as OEAS.

- COMPANY PRIVATE -

35

SOfTWARE RELEASE BULLETIN
NOS/VE (CYCLE 17)

84/02/10

PDT deas_command (
statistic, statistics, s: LIST OF NAME = SREQUIRED
type, t: KEY statistic, st9tistlcs, accounting, account, •••
engineering = statistic
STATUS)

The STATISTIC parameter specifies one or more statistics to be
disabled.
Each
statistic Is specified 8S two alphabetic
characters followed by a decimal number; for exemple, AV2b0007.
A list of statistics, enclosed In parenthesis as per Sel syntax,
may be specified.
The TYPE parameter specifies the global binary log to which the
speclfled statistics are to be disabled. Only one log may be
specified In each DEACTIVATE_STATISTIC command. If It is desired
to disable a particular statistic from more than one log,
multiple DEACTIVATE_STATISTIC commands may be used.
At. statistics spec.fled In the DEACTIVATE_STATISTIC command must
have prevjoYsly been enabled to the specified log, either by an
ACTIVATE_STATISTIC command or by a program Interface call.

The ACTIVATE_INTERVAL_STATISTIC (AeTtS) command is used
to
establish and and enable those statistics which are emitted on an
Inter'Val basis to a toa given global binary log.
This commend
can only be Issued from the system console.

PDT actis_command (
Jms_interval, Ji: integer 1 •• q99 = 1
pms_lnterval, pi: Integer 1 •• 999 • 5
status )

The STATISTIC parameter specifies the statistics to be emitted.
The only valid statistics of this type,currently Is the OS210000
and OS210001 statistics.
The JMS_INTERVAL parameter specifies at what time Interval the
Jms statistic (0$210000) should be emItted. The default value is
1 mInute.
The

PMS_INTERVAL parameter specifies at what time Interval the
PHS statistic (0$210001) should be emitted. The default value is
5 minutes.

- COMPANY PRIVATE -

36

SOFTWARE RELEASE BULLETIN
84/02/10

NOS/VE (CYCLE 17)

The OEACTIVATE_INTERVAl_STATISTIC (DEAlS) commmand is used to
interval statistics that have previously been enabled to a particulaf.
log. This command only disables the 05210000 and OS210001 statistics.
This command can only be issued from the system console.
disabl~

PDT deals_command (
status)

This is a list of the current statistics available on NOS/VE.

STATISTIC

NAME

COUNTER/DESCRIPTIVE DATA

Accounting Cp time

ClI Total CP increment
C2: Job-mode cp time Incr.
C3: Monitor-mode cp time incr.

AV260()Ol

Accounting Page faults

Cl: Total page fault Incr.

AVZ60002

Accounting working set

el: Current W.S. size

AV260003

Accounting Ready Tasks

C1: Current ready task count

- COMPANY PRIVATE -

37

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)
AV260tl06

Accounting Begin Accnt.

00: 1-31
32-33
34-64

AV260+)07

Accounting End Account

name
- account
,
t,
- project name

-

el: Total Job SRU's
Total Job CP time

e21
AVZ6(H)Oa

,~ccount

I ng SRU' s

Cl: Total SRU Increment

Cl110000

Display message command

DO: String specified in
command

tl170001

Comr~~nd

JM180000

User name

DO: User name) 31 characters

JM18(lOOl

Job name

DO: User's Job name; 31 chars

Jr1180i)02

Job mode

DDt 'INTERACTIVE' or 'BATCH';
11 characters

JH180003

Job end

Cl: CP time - Job mode
ell Cp time - monitor mode
C3: Page 'au Its

names

00: Name ot command; upper
case, 31 characters

C4: Page-J ns

CSt Page-reclaims
C6: Page-assigns
PM 230000

Task begin

None

PM230C'Ol

Task Starting Procedure

DO: Starting procedure name;
31 ch ar acter s

PM 230;;.)02

Task

name

00: Task name) 31 characters

PM2300()3

Task

end

Cl: CP time - Job mode
ell Cp time - monitor mode
C3: Ps:ge faults
C4: P 8 9 e-I n s

C5: Page-rec'alms
C6:P age-as signs
PM230004

Loader begin

none

PM230;:)05

loader end

Cll CP time - Job mode
e2: Cp time - monitor mode
e3: Page -faults
C4: .Page-ins
C5t Page-reclaims
C6 sPage-ass 'gns

FC580000

Fortran Compilation

Cl: Task time In compiler
Cl: Monitor time

- COMPANY PRIVATE -

38

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)

e3: No. of lines compiled
C4: No. of statements
C5: No. of program units
FC.580001

Fortran Program Unit

DDt Program unit name
Cl: Task time for unit
el: Monitor time for unit
e31 No. of lines in unit
C4: No. of statements

OS210()OO

JHS-j nterV:2 I

Cl: 'f ree pa ges
ell available pages

(jo~-memory

interval)

C3: available modified pages
C4:wlred pages
C5:shared pages
Co: fixed pages
e7: 10 error pages
C8t Job shared pages
C9: Job working set pages
ClOt swapped Jobs
ell: ready tasks
el2: Interactive class
e13: batch class

C14:
C15:
Cl b:
t17:
C18:
OS 2 1 C)() 0 1

PHS-interval
(paging-monitor Interval)

site class 0
site class 1
site c I ass Z
site class 3
maintenance class

CIt pI evallable

ell pf available modjfled
C3: pf disk read
C4: pf new page
C5:p t locked
C6: P" 10 reject

C7: force aggresive aging
CS: aggreslve aging shared queue
C9: aggreslve aging Job queue
ClOt

.aggres lYe ag i no f a II ed

ell: write aged page
C12: mr cycle
el3: mr cycle average duratIon

mr delay
CIS: mr delay average duration

C14:

C16: mr we It

el7: mr walt average duration
CiS: mr write modified pages
C19: mr write modified pages
average duration

- COMPANY PRIVATE -

SOFTWARE RELEASE BULLETIN
NOS/VE (CYCLE 11)

39

84/02/10

The ADMINISTER_USER utltity can be run from I batch job
or Set procedure contrary to what the Family Administrator
for NDS/VE Usage Manual says.
PSRs NVEA045 and NVEA046

- COMPANY PRIVATE -

40

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)

1)

When using DEBUG to breakpoint on a multi-line
statement, the line number suppl led to DEBUG must
be the last tine number of the statement.
CILA498

2)

prohibits the user from defining an integer
greater than 48 bits. This has been fixed In the Cycle
18 compiler version 83333.
PSR CIlA609, PSR Clll515

3)

The 256th character of an Sel string variable cannot be
set to any character other than a space. This Is
corrected in CrBll 83333 for Cycle 18.
PSR CIlA634

1)

The COBOL READ REVERSE statement does not Mork. If used,
It will loop Indefinitely on the first record and never
take the AT END path. This Is the result of BAM failing
to set the file position to BDl.

Cybil

PSR NVOEf)44

2)

Two consecutive instances of OPEN OUTPUT on the same indexed
sequential file wi II not cause a message warning that the
data has been evicted by the second OPEN. The user should
refrain from Issuing another OPEN OUTPUT once the ftle has
been created.
PSR AA8A106

1)

Tape support Is limited to and Intended for use by the
permanent tile backup and restore utility. Use of tape
110 for any other purpose may produce undefIned results.

2)

When preparing to mount a tape to be read by NOS/Ve, the heads on
the drive should first be cleaned. This is recommended before
each tape mount due to the currentl, Incomplete Implementetion of
error recovery.

- COMPANY PRIVATE -

41

SOFTWARE RELEASE BULLETIN
84/02/10

NOS/VE (CYCLE 17)

l}

Do not use the file name INPUT In batch mode. It Is
always a null (empty) fite with no data in It. Choose
8 different name.
This affects migration
of Jobs from NOS, where the name INPUT was the Job's
Input deck. On NOS/VE use the COLLECT_TEXT command to
create the input data.

2)

When using FMU and Inside Interstate Communication
Facility, do not do a CLEAR on the EXECUTE_INTERSTATE
CO"~ANO.
This wit' c'e~r FMU checkpoint files and
render FMU Inoperable.

1)

when using READ (* ••• )

In batch ,jobs,af.le

containing the desired input must be connected to
SINPUT by CREATE_FILE_CONNECTION or equated to INPUT
on the FTN program state~ent or LGOstatement.

2)

If INPUT or OUTPUT Is opened using an OPEN statement,
the OPEN statement must be changed to use SINPUT or
SQUTPUT.

3)

To lnsure correct listings and Improve compilation performance
it is necessary to prevent the listing file and the errors file
from being the same fl'e. In batch Jobs both wou.d default to
SOUTPUT. To avoid this set the ERROR parameter on the FORTRAN
command to a fife reference different rrom that of the LIST
parameter.

A Job using an Indexed sequential 11 Ie wlll'all due to
entry point errors from the loader.
The following command executed earlier in the Job will
o;r r e c t t h j s :

C

SET_PROGRAM_ATTRIBUTES TERMINATION_ERROR_LEVEl=FATAL
or SErPA TEL=F

PSR NVOC941, NVOE276

- COMPANY PRIVATE -

42

SOFTWARE RELEASE BULLETIN
84/02/10

HOS/VE (CYCLE 17)
~~I_SQU£~I_'Qda_U11111~

1)

The Stu editor command SEARCH_BACKWARD will hang if
asked to locate multiple occurrences of a range of
text. A terminate break will stop the hung command
and a.low the user to continue editing.
PSR SC8A021

2)

An anomaly can occur when some modifications are
excluded when a deck Is expanded. An example
is below:
line 1 version 1.
is introduced by modification A. Modltlcatlon B
replaces thl s line with

line 1 version 2.
Then modificatIon C in turn replaces this line
with
Line 1 version 3.
If one expands the deck with modification B
excluded both the Jines introduced by modIfications
A and C wltl appear In the COMPILE file.

If a Job calls a procedure In a tower-numbered rlng and
that procedure causes an error, then Debug does not give
a proper indication of the problem. Debug reports
that PM INVALID SEGMENT has occurred In the user's program
at the line which orlglnall, called the (faulty) procedure.
This situatIon can occur when a CYBIL program calls an OS
procedure and the as procedure does something wrong.

Help (also known as EXPLAIN_MESSAGE) does not exist In the
system.

- COMPANY PRIVATE -

43

SOFTWARE RELEASE BULLETIN
84/02./10

NDS/VE (CYCLE 17)

The BATCHIO printer driver does not correctly handle long lines
(over 135 characters). The extra characters are either dropped,
overprinted, or cause the page to be spaced erratically.
NS2C 1.21

- COMPANY PRIVATE -

SOFTWARE RELEASE BULLETIN

44
84/02/10

NDS/VE (CYCLE 17)

The 'olawing tables show the microcode and controlware levels that
were used to validate the NOS/VE system on the specified hardware
systems supported. These tables show the latest official FeA levels
of the hardware and microcode and the necessary modifications
(deviations) required to support the NDS/VE system. Tables 1, Z,
3, and 4 correspond to the eI70-St5, C170-825, C170-835,
C170-845, and e170-aS' systems, respectively.

- COMPANY PRIVATE -

SOFTWARE RELEASE BULLETIN
NDS/VE (CYCLE 17)

45
84/02/10

Jef.Ef!nl!_a_tUJs.l~f_efRleHEB.AL_l!IAltiIEtiAtic.E_SUee.QBI

- COMPANY PRIVATE -

Al-l

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)
Al.O DEVICE CHARACTERISTICS

1
Z

,.
3

5
6
7

8
9

Al.l.l PHYSICAL CHARACTERISTICS

10
11

844-ltx

Splndl as/Cabinet

1

2

Cylinders/Spindle
Tracks/Cy II nde:r

823

843

19

Bytes (8 bit)/Sector

24
483

40
32
516

Sectors/Track

12
13
14
15
16
17
18
19
20
21

885-1 x

22
23

AI.1.2 LOGICAL CHARACTERISTICS

Z4

25
26

27

. za

2.9

•

Allocatlon_unJt - The quantum of assignment of mass storage
space to a file. An allocation_unit is a power-of-two multiple
of consecutive DAUs. At present, the allocation_unit Is not
selectable on a tile by flte basis; all end-user files default
to 16384 byte allocation.

•

Device_allocation_unit (DiU) - The quantum of a'locatlon of 8
mass storage volume (spindle).
MOS/VE views a device 85 an
array of OAUs which individually or as a contiguous group
(called an allocation_unit) may be assigned to a mass storage
'lie. A OAU consists of an Integral number of MAUs; the fatlo
is device dependent and dependent upon the granularity of
allocation NOS/VE can afford to provide for a particular device.
A DAU may span tracks but never spans cylinders of 8 device.

•

large_sector
A controlware capabJ Itty provIded by the 7155
class of mass storage controller which logically groups four
physical sectors Into one for the purpose of decreasing device
drIver overhead. The term 'MAUl is preferable to 'large sector'
since ~ot all controllers may prov1de this capability to NOS/VE.
Note that a large_sector on an 885 device Is composed of four

30
31

32
33
31t

35
36
37
38
39
40
1t1
42
43

44

- COMPANY PRIVATE -

45
46

47
48

49
50

A1-2

SOFTWARE RELEASE BULLETIN

64/02/10

NOS/VE (CYCLE 17)

Al.O DEVICE CHARACTERISTICS
A1.1.2.1 Terminology
physical sectors each of which contains 516 bytes. The last 33
of these bytes are not transferred Mhen a physical sector is
read in small sector mode.
Ther~fore,
It Is possible that
NQS/VE
witl
encounter
additional bad-spots on a device
prevlousl, only accessed In small sector mode.
The
Ol8
diagnostic is provided to verify the data field of a large
sector. The controlware and NOS/VE consistently report failure
status in terms of physical (sma") sector address. The large
sector dlaJnostlcs such as Ol8 end FLD, however, display large
sector address.
When using the latter diagnostics, It Is
recommended that one rely on the sector address in the deta'Jed
status.

..

Minimum_addressable_unit (MAU)
The quantum of date transfer
supported by a PP driver. The MAU is a software concept which
is used to normalize the various device sector sizes for the
Central Processor. When the CP prepares requests for mass
storage devices it thinks In terms of a number of MAUs. The PP
driver then breaks down the MAU into physical address and
sectoring considerations. If a mass storage device has a sector
size which is not a power of two bytes In length (such as the
844-4x), then th~ MAU wll' begin at the start ot a sector and
finish In the midst of the last sector; the number of sectors
spanned is device dependent. An "AU may span tracks but never
spans cylinders of a device.

1
2
3

"
5
b
7
8
q

10
11

12
13
14
15
16
11
18
19
20

21
22
23
Z4

25
26

•

Page_size - A power of two number of bytes ranging from 512
bytes to 65536 bytes.
NOS/VE is presently constrained to
supporting page sizes of 2048, 4096, 8192 and 16384 bytes.
The
constraint is a file system constraint reJated to .)not wanting
more than one page per MAU and b) not wantln9 8 page to span
tr acks.

27

28
29
30
31
32
33
34

3S

844-4.x

Sectors/MAU
M.AU1Track

OAU/Track
DAU/Cy I I nder

DAti/Spindle
Byta.s I

~tAU

Bytes/Track (avg.)
Bytes/Cylinder
10**6 Bytes/Spindle
10**6 Bytes/Segment

5
4.8
.2.4
44
31035
2048
9485.4
180224

151.6
2147.5

36
37
38
39

BSS-lx
4

40
41

4

1t3

160
134880
2048
16384

44

e

42

45
46

41

655360
552.• 46
2147.5

48

49
50

- COMPANY PRIVATE -

A1-3

SOfTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)
Al.O DEVICE CHARACTERISTICS
.1.1.2.2 NOS/VE Disk Volume Allocation
1

2
3
It

Allocation Unit Size:
(Consecutive DAUs)
1
2
4
8

16
~,

;;'w.-

64

128
256

844-4x
(bytes)

4096
8192
16384
32168
655.36
131()12
180224
180224
130224

5
6
7
8

885-1x
(bytes)

9

10
11
12

4096
8192
16384

13
14
15

32768

65536
131072
262144

16
11

18
19
20

524.288

655360

21
22
23
24
25

A1.2.1 PHYSICAL CHARACTERISTICS

26

27
28

Al.2.2 LOGICAL CHARACTERISTICS

29

30
31

32
33
34

35
36
37
38
39
40
41
42
43
44
45
46

47
48
49
50

- CDMPANY PRIVATE -

A2-1

SOFTWARE RELEASE BULLETIN

84/02/10

NDS/VE (CYCLE 17)
A2.0 MASS STORAGE VOLUME MANAGEMENT

A2.0

HASS_Sla&AiE_~aLUHE_~AUAGE!EHI

1
2
3

"
5
6
7
8
9

AZ.lSYSlftl_lt:1S,I61.LAI10tl_f.REfAB.AIlflM

A2.1.1 PREPARING 844 AND 885 DEVICES

All 844 and 885 volumes are 'ormatted at the factory. Neither 844
nor 885 volumes need to be reformatted to be used by NOS/VE. Volumes
used by NOS are Interchangeable with NO$/YE without re-formattlng.
Utility Map processing is identical in all aspects. However, with the
exception of the Factory Map and the Utility Map, the date recorded on
8 volume by NOS cannot be interchanged with NOS/VE and vice versa.
NOS/VE does not honor the eTI deadstart sector content. Therefore
it does no good to install CTI or CMl on a NOS/VE device nor
can one
expect this Information to remain Intact across mixed system use of
the device, e.g. first NOS, then NOS/VE and then NOS again. eTI and
CMl should only be installed on the NOS deadstart device or an
alternate device used ani, by NOS.
Prior to attempting NOS/VE system installation, the f0110wing
procedures shou'd be performed either on-tine using MAlET on NOS or
off-tine using DEMOT. The objective of these procedures Is to ensure
the correctness of the Utility Map maintained on each device. The
INITIAlIZE_MS_VOLUME process described later uses the Utility Map to
avoId defects (bad-spots) on the disk surface.

10
11
12
13
14
15
16
17
18
19
20

21
22
23
24
25
26
21
28
29
30
31
32
33
34

35
36

A2.1.1.1

S~~1Am_D~4d~taLt_DA~lcA

31
38
39

For the NOS/VE system deadstart device i t Is recommended that
the SCAN DISPLAY FLAWS module of the FMU diagnostic be used to
disp'ay atl the sectors which have track or sector flaMs set.
This display must then be compared to the display of the Utility
Map. Any flaKed sectors not In the Uti lity Map must be added to
ensure that the Installation of the NOS/VE system will gO
smoothly. This procedure should be expected to take at 'east 10
minutes. Refer to the discussion of defect m8n~gement below for
further insight as to why the above procedure Is recommended.
b. Use the Ol8 diaunostic to write/read large sectors on Cylinder
0, Track 0 of an 885 deadstart device.
This accomplishes tHO
8.

- COMPANY

PRIVATE -

40
41
42
43
44
45
46
47
48
49
50

A2-2

SOFTWARE RELEASE BULLETIN

84/02/10

NOS/VE (CYCLE 17)

A2.0 MASS STORAGE VOLUME MANAGEMENT
A2.1.1.1 System Deadstart Device
thIngs: 1) it proves that track 0 can later be written by
INITIALIZE_HS_VOLUME (INIMV) 2) It ensures that fictitious
unrecovered checksum failures are not encountered by INIHV when
performing NOS/VE label searching.
Note that it is totally
unnecessary to write large sectors on the whole device because
NOS/VE never reads a sector that
It has not first written
(except during INI"V label searching).

1
Z
3
"
5
6
1
8
9

A2.1.1.2

10
11

KAlYml~_D1ha&_Ib.Q_tbA_S~~tam_Q.ad~t~Lt_Q.~lca

12
13

The above procedure is strongl, recommended for each
device to be used by NOS/VE.

A?.2

.ass

storage

ltiI.IIALIZE_t:lS_lLDLUHf

14
15
16
17
18
19
20
21
22

A2.2.1 INITIALIZATION Of 844 AND 885 VOLUMES

23
Z4

25
26

The
INITIALIZE_HS_VOlUME
(INIMV)
subcommand of the logical
Configuration Utility (LeU) is used during the NOS/VE installation
process to prepare m~ss storage volumes for use by NDS/VE. The
Initialization includes writing a NO$/VE software label on the volume
and processing the Utility Map located on the volume Itself. Before
proceeding with the initIalization or the vo1ume, INIMV attempts to
read a NDS/VE label 'rom one
three possible locations on the
volume: "iUs 1, 2 and 3 are trled In succession. This Is done as a
protection against operator error which could destroy files on the
volume if re-lnltlallzed.

0'

27
28
29
30
31
32
33
34
35
36

37

If an 885 volume has not been prevlousl, Inltl.llzed by NOS/VE or
has not been written in large sector mode by diagnostic software, then
an uncorrected checkword failure wIll be reported for each ot the
three attempts made by INIMV to read a NOS/VE label. Unrler the
previous'y stated conditions, the reporting of th~se 3 failures Is
IX21,L.e.d. and should Q~1 be a souree of concern. The 3 locations read
by INIMV, in the order attempted, are:
I.Cyllnder 0, Track 0, Sector 0
2.Cyllnder 0, Track 0, Sector 4
3.Cyllnder 0, Track 0, Sector 8 (10 octal)

38
39
40
41
42
43
44
45
46
47
48

Note that for an 844 device, checkword fai .ures
during INIMV label checking.

are

n~l

expected

- COMPANY PRIVATE -

49
50

SOFTWARE RELEASE BULLETIN

AZ-3
84/02/10

NOS/VE (CYCLE 17)
Al.O MASS STORAGE VOLUME MANAGEMENT
A2.2.1 INITIALIZATION OF 844 AND 885 VOLUMES

1

Once convinced that It is not destroying files by mistake, INI"V
proceeds to write a NOS/VE label on the volume. Next It processes the
Utility Map recorded on the volume. The location of the Utility Map
Is device dependent as Is the content of the map. However the manner
In which the Utility Map is read by the NOS/VE driver Is device
Independent as followst
The 844 and A85 Utility Maps ere written in sm31. sector format by
the factory and by diagnostic utl11tles.
The Utility Maps fall
somewhere within a NOS/VE MAU (logical sector of 2048 bytes). The
driver Is given an MAU ordinal by INIMV end t~e driver attempts to
deliver an "AU.
This Involves reading either 4 or , small sectors
depending upon the device. Because some Gf the sectors have been
write-protected by the controller and some have not the driver
attempts to read each small sector using the following sequence of
commands:
l.Read protected sector (34)
2.Read (4)

2
3
It

5
6
7
8
q

10
11
12
13
l~

15
16
17
18
19
20

3.Read factory data (30)

21

4.Readuti I) ty map ( 3 1 ) 2 2

If an address error's returned for 8 particular sector the next read
function is tried for the same sector until all 4 generic read
functions have been tried or the read Is successful, whichever occurs
fIrst. Intervening address error failures are not reported, only the
last of the four. Any 'allure other than an address error detected
after any of the four generic reads causes request termination and is
reported.

,A2. 2 .l.l

23
24
2S
26
27
28
29
30
31
32
33

a~_utl11.t:t_t1.12_!.to.~.cS.;ilJlJl

34
35
36

The INTIALIZE_MS_VOlUME subcommand uses the utility Map located at
Cylinder 822, Track 0, Sector 2 to flaw defects "hlch have been
detected at the factory or by the CE and recorded In the Utility Map.

"37
38
39

The Utility Map is an array of 0 •• 161 flaw entries. Each entry
documents either 8 track flaw or a sector flaw. Sector flaws are
recorded in the physical (sma") sector nu.berlng scheme.

41
42
43

40

44

INIMV logically flaws the DAU affected by a sector flaM and the 3
OAUs affected by a track flaw. Note that because of the data mappIng
of the 844 device a track flaw wl11 also 10glcat.y flaw from 0 to It
small sectors on the next track.

45
46
~7

48
49

To support

dia~nostJc

use of the device, INIMV a.so flaws cylinders

- COMPANY PRIVATE -

50

A2-it

SOFTWARE RELEASE BULLETIN
84/02/10

NOS/WE (CYCLE 11)
A2.0 HASS STORAGE VOLUME MANAGEMENT
A2.2.1.1 844 utility Map Processing
820..

822.

1
2

3
A2. 2.1. 2

It
.5
6
7

a~2_U.tll1t~_8.i2_et.Q.G&~~1.D2

The I~ITIALIZE_MS_VOLU"E subcommand uses the Utility Map located at
Cylinder 841, Track 1, Sector 1 to flaw defects which have been
recorded there by the factory or by aCE.
The Utility Map Is an array of 0 ••
documents a track 'taw.

INIMV
track.

logically

f1aws

the

To support dia1nostic use of
841 •• 842.

161 flaw entries.

Each

entry

4 DAUs which are affected by a 'taMed
the

device.

INIMV

'laMs

cylinders

8
q
10
11
12

13
14
15
16

17
18

19
20

21
22
23
A2.3 l t Q L U r : 1 f _ f l f E f t . I _ l 1 A t ! ! G f t 1 f t i I Z 4
25
26

AZ.3.1 RECOMMENDATIONS FOR 844 ANO 885 DEVICES

27
28

Zq

30

Once NOS/VE has been instal ted and allot Its mass storage volumes
have been Initialized, It is possible that additional defects witt
appear on the surface of a volume.

31
32
33

The symptom or this defect is likel, to initially be a recovered
read/write failure. If the same sector Is reported repeatedly, one
may wish to take action to avoid the loss of performance Incurred by
repeated disk driver recovery attempts. The SAVE DATA and RESTORE
DATA capabilities of the FMU diagnostic utility may be used to
relocate the failing sector. This capability only applies to 885
devices as these devices provide two spare sectors per track for this
purpose. The procedure must be performed off-line to NOS/VE.
Refer
to the discussion of ofr-Ilne "awing for further Information.

35
36
37
38
39
40
41
42
43

34

44

If the symptom of the defect Is an unrecovered read failure, the
recommended procedure is to delete the '1 Ie to which the failing
sector was allocated.
The deletion of the file should only be done
after repeated attempts to read the file have all tailed.
It Is
possible

t«««

~5

46
47
48
4q
50

-

COMPANY

PRIVATE -

SOFTWARE RELEASE BULLETIN
NOS/VE (CYCLE 17)

84102/10
1
Z
3
It

5
6

7
8
9

10
11
12
13
14
15
16
17
18
19
20

21
22
23
24
25

26
27
28
29

30
31
32

33
3ft

35
36
37
38
39

'to

41
42
43
44
4!1

46
47
48

49
50
51
52
53
54

- COMPANY PRIVATE -

1

SOFTWARE RELEASE BULLETIN

84/02/10

NDS/VE (CYCLE 17)
TabJe
1.0
2.0
3.0
3.1

INTRODUCTION
fEATURES AND
INSTALLATION
Installation

or

Contents

•••••••••••••••••••••
PRODUCTS • • • • • • • • • • • • • • • •
AND OPERATIONS NOTES • • • • • • • • • •
•••••••••••••••••••••

3.1.1 NOS Installatlon • • • • • • • • • • • • • • • • • •

3.1.2 NOS/VE Installation • • • • • • • • • • • • • • • •
3.2 NOS/VE Executive • • • • • • • • • • • • • • • • • • •
3.3 Operator Commands • • • • • • • • • • • • • • • • • •
3.4 Configuration Management • • • • • • • • • • • • • • •
3.5 Device Management/Recovery • • • • • • • • • • • • • •
3.6 Physlca' 1/0 (Tape)

•••••••••••••••••

3.7 Interactive • • • • • • • • • • • • • • • • • • • • •
4.0 OPERATING SYSTEM NOTES AND CAUTIONS • • • • • • • • •

4.1 System Command Language • • • • • • • • • • • • • • •
4.1.1 Additional Commands (Not in Manuals) • • • • • • • •

4.1.1.1 DISPLAY_COMHAND_PARAMETER(S) (DISCP) • • • • • • •
•••••••
4.1.2.1 SCOMMAND_SOURCE • • • • • • • • • • • • • • • • •
4.1.2.2 SPREVIOUS_STATUS • • • • • • • • • • • • • • • • •

4.1.2 Additional Functions (Not in Manuals)

4.1.2.3 SQUOTE • • • • • • • • • • • • • • • • • • • • • •

4.1.2.4 SSCAN_ANY • • • • • • • • • • • • • • • • • • • •
4.1.2.5 SSCAN_NOTANY • • • • • • • • • • • • • • • • • • •
4.1.2.6 SSCAN_STRING • • • • • • • • • • • • • • • • • • •
4.1.2.7 STRANSlATE • • • • • • • • • • • • • • • • • • • •
4.1.2.8 STRIM • • • • • • • • • • • • • • • • • • • • • •
4.1.3 Additional Control Statements (Not In Manuals) • • •
4.1.3.1 PUSH_COMMANDS • • • • • • • • • • • • • • • • • •
4.2 Permanent Files • • • • • • • • • • • • • • • • • • •
4.3 Remote Host • • • • • • • • • • • • • • • • • • • • •
4.4 Program Management • • • • • • • • • • • • • • • • • •
4.5 Physical 1/0 (Tape) • • • • • • • • • • • • • • • • •
4.6 Basic Access Method • • • • • • • • • • • • • • • • • _
4.7 loader • • • • • • • • • • • • • • • • • • • • • • • •
4.8 Interactive • • • • • • • • • • • • • • • • • • • • •

2
3

4
4
4
4
6

10
11

9

12
13

10
11
12
12
13
13
13
13
14
14
14
15
15
16
16
16

- COMPANY PRIVATE

25
26

27
28

16

29

30
31
32

ZZ

25

••••••••••••••

14
15
16
17
18
19
20
21
22
23
24

17
17
lq
19
20
21

4.11.1.2 Oefinitlon Sub-commands • • • • • • • • • • • • •

4.11.2 The ACTIVATE_STATISTIC Command • • • • • • • • • •
4.11.3 The DEACTIVATE_STATISTIC Command • • • • • • • • •

7
8
9

6

22
23
24

4.11.1.5 The QUIT Sub-command

~

5
6

7

4.9 Job Management • • • • • • • • • • • • • • • • • • • •
4.10 Interstate Communication • • • • • • • • • • • • • •
4.11 DISPLAY_BINARY_lOG • • • • • • • • • • • • • • • • •
4.11.1 DISPLAY_BINARY_lOG • • • • • • • • • • • • • • • •
4.11.1.1 The Display_binary_log Command • • • • • • • • •
4.11.1.2.1 The DEFINE_GRDUP Sub-command • • • • • • • • •
4.11.1.2.2 DEFINE_METRIC Sub-command • • • • • • • • • • •
4.11.1.3 Display Sub-commands • • • • • • • • • • • • • •
4.11.1.3.1 DISPLAY_SUMMARY Sub-command • • • • • • • • • •
4.11.1.3.2 DISPLAY_DISTRIBUTION Sub-command • • • • • • •
4.11.1.3.3 DISPLAY_TIME_DISTRIBUTION Sub-command • • • • •
4.11.1.3.4 DISPLAY_DESCRIPTIVE_DATA Sub-command • • • • •
4.11.1.3.5 DUMP_GROUP Sub-command • • • • • • • • • • • •
4.11.1.4 GENERATE_GROUP_FILE Sub-command • • • • • • • • •

1
2
3

24
2-4

33
34

35
36

37
38
39
40

41
42

26

43

27
28
28
28

44

30

31
31
32
34
34
34

45
46

47
48
49

50
51
52

53
54

l

SOFTWARE RELEASE BULLETIN

64/02/10

NOS/VE (CYCLE 17)

4.11.4 ACTIVATE_INTERVAL_STATISTIC • • • • • • • • • • • •

3.5

4.11.' DEACTIVATE_INTERVAL_STATISTIC • • • • • • • • • • •
4.11.6 STATISTICS AVAILABLE IN NOS/VE • • • • • • • • • •
4.12 Accountlng/Vatldation • • • • • • • • • • • • • • • •
5.0 PRODUCT seT NOTES AND CAUTIONS • • • • • • • • • • • •
5.1 CYBIL • • • • • • • • • • • • • • • • • • • • • • • •
5.2 COSOL • • • • • • • • • • • • • • • • • • • • • • • •
5.3 TAPE 110 • • • • • • • • • • • • • • • • • • • • • • •
5.4 File Management utility • • • • • • • • • • • • • • •
5.5 FORTRAN • • • • • • • • • • • • • • • • • • • • • • •
5.6 Advanced Access Methods • • • • • • • • • • • • • • •
5.8 Source Code Utility • • • • • • • • • • • • • • • • •
5.9 Product Set - DEBUG • • • • • • • • • • • • • • • • •
5.10 On line Manuals • • • • • • • • • • • • • • • • • • •
6.0 NOS R2.2 • • • • • • • • • • • • • • • • • • • • • • •
7.0 FeA lEVELS • • • • • • • • • • • • • • • • • • • • • •
APPENDIX A NOS/VE PERIPHERAL MAINTENANCE SUPPORT • • • • •

1

36
36
3q

2
3

4

40

5

40
40
40

6

41
41

7
8
9

10

41

11

42

12
13
14

42
42

44

15
16

45

17

• • • • • • • • • • • • • • • • • • • • • • • • •

A-I

19

Al.O DEVICE CHARACTERISTICS • • • • • • • • • • • • • • • • •
Al.1 DISK DEVICES • • • • • • • • • • • • • • • • • • • • • •
Al.1.1 PHYSICAL CHARACTERISTICS • • • • • • • • • • • • • •
Al.1.2 LOGICAL CHARACTERISTICS • • • • • • • • • • • • • • •
Al.l.l.l Terminology • • • • • • • • • • • • • • • • • • •
Al.l.2.2 NOS/Ve Disk Volume Altocatlon • • • • • • • • • •
Al.l.2.3 NDS/VE fife Allocation • • • • • • • • • • • • •
Al.2 TAPE DEVICES • • • • • • • • • • • • • • • • • • • • • •
A1.2.1 PHYSICAL CHARACTERISTICS • • • • • • • • • • • • • •
A1.2.2 LOGICAL CHARACTERISTICS • • • • • • • • • • • • • • •

A1-1
A1-1
A1-1
Al-l
Al-l
Al-2
Al-3
A1-3
A1-3
A1-3

A2.0 MASS STORAGE VOLUME MANAGEMENT • • • • • • • • • • • • •
AZ.l SYSTEM INSTALLATION PREPA~ATION • • • • • • • • • • • • •
A2.1.1 PREPARING 844 AND 885 DEVICES • • • • • • • • • • • •
Al.l.l.l System Deadstart Device • • • • • • • • • • • • •
A2.1.1.Z Volumes Other Than the System Deadstart Oevice •
A2.2 INITIAlIZE_MS_VOlUME • • • • • • • • • • • • • • • • • •
A2.2.1 INITIALIZATIDN OF 844 AND 885 VOLUMES • • • • • • • •
A2.2.1.1 844 Utility Map Processing • • • • • • • • • • •
AZ.2.1.2 885 UtIlity Map Processing • • • • • • • • • • •
A2.3 VOLUME DEFECT MANAGEMENT • • • • • • • • • • • • • • • •
A2.3.1 RECOMMENDATIONS FOR 844 AND 885 DEVICES • • • • • • •

A2-1
A2-1
A2-1
AZ-l
A2-Z
A2-2
A2-2
A2-3
A2-4
A2-4

43

18

APPENDIX A

A2-~

20
21
22
23
24
25
26

27
28
29
30
31

32
33
3·4

35
36
37

38
39
~C

41
42
43

44
45
46
47
48
4q

50

51
52
53
54

- COMPANY PRIVATE -



File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.3
Linearized                      : No
XMP Toolkit                     : Adobe XMP Core 4.2.1-c043 52.372728, 2009/01/18-15:56:37
Create Date                     : 2011:08:12 13:24:40-08:00
Modify Date                     : 2011:08:13 01:33:12-07:00
Metadata Date                   : 2011:08:13 01:33:12-07:00
Producer                        : Adobe Acrobat 9.45 Paper Capture Plug-in
Format                          : application/pdf
Document ID                     : uuid:108b05ea-d27d-4954-a73c-c5d2ff29c616
Instance ID                     : uuid:e40b7733-f0a2-4c78-aa56-ca4a21455d4c
Page Layout                     : SinglePage
Page Mode                       : UseNone
Page Count                      : 55