NOS_VE_1.1.2_Level_630_Sofware_Rel_Bulletin_Mar85 NOS VE 1.1.2 Level 630 Sofware Rel Bulletin Mar85

NOS_VE_1.1.2_Level_630_Sofware_Rel_Bulletin_Mar85 NOS_VE_1.1.2_Level_630_Sofware_Rel_Bulletin_Mar85

User Manual: NOS_VE_1.1.2_Level_630_Sofware_Rel_Bulletin_Mar85

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

Download
Open PDF In Browser	View PDF

1
85103/29

SOFTWARE RELEASE BULLETIN
NOS/VE ~1.1.2
LEVEL 630

NOS/VE and its product set are intended for use only as
described in this document. Control Data cannot be
responsible for the proper functioning of undescribed
features and parameters.

Revision Date:

3/29/85

~UFTWARE

1-1

RELEASE BULLETIN

851fJ3/29

NOS/VE Rl.1.2 lEVEL 630
1.0 INTROOUC TI ON

The NOS/VE Rl.l.2 level 630 Software ~e'ease Bulletin (SRB) is to be
used with the NOS/VE Instal~3tion an1 Upgrade Manual (Publication
60463913) for installing NOS/VE and its software products. Control Data
recommends that the SRB be read in Its entirety prior to software
i nst at. atl on.
The SRB is the vehicle used to docume~t any changes to the Instal'ation
and Upgrade Manual after it has gone to print. The SR8 also documents a
number of system deficiencies. It is Aecessary to install NOS 2.4.1
Level 630 or NOSfBE 1.5 leve. 621, level &28 of the Common Products, and
CIP 003 before installing NOS/V~ Rl.l.2.
The following warnings and
release:

restrictio~s

are especially important to this

1. A Backup_Permanent_Ftle operation must be done using the old
system before upgrading to Rl.l.2 and the files restored using
level Rl.l.2. See Sectio~ 3.1.2 for more information.
of
release 1.1.2, permf:\nent file labels wi.1 be written in a
neM format which older systems wi" not be able to read.
This
presents no prob'em unfess permanent files created on a Rl.l.Z
system or later must be used on a system older than Rl.l.2.
Should this situation arise. contact Central Software Support for
guidance.

2.A:s

3. A new version (VI.l) of object code library format has been
implemented to support improved message template capabilities.
Message template modules are now created through
the
OCU
CREATE_MESSAGE_MOOULE subcommand which places message template
modules on the object library. The ncu on the Rl.l.2 system can
accept object modules fro~ both old (VI.D)
and new (Vl.I)
libraries but will only generate new (Vl.1) format libraries.
Libraries created by the Rl.l.2 OCU cannot be used by previous
versions of the system or previous versions of OCU.
Object
modules (but not SeL procedures or program descriptions) can be
moved from a Vl.l library to a Vl.O library as follows:
a. Using the Vi.l CREOl, do the following:

CREOL
ADoM vll_library "version Vl.l library"

SOfTWARE RELEASE BULLETIN
851 lJ3129

NOS/VE Rl.l.2 lEVEL 630

1.0 INTRODUCTION

GENl obJect_fite f=f "generates an object file"
b. Using the VI.O

CREOL~

do the following:

CREOl
ADOM object_file "generated as above"
GENt vlO_.ibrary "version Vl.O object tibrary"
4. Previous versions of message template modules cannot be used by
the
Rl.l.2
system.
They
~ust
be
rebuilt
using
the
GENERATE_MESSAGE_TEMPLATE procedure. A MODULE statement must be
placed at the beginning and a ~ODEND statement at the end of the
message template definitions in order to provide the name for the
message template module on the DCU library. The message template
module should be placed on the same library as the program
description and eVBIl modules for the application program.
5. A new version (VI.l) of sauree code library format has been
implemented
to
support
current
and
future
performance
improvements.
It wi' I be necessary to convert al'alder (pre
Rl.l.Z) source libraries with a utillty described in Section 5.5.
6. Changes

to the program i,terface require the recompilatlon of all
modules.
Modules which have not been recompiled may
encounter 'declaration mismatch' errors when they are loaded. In
addition, any modules bound ~ith runtime libraries wilt have to be
rebound.

CrBIl

7. Tape usage is restricted
dump analyzer operations.

to permanent fite backup/restore, and

8. Rl.l.2 changes the operator i,terface to NOS/VE
from
the
combination of the K-dlsplay and MOO Interface to 9 single CDC
CC634B terminal connected via cable AVI17A to the mainframe's two
port multiplexor.
The ~OS/VF system console should be connected
to port 0 of the two port muttfolexor to allow RTA access via port
1.
The new NOS/VE system conso'~ orovides access to the operator
fac.lity, system core debugger, the refreshing displays under
VEDISPlAY, and an operator actions display. This console allows
use of fu'l ASCII for at. key-~~s.

A single CC6348 can
810/830

systems.

be used for both NOS and NOS/VE on
the model
However, only one operating system can use the

1-3

SOFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 lEVEL b30
1.0 INTRfJOUCTION

system console at a given instant. The f6 key must be used
switch ownership of the system consote between NOS and NOS/VE.

to

For al I other model 8xx mainframes supported by NOS/VE, the e170
state operating system ~il' continue to use the Ce545 consote and
NOS/VE Mil' use the CC634~ as its system console.
In several sections of this document. PSR numbers are given fo.Jowing a
problem description. Additional information about the problem may be
obtained from SOLVER by using this number.

SOFTWARE RELEASE BULLETIN

2-1
65/03/29

NOS/VE Rl.l.2 lEVEL 630
2.0 FEATURES AND PRODUCTS

The products associated with NO$IVE Rl.l.2 level 630 are documented in
detail
in the Software Availability Bu1letin. Please refer to that
document for this information.

3-1

SOFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630

3.0 INSTALLATION AND OPERATIONS NOTES

-----------------------------------------------------------------------:3. 1 IB~IALJ.A!ILlrJ

3.1.1 NOS INSTALLATION

1. 80th PASSON and IRHF must run out of the SYSTEMX account in order
to access NOS output queue files which are transmitted to the
NOS/VE input queue. If your site has changed the password of the
SYSTEMX user, then you must alter the USER statements in the
RUNJOBS procedure. Enter the following statements under the user
name from which NOS/VE is being deadstarted:
COMMON, SYSTEftl.
GTR,SYSTE",NVELr8,U.UlIB/~VELIB.

GETPRflC,RUNJOBS.
*Change all USER statement oasswords to your site's value
FSE;, RtlNJOt'S.

*NVer,t,. adds'OSTLI8 to the Ijbrarv set
REPPROC,RUNJ08S,l=DSTlIB.
*Change DSTlIB from semi-3rivate to private
CHANGE,OSTlIB/CT=P.
2. In

order to use the ST-NVE oaraneter to route a file to the input
queue, the user must have CUST validation 'lag set.

3. The NOS system must have a LID table defined containing a
NVE with a LID of NVE. Neither entry has attributes.

PIO

of

4. A skeleton file (ACCOUNT) is created during deadstart and used by
Interim Remote Host and Interstate Communications to generate
partner JOOS that are submitted to NOS. This file is created
~ithin a procedure named ACCFIlE which is located in user
library
NVEL lB.
Cur r en t I y ,
the ACe 0 1.J't r
f j l e e rea ted wi' I c on ta i nth e
followingl
&JOS.

US E R, &USE R, & PA:5 SwOR 0 • J

CHARGE,&CHARGE,&PROJECT.
IEOR

When an Interstate Communic~tions job (GETF, REPF, CREIe) is
executed, the partner job is created using the ACCOUNT file to set

3-2

SOfTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630
3.0 INSTALLATION AND OPERATIONS NaTES

3.1.1 HOS INSTALLATION

NOS accounting for the NOS batch job. The field '&JOB' causes
the Job card that was created withtn Interstate Communications to
be put in its place. The fields "USER', "PASSWORD', "CHARGE',
and t&PROJECT' are filled in with the accounting information
entered by the user when e.ecuting 9 SET_LINK_ATTRIBUTES command.
Interim Remote Host uses the ACCOUNT file In the same way.
UP

If the charge and project nu~bers were not specified on the
SET_lINK_ATTRISUTEScommand the characters '*.t are substituted
for '&CHARGE' and blanks for
'&PROJECr f •
This implies that
default charge wit' be used by NOS and the user must have the
correct charge and project numbers specified under MODVAl.
Changes can be made to the ACCOUNT fite so that a site may create
their own accounting fi Ie for Remote Host
and
Interstate
Communications Jobs.
a. Get the user library NVELI8 from the system in order to change the
ACCFILE procedure.
b. Extract the procedure ACCFILE' fro," NVELIB.

c. Modify the procedure defj,ed in this file by inserting the control
cards necessary for accounting vatid3tion.

d. Place the procedure onto 05TlI8.

REPPROC,ACCfILE,OSTLIB.
3.2

Anr nlE.E.t:B,'-tJ..-cs
Ri"'
"1"1
- ~
°1 L "l. L__
2 Ihl<:lAI
J ATlrhl"
A\ID
uprO
~ L
L. ___
~ Q~~~_
W~ __
~~ __
~~~Q~~_~
~ t~~~_

This

section

documents the differences between NOS/VE 1.1.1 and
It concentrates on the changes affecting those sites

NOs/ve 1.1.2.

which tailored:

1. system start up commands
2. system shut down com1ands
3. command libraries
4. system proloQs and eoilogs

according

to

(60463913B).

discussed.

the NOS/VE 1.1.1 Installation and Upgrade Manual
Reloading of oermane"t files at NOS/VE 1.1.2 is also

3-3

SOFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630

3.0 INSTALLATION AND OPERATIONS NOTES
3.2.1 SYSTEM START UP COMMANDS
3.2.1 SYSTEM START UP COMMANDS
Previously YOU modified record STlUC in the NOS file NVElIB.
At
1.1.2, you should place your syste~ start UP commands in the filet

This file is created only by an installation deadstart, with files
being reloaded from the REQUIRED tape (i.e., the first time you
install NOS /VE 1.1.2).
Examine the contents of $syste~.start_up_commands, and
to change the commands, simp"
overwrite this file
commands you want executed. Possible commands include:
1. set_default_family
2. set_Job_class_limits
3. set_command_' 1st (for'

the

jf

you want
with the

operator command list)

You may also wish to execute certain commands based on the type of
deadstart being performed. You can determine the type of deadstart
by testing
the value of the variabte ravS'oad_option, which may
have these values.

'INSTALL'

Installation deadstart was performed, the
value of set_flle_loaindQ_options was set
to instal'
(the default value for
an
i os t a' I at i () n de ads tar t ).

'RELOAD'

Installation
deadstart,
the
value of
set_fi'e_loadinQ_options was set to reload.

'NORMAL'

Continuation
deadstart,
the
value of
set_fite_IoadinQ_options was set to normal
(the
default value for a continuation
dea dst ~l"t).

'UPGRADE'

Continuation deadstart,
set_,jle_loadinQ_options
upgrade.

'INSTALL_DEFERREO_FIlES'Continuation

deadstart,

set_ftle_loaindg_options
install_deferred_flles.

was

set

of
to

the
was

value
set

of
to

the

value

3-4

SOFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 lEVEL 630

3.0 INSTALLATION AND OPERATIONS NnTES
3.2.2 SYSTEM SHUT DOWN COMMANDS
3.2.2 SYSTEM SHUT DOWN COMMANDS
At NOS/VE 1.1.1, this file was record SHUDC on the NOS file MVElIB.
The file
$system.shut_down_com~a~ds

is created the first time YOU instal' NOS/VE 1.1.2. Overwrite this
file with any commands yOti wish to be executed during system shut
down.

3.2.3 SITE COMMAND LIBRARY
At NOS/VE 1.1.1, the fi'e
Ssystem.osfSsite_command_library
was created from record 1SFSCl on the NOS file NVELI8. Any
procedures you wished users to have as part of their command lists
could be placed in this file, as i t was added by the system prolog
to users' command lists.
This file is now reserved for CDC, and the system is released such
that this fie is no longer automaticajly added to users' command
, j s ts.
Procedures YOU want to make acces$ible to your users should be
placed on another command library. and the system prolog should be
modified appropriately (see belo~).

3.2.4 OPERATOR COMMAND LIBRARY

At NOS/Ve 1.1.1, the fi Ie
$system.osf$operator_comm~nd_IJbrary

was created from record OSFOCl on the NOS file MVElIB.
Any
procedures you wished Y3ur operators to have as part of their
command lists could be placed in this fi'e, as It was part of the
operator's command list.
Th j s f i • e
is
n 0 PI
res e r v'e d
operator's command list.

for

CDC,

but

it

is

still

in the

Procedures you want to make accessible to your operators should be
placed on another command Ilbr~ry, and the system start up commands
(see above) should be modified appropriately to also add your
operator command library to the ooerator's command list.
Should

you

have

tibrary witt not be

to reload per~a"ent files, your operator command
available until
files are reloaded.
This

3-5

SOFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630

3.0 INSTALLATION AND OPERATIONS NOTES
3.2.4 OPERATOR COMMAND LIBRARY
should not bea problem, unless yoU want to use a restore procedure
different from the one supplied by CDC. In this case, place your
procedure on the NOS file SITECP (Just like the CDC restore
procedure) and rebuild your deadstart flte with REPRECS. This
procedure will then be made a permanent file under SSYSTEM for any
installation deadstarts.

3.2.5 SYSTeM PRDlOGS AND EPILOGS
At NOS/ve 1.1.1, the

syste~

prolog executed commands which added:

1. $system.scu.maintenance.command_library
2. $system.osfSsite_comm~nd_library
The released system protog no lo~ger contains these commands.
Also, the first library has bee" renamed to:
$system.scu.command_'ibrarv
If you want to add these (or other)
libraries to users' command
lists, create a newc.Ycte of the file
$system.prologs_snd_epl'oQs.system_pro'og
and include commands to add these libraries to the user's command
tis t.

3.2.6 RELOADING FILES
Perform the following steps if

yoU

have to

reload

your

permanent

f i I e bas e.

1. Execute

an installation 1eadst3~t, but using a NVE procedure
file which pauses for operat3r system core commands.
Enter
the system core commandsl
initdd 111111
GO

Note that the GO must be uopercase, and you do not enter the
auto system core command.
2. Deadstart wilt eventual., pause with
options disP'ay. Enterl

the

set

set_file_loadin9_option toad_option=reJoad
GO

fite

loading

3-6

SOFTWARE RELEASE BULLETIN

85/03/29

NOS/ve Rl.l.2 LEVEL 630

3.0 INSTALLATION AND OPERATIONS NaTES
3.2.6 RELOADING FILES
3. After deadstart completes, execute the permanent rite
procedure.
attach_file
restore

reload

$Syste~.restGre

Note that if you write your own
procedure (see the ]perator Command
would attach your procedure instead.

permanent file reload
Library section) you

4. After files are reloaded, enterl
create_family nwe 'administrator-user-name'
include_file Ssyste~.start_up_commands

3-7

SOFTWARE RELEASE BULLETIN
85/0312.9

NOS/VE Rl.l.2 lEVEL 630

3.0 INSTALLATION AND OPERATIONS NOTES
3.2.1 NOS/VE INSTALLATION
3.2.1 NOS/VE INSTALLATION
1. Table 1-1 and 2-2 of the ~OS/VE Inst~ltation and Upgrade Manual
should be expanded to include the larger memories supported by
release 1.1.2. The expanded table is shown betow:
C.H
SI ZE

eM

1 M3
Z Mil
3 fiB
It 1'16
5 MB
6 "3
7 MS
8 MB
9 tiS
10 MB

4000000
10000000
14000000
20000000
24000000
30000000
34000000
40000000
44000000
50000000
54000000
60000000
64000000
10000000
74000000
100000000
lO400000(}
110000000
114000000
1.20000000
124000000
130000000
1·34000000
140000000
144000000
150000000
154000000
160000000

11 MB
12 MB
13 MB

14 MS
15 MB
16 M8

17 MB

18 MB
19 MS

20
21
22
23
24
25

MB
M8

MB
M8
118

MB

'26 H8

27

Me

MB
MB
30 MB
31 MS
32 MB
28
29

WORD S

(OCTAL)

164000000
170000000
174000000
200000000

M WORO S
(OECI!1Al)

eM

WORDS

(HE Xl

131072
2&2144
393216

20000
40000
60000

524288
65536J

800000
OAOOOO
OC:OOOO

786432

91 15t)4
1048516
111q6~8

1310720
1441792
157286 ·4
11039':J6
18350)8
1966080
209115:2
22 .2a2~lt

OEOOOO
100000
120000
140000
160000
180000

l'AOOOO
lCOOOO
1£0000
·2000i)0
2'-0000

2490:368
2621440

240000
260000
280000

2152512

2~OOOO

2359296

2883534

2COOOO

3014656
314:5'728
3276800
340787 ~

2E;)OOO
300000
320000
340000
360000
380000

3538944

3670016
3801088
39 321!l 0
4063232

3AOOOO
3COOOO
3EOOOO

4194304

400000

eM

BYTES
(DECIMAL)
1048576
2097152
31't5728
4194304
5242880
6291456
7340032
6388608

eM

BYTeS
(HE X)

100000
200000
300000
400000
500000
60·0000
700000
800000

9431184

QOOOOO

10485700
115:34336

OAOOOOO

0800000

12582912

OCOOOOO

13631488
14680064
15728640
16777216
17825192
18874368
19922944
20971520
220200Q6
23068672

0000000

24111248

1700000

25165824

1800000
1900000

26214400
27262916
28311552
29360128
30408704
31457280
32505856
33554432

OEOOOOO
OFOOOOO
1000000
1100000
1200000
1300000
1400000
1500000
1600000

1AOOOOO
1800000

lCOOOOO
1000000

lEOOOOO
IFOOOOO
2000000

2. When upgrading from an earlier NDS/VE release to NOS/VE Release
l.l.~
YOU
must backup your existing NOS/VE permanent files,
deadstart NOS/VE Release 1.1.2, and restore your NOS/VE permanent

3-8

SOfTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630

3.0 INSTALLATION AND OPERATIONS NOTE5
3.2.7 NOS/VE INSTALLATION
files. System and product fites cOAtained on your permanent file
backup tapes may have higher cycle numbers than those installed at
NOS/VE Release 1.1.2.

Res·tarlng fites into

the$SYSTEM

catalog

from your existing permanent flte backup tapes can result in a
mixture of old and new installed versions, since the highest cycle
is used by default as the installed version. If your permanent
f i I e backup tapes gl1 __ 11~t con t a in
$SYSTEi*1 cat a log
files, then
follow
the
instructio1S
outlined
in chapter two of the
Installation and Upgrade manual
(publication number 60463913).
The following steps descrlbe how to upgrade to NOS/VE Release
1.1.2 from an earlier ~nS/VE release, and how to reconcile
differences between old SAd new SSYSTEM fites:
a. Once you have generated the NOS/VE Release 1.1.2 Deadstart
Input file as descri~ed in chapter two of the Installation
and Upgrade manual, enter the following command from the
operator console to terminate your current NOS/VE system:
TEIU1 INATE_S YSTEM
b. Deadstart NOS 2.4.1 level 630 or NOS/BE 1.5 leve' 627 and
NOS/VE Release 1.1.2. Se sure to use a deadstart procedure
fife for NOS/VE that enables operator intervention prior
to
system
core
com~and
orocessing.
Refer to the SETVE
procedure documentation in the Installation and Upgrade
manual when creating this deadstart procedure file.
c. When "ENTER SYSTEM CaRE COMMANDS" appears on the operator
con so. e, en t e r :
INITOD  ffwhere  and
SWAPIN  is the system job name of the job to be swapped.

3-21

SOfTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 lEVEL 630
~~-.-.-- ....
....----.- .... ......~..-..-.-~..-..------ ....
3.0 INSTALLATION AND OPERATIONS MOTES

-.----.--

'--"-------'--'-'''----------.....---...

.---

3.4 OPERATOR CO"MANDS
..-..-.

...-.....-.--.-.-........--- ...---.........

-

.... ......-,- .....

---.-----.-~----.-

.--

..... ----.--.---~

.-- .....-~------.--~-------

...--- ... ----.-.-............----:--...-.- ........--.-..•~-

If the job is to be swapped in, uslng the OISSJ command Hill
provide the JSN necessar~ for the SWAPIN command. When a Job is
swapped out using the SWAPOtJf command, i t wi I t remain swapped
out
until the S~APIN co~mand.is executed.
11. When an operator makes 30 error on an ASSIGN_DEVICE (ASSD)
command, the tape request message will be replaced by an error
message.
The operator should acknowledge the error by entering
the REPLY_ACTION (REPAl command with the appropriate Job name.
The error message wi" be cleared. and the original tape request
message wi
reappearJ allowing the ASSIGN_DEVICE to be retried.

I.

3-22

SOfTWARE RELEASE BULLETIN

85103/29

NOS/VE Rl.l.2 lEVEL 630

3.0 INSTALLATION AND OPERATIONS NOTES
3.5 CONFIGURATION MANAGEMENT

1. The physicat and logical configuration
invoked by name from the system cnnsole.
the EXECUTE_TASK command as sho~n here:

utilities can only be
All other users must use

2. The name ALL is a reserved element name and should not be used
any element defi~itions.
3. When

running

the

Physical

interactive termin.al, the

in

Configuration

include_file

Utility (PCU) from an
command wilt
return an

error stating that the included ftle is not callable. In order to
test the configuration, e~ter the PCU, then copy the test file to
another tocal file. You no'. can include_file the new local file.
number uniqueness is now enforced by
the
Physical
Configuration
Utility_
When
defining
elements
in
the
configuration prolog, care must be taken to specify a unique
seri al number for each element. The only exception to this i s fo r
!1l u I t i -sp i n die devices such as Ba5-Ix.

4. Serial

5. For 830 dual CPU installation to run NOS/VE duat CPU, when "ENTER
SYSTEM CORE COMMANDS" aopears on the NOS/VE operator console,
enter the followingS
SETSA ENABlE_MULTIPRJCESSING 1
This command is temporary and
b. NOS/VE cannot run on CPU

0

messages are not Included in the diagnostic

--ERROR--THE ACTIVE LOGICAL
Product Identifier:
Condition Identifjer:

be removed in 1.1.3.

1 of a dual CPU configuration if CPU

is off or down.

1. The following error
manual for Rl.l.Z:

~Itl

C~

CO~FIGURATION

IS EMPTY.

coodition: 350410
Ci'1E$LCM_EM?TY _LC

Descriptionl The logical configuration was defined
physical configuration In the configuration prolog.

before

the

3-23

SOFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 lEVEL 630

3.0 INSTALLATION AND OPERATIONS NOTES
3.5 CONFIGURATION MANAGEMENT
User Action: Define' the
physical
configuration
configuration
prolog
before
you
define
the
configuration.
--ERROR--INCOMPATIBlE LOGICAL
Product Identifier:
Condition Identifier:

C~

CO~FIGURATION

in
the
logical

FILE.

c3ndttion: 350405
CMESlCM_INCOMPATIBlE_LC

Description: Encountered an internal file problem.
User Action! Reexecute the logical
configuration utility.
If
the error reoccurs, execute both the physical and logical
configuration utilities to define the physical and logica'
configurations.
If the error persists, contact Control Data
field support

--ERROR--PERMISSION NOT
Product Identifier:
Condition Identifier:

GRA~TED
C~

FOR {text}.

condition: 350430
CMe$lC~_RING_VALIDATION_ERROR

Description: User does 10t have rlng privilage
program interfaces or command.
User Action: Request
family administrator.

the

--ERROR--{text} MISSING

I~

Product Identifier:
Condition Identifier:

eM

to

execute

the

aooropriate ring privilege from the

P~YSICAL

ADDRESS SPECIFIER SET.

condition: 350435
CMESlCM_MISSING_PA_SET_MEM8ER

Description: Missing required set value in the physical
specifier set.

address

User Action: Specify the appropriate set value In the physical
specifier, I.e. to query controller name. you need to specify
cmc$channel and cmc$channel_address on the physical address
specifier set.

--ERROR--{text}
Product Identifier:
Condition Identifier:

eM

condition. 350455

CMESLCM_NOT_AVAILABlE

3-24

SOFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630
3.0 INSTALLATION AND OPERATIONS NOTES
3.5 CONFIGURATION MANAGEMENT
Description:
implemented.

User

User Action: Contact

is

tryi~g

Co~trol

to

use

a

feature

not

yet

Data Central Software Support.

1. If any disk volume being used by NOS/VE becomes full, the
following message wil. per'iod,cally appear on the console:

AAAAAA - out of space (date) (time)
(AAAAAA is the vsn of the volume)
Any task that Is re'questing space

on

a

full

yolume

wi t I

hang

waiting for space. Some space may be obtained by asking users (if
they are able) to delete permanent files and detach joca'
files.
If the disk futl condition persists, the NOS/VE system should be
taken down and brought back UP. This action will release most of
the temporary 'ile space that was in use. If the disk full was
caused by permanent files, then the disk witl be nearly full after
the recovery, and the archiving of permanent files or deleting of
some files must be done as soon as the system Is up.
It is possible that a disk full situation will occur that cannot
be recovered.
This wi"
ha,e happened if the "out of space"
message appears during a deadstart before the system is UP (this
usual.y will occur during the permanent file reorganization phase
of deadstart -- recognized by the up' recovery" message at the
console). In this case permanent file volumes must be initialized
and reloaded from a previous backup dump.
2. If a continuation deadstart fails after disk fu11

with a NOS/VE
CPU monitor fault,
it is possible that the failure is due to
unprinted files in the output queue, one or more of which are no
'onger printable. The failure is a job mode software failure and
does not leave the Monitor Control ~egister set in monitor mode.
The message indicating this failure is "HR - MONITOR FAULT".
Remedial action'
a continuation deadstart (with W=TRUE so you can enter
system core commands) and e~ter the following system core command:

Perfor~

3-25

SOFTWARE RELEASE BULLETIN
85/03129

NOS/VE Rl.l.2 lEVEL 630
3.0 INSTALLATION AND OPERATIONS NOTES
3.6 DEVICE MANAGEMENT/RECOVERY
This command wi' I allow deadst3rt to complete.. If you find that
task RHOUTPUT has terminated (by looking at the system Job log
with DISSl), and files exist in the Job output queue (DISC
SSYSTEM.SJDB_OUTPUT_QUEUE) you can be reasonably sure that YOU
have encountered this problem.

Delete
the
contents
of
SSYSTEM.SJOB_OUTPUT_QUEUE),
continuation deadstart.

the

Job

ter~inate

1. The power of the family administrator has been extended
backing UP and deleting fioles for users in his family.

The data that gets emitted
faults for the task that calls
a task, then the data for that
and the command statistic wit'
for the initiating task.

(DELee
another

output
queue
NOS/VE, and do

to

allow

for this statistic is the time and page
the command. If the command spins off
task is found under the task statistics
only contain the time and page faults

Statistic

Name

Oescr:i ptjon

-----------------------------------------------------------------CIL1002

Command Resources. This statistic wit.
co.lect and generate data for every command
executed. It should only be used for testing
or perfor.ance fnformation gathering.

The information generated by this statistic
includes'
DESCRIPTIVE DATA - command name
COUNTER 1 - Job ~ode CP time
COUNTER ? ~ monitor mode CP time
COUNTER 1 ~ tot~, page faults
COUNTER 4 - tot31 page-Ins
COUNTER 5 - total page-reclaims
COUNTER ~ - tot~, page-assigns

3-26

SOFTWARE RELEASE BULLETIN
85/03129

NOS/VE Rl.l.2 lEVEL 630
3.0 INSTALLATION AND OPERATIONS NOTES
3.8 COMMAND LANGUAGE STATISTIC
Due to the large overhead incurred by using this statistic,
conditional and must be activated to the following manner.

it

is

FROM THE CONSOLE ENTERI
seTSA COMMAND_STATISTICS_ENABLED TRUE
ACTS Cl170002

To deactivate the statistic, use the opposite of the above sequence.
DEAS CL170002

SETSA COMMAND_STATISTICS_ENABLED FALSE

1. The installation and upgrade of online manuals is documented in
the NQS/VE Installation and Upgrade Usage Manual for Release
1.1.2. The maintenance process is described in this section.

The source for online manuals is being distributed to allow
customers the capability of tailoring the manuals for their site.
Source libraries contain a SCU feature reflecting t~e revision
level documentation changes (example: feature VER_l_l_l
for
Release 1.1.11 This not only gives the benefit of a "revision
packet" to identify new cgp3bilities and changes, but also aids
the update process for the site version of manuals.
To tai lor a manual fora s i tel
a. Create

a

new

source

library

or

additional cycle of
reflecting
the

Ssystem~manuals.malntena,ce.$ource_library
site modjfjcations.~ (Note that each manual
a deck- Decks are gr~uped by product.)

is contained in

b. Execute $system.ma~uals.maintenance.bindtng_procedure within
the $system user or maintenance user name to create new
manualS.

PROC bind_manua.s, bin~, bind_manual
manua., manuals, ~: LIST OF NAME or KEY all • al I
source_catalog, set ~ILE = 'SYSTEM.MANUALS.MAINTENANCE
catalog, Cl FILE • SUSE~.MANUALS
status)
where,

3-27

SOFTWARE RELEASE BULLETIN
85/0312.9

NOS/VE Rl.l.2 lEVEL 630

3.0 INSTALLATION AND OPERATIONS NOTES
3.9 ONLINE MANUALS
manual

lit

seu

deckname(s)

of

manual(s)

desired

to

be

created
contains the source libraries
compilation
catalog == resultant catalog for new manual(s)

source~catalog

used for

The following diagnostjc messages have not been included in NOS/VE
manuals for Rl.l.2. They will be included in a future release.

3.10.1 PASSON DIAGNOSTI(

"ESSAGE~

There are 28 distinct errors that PASSON indicates by issuing a
'PASSON ABNORMAL' message at its control point.
The cause of each
error and its associated error code (issued in the ,'PASSON ABNORMAL'
message) are listed below. The error explanations assume a knowledge
of the network concepts evinced in the NAM/CCP Reference Manual
(publication number 60499500).
1. PASSON ABNORMAL 0
PASSON's attempt to sign on to the memory link failed with a fatal
error status. PASSON ter~inates.
2. PASSON ABNORMAL 1
The memory link reported a fatal error status when PASSON
attempted an mtpSadd_sender to permit itself to receive messages
from any NOS/VE application. PASSON terminates.
3. PASSON ABNORMAL 2
PASSON does not begin interactive processing until NOS/Vets
Interactive Facility's executive signals it to do so.
In this
case, the memory link reports a ratal error status while PASSON is
awaiting the executive's signal. P4SS0N terminates.
4. PASSON ABNORMAL 3
An attempt to activate network message logging has failed
the logging code is not available. PASSON terminates.
5. PASSON ABNORMAL 4

because

3-28

SOFTWARE RELEAse BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630
3.0 INSTALLATION AND OPERATIONS NOTES
3.10.1 PASSON DIAGNOSTIC MESSAGE~
An attempt to activate network statistics accumulation has
because the statistics accumulation code is not aVli 'able.
terminates.

faited

PASSON

6. PASSON ABNORMAL 5
The memory link reported g ratal error status when PASSON
attempted to receive a dowAJlne message from NOS/VE. PASSON
issues the abnormal message 30d continues Interactive processing.

7. PASSON ABNORMAL 6
After receiving a message from ~OS/VE, PASSON has discovered that
the message is neither a data message nar a supervisory message
(the only 2 possibilities f~r application messages). PASSON
issues the abnormal message and continues interactive processing.

8. PASSON ABNORMAL 7
HAM has signaled to PASSON (via the supervisory status word) that
an upltne supervisory message is available to relay to NOS/VE, but
PASSON ascertains that the message is not a supervisory message.
PASSON issues the abnor~al message and continues interactive
pr o-cess i ng.

9. PASSON ABNQRMAl 8
Not used.

10. PASSON ABNORMAL 9
PASSON has received a connection request supervisory message
(CON/REQ/R) from NAH for a connection which is already in use.
The connection request is iq~ored. PASSON issues the abnormal
message and continues Jnter~ctive processing.

11. PASSON ABNORMAL 10
PASSON has received an injtialized-eonnectioo (EC/INIT/N) or an
initialized-connection request (FC/INIT/R) supervisory message
from NOS/VE or HAM, respectivel,. and the connection receiving the
message is not at the appropriate stage of the connection
initialization sequence. PASSON olaces a connection in a state of
~ajtln~
for an FC/INIT/R (~'ter a CON/REQ/N) or an Fe/INtT/N
(after an FC/INIT/R). In this case the connection Is not in the

3-29

SOFTWARE RELEASE BULLETIN
85/0312.9

NOS/VE Rl.l.2 lEVEL 630
3.0 INSTALLATION AND OPERATIONS NOTES
3.10.1 PASSON DIAGNOSTIC "ESSAGE~
wait state when the FC/I~IT/R or Fe/INIT/N is received.
The
message is ignored (which ~il' hang an uninitialized connection)
and PASSON continues interactive processing after issuing the
abnormal message.
12. PASSON ABNORMAL 11

PASSON
has received a net~ork shutdown supervisory message
(SHUT/INSO/R) from HAM indicating that NAM shutdown is
in
progress.
PASSON terminates immediately if the shutdown is
immediate, otherwise the shutdown message is relayed to NOS/VE and
PASSON continues interactive orocesslng after i t issues the
abnormal message.
13. PASSON ABNORMAL 12

A supervisory message has be~n received by PASSON fromNAM that is
not in the list of supervisory messages which PASSON can recognize
and receive from NAM. The message is ignored, PASSON issues the
abnormal message and continues interactive processing.

14. PASSON ABNORMAL 13
The status of PASSON is

nor~al

and processing continues.

15. PASSON ABNORMAL 14
The memory link reported a fatal error status when PASSON
attempted to send a queued uoline supervisory message to NOS/VE.
The
message
is not sent and PASSON continues interactive
processing after issuing the abnormal message.

lb. PASSON ABNORMAL 15
The memory link reported a fatat error status when PASSON
attempted to send an up.ine supervisory message to NOS/Ve that was
not queued.
The message is not sent and PASSON continues
interactive processing after is.ulng the abnormal message.

17. PASSON ABNORMAL 16
PASSON tried to send a suoervisory message from NAM to NOS/VE but
had to queue the message for later transmission, .but there Mas no
allocatable space to queue the ~essage. The message is oot sent
and PASSON continues interactive Dfocessing after issuing the

3-30

SOFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630
3.0 INSTALLATION AND OPERATIONS NaTES
3.1D.1 PASSON DIAGNOSTIC MESSAGES
abnormal message.

18. PASSON A8NDRMAl 17
The memory link reported a fatal error status when PASSON
attempted to send a queued upJine data message to NOS/VE. The
message is not sent and PASSON continues interactive processing
after i-ssuing the abnormal- m-ess.age.
19. PASSON ABNORMAL 18
The memory link reported a fatal error status when PASSON
attempted to send an up'ine data message to NOS/VE.
The message
is not sent and PASSO~ continues interactive processing after
issuing the abnormal mes_sa:ge.'

20. PASSDN ABNORMAL 19
PASSON has received a connection-TeJected supervisory message
(CON/REQ/A) from NOS/VE for a connection which was not in the wait
state for a CON/REQ/N. PASSa~ places a connection in a state of
waiting for a CON/REQ/N after the connection has sent a CON/REQ/R
upline to NOS/VE. The co,nection Is ended and PASSON continues
interactive processing after issuing the abnormal message.

21. PASSON ABNORMAL 20
PASSON

has

received

a

co~nection

accepted supervisory message

( C ON IRE Q IN) from NOS/VE for a connection which was not in the wait

state for
waiting for
\,J.p' i ne
to
interactive

a CON/REQ/M. PASSON places a connection in a state of
a CON/REalM aFter the connection has sent a CON/REQ/R
The connection Is ended and PASSON continues
NOS/VE.
pro cess j og aft er i s~u i n-g the abnorma I message.

22. PASSON ABNORMAL 21
PASSON has received a supervisory message from
interactive processing. PASSON terminates.

NOS/VE

to

stop

23. PASSON ABNORMAL 22
PASSON has received a supervisory message from NOS/VE which is not
in the. 1st of supervisory messages ~hich PASSON recognizes and
can receive from NOS/VE.
The message Is ignored and PASSON
continues interactive prbcessing after tssuing the
abnormal

3-31

SOFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 lEVEL 630
3.0 INSTALLATION AND OPERATIONS NOTES
3.10.1 PASSON DIAGNOSTIC MESSAGE,S

24. PASSON ABNORMAL 23
Not u.sed.

25. PASSON. ABNORMAL 24
PASSON has received a data message from NAM whose message header
has the ibu (input block u~detiverab'e) bit set. The message is
not sent to NOS/VE and PASSO~ contlnutes Interactive processing
after issuing the abnormal ~ess~ge.

26. PASSON ABNORMAL 25
PASSON has received a supervisory message from HAM whose message
header has the ibu (input block undeliverable) bit set.
The
message is not sent to NOS/VE and PASSON continues interactive
processing after issuing the abnormal message.

27. PASSON ABNORMAL 26
The memory link reported a fatal
error status when PASSON
attempted to send a message (data, supervisory, queued data or
queued supervisory) to a ~05/Ve application not signed on to the
memory link.
The message is not sent to NOS/VE and PASSON
continues interactive processing after issuing the
abnormal
mess age.

28. PASSON ABNORMAL 27
PASSON
has
received
~n
error-logical supervisory message
(ERR/LGL/R) from NAM for a connection. The message is reported to
the Job dayfile for the connection and then relayed to the
connection's associated NJS/VE application.
After issuing the
abnormal message PASSON continues Interactive processing.

3.10.2 MEMORY LINK FATAL ERROR CODES
'fatal memory link error codes are' i sted below wi thcorresponding
descriptions. Those error codes not fisted are not fatal errors.

The

1. MEMORY LINK FATAL ERROR 1
This status value indicates

that

the

application

name

of

the

3-32

SOFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 lEVEL 630
3.0 INSTALLATION AND OPERATIONS NOTES
3.10.2 MEMORY LINK fATAL ERROR CODES
receiver is not valid. Currentl"
The request is ignored.

the only invalid value

is

-1.

2. MEMORY LINK FATAL ERROR Z
This status value indic~tes that the
sender Is not valid. Currentt" the only
The request is ignored.

application name of the
i nv a' I d
va' u e i s ·-1 •

3. MEMORY LINK FATAL ERROR 3
This status va'ue indicates tbat the receiver application is not
currently signed on to "LI. The request is Ignored.

4. MEMORY LINK FATAL ERROR 4
This status va.ue indicates that the application name specified is
signed on to "LI, but by a different task than the one making the
r e 
[output-(file reference)]
[status=(status variable)]

command: ct This parameter specifies the command for which
about par ameters is sought.;

Information

output : ot ThiS parameter soeclfies the flle to which the parameter
information is written. O~lsslon wilt cause SOUTPUT to be used.
status: This is the standard status

oar~meter.

4-6

SOFTWARE RELEASE BUlLfTIN
85/03/29

NOS/VE Rl.l.2 lEVEL 630
4.0 OPERATING SYSTEM NOTES AND :AUr!O~S
4.1.1.2 DISPLAY_COMMAND_LIST (OISCl)

This command displays the names of the entries in and/of the search mode
governing the command 'ist.
display_command_tist [djsP'ay_options=list of atl
entries:entry:e : search_modetsml
[output-: all:

contro'_statements:cootrol_statement:cs :
first:f]

Cdisplay_options=Jist of all: all_names:al.name:an
commands:command:c :. functions:function:f

nameslname:nl
[output-]

command 'ist

4-7

SOFTWARE RELEASE BULLETIN

85/03/2.9

NOS/VE Rl.l.2 lEVEL 630
4.0 OPERATING SYSTEM NOTES AND :~UTrONS
4.1.1.3 DISPLAY_COMMAND_LIST_ENTRY(IESI (OISClE)
[status= ::: SCOMMAND_SDURCE

[«)

(})]

Example: "The following proc resides on an"
"object library in some catalog."
PROC sample_command
cs : $command_source
cat • SpathCSfname(cs), catalog'
"The following command executes file"
"sample_program in the sa~e catalog"
execute_task Stname(catJI'.sample_program')
PROCENO

This function is used to obtain the
command.

ca~pletion

($previous_status> ::= SPREVIOUS_STATUS t(C)

status

of

the

previous

(»]

Example: collect_text display_status
PROC display_status, diss (
status: status = ,previous_status)
display_value Svatue(status)
PROCEND display_status

**
create_variable

s klnd=status
create_variable x status4s

displ ay._status

NORMAL STATUS
create_variable x status=s
di.spt ay_status

--ERROR-- X is already declared as a variable.
there
are
certain
status conditions that do not
$PREVIOUS_STATUS to return the expected value. Among these are
from control or assignment statement and "xxx is not a command".
PSR NVOF077

~Qt~:

This function is used to quote


~

string.

(string exor) ()

cause
error

4-11

SQFTWARE RELEASE BULLETIN

85/03/29

MOS/VE Rl.l.2 LEVEL 630
4.0 OPERATING SYSTEM NOTES AND CAUTIONS
4.1.2.3 $QUOTE
Example: s • 'ASC"OEF'
q :: $quote(s}
display_value s

ABC'DEf

display_value q
'ABC"DEF'

4 .1.:2. 4!S.t.Ali_Ati!

This function is used to search a string for anyone of a set of
characters and return the index in the string of the found character.
If no character from the set apoears in the string, zero is returned.
<$scaA~any>





(J:sP)



<»



= '0123456789'

s= 'rE MP _32 •

display_value Sscan_anytdlgits, s)

6

This function is used to search a string for any character that is not
in a set of 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.
<$scan_not_any)

:,=

SSCAN_NOT_ANY

«) (char set> <,Isp)
 <»

 (pattern) <,:sp)
(string expr> <»

 :1= 

SI-

STRANSLATE

«>



table> <,:sp)

<»

 :s= 
: LOWER_TJ_UPPER : lTU

: UPPER_TO_LOWER : UTL
Example: display_value StranslateCfower_to_upper, 'l23_abc')
123_ABC

4-13

SOfTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630
4.0 OPERATING SYSTEM NOTES AND
4.1.2.8 $TRIM

:~UTIONS

This function is used to remove trailing space characters from a string.
(Strim>

:1:

STRIM

«>



display_value '(I//Strim(slll')'



II·

PUSH_COMMANDS

The purpose of this statement is t? cause the source (file or catalog)
of the issuing command to be pu;hed onto the top of the "dynamic command
list".
The entries in the dy~a~ic command list are searched after the
commands belonging to any active utitities and before the command list
entries manipulated by the SET_CDMMAND_LIST command. The effect of this
statement is removed (popped) when tbe issuing command terminates.

4.1.4 ADDITION CVBll PROGRAM

INTERFAC~S

(NOT IN MANUALS)

The purpose of this request is to replace an entire record.
This
request Is val id only for lass storage fi les opened for sequential
record access. The file position must be at the end of the record to be
replaced. The file position remains at the end of the record replaced.
The length of the replacement record must be identical to the length of
the previous record for a file whose record-type is CDC-variable (V).
Note the length of the previous record is exclusive of V record-headers,
i.e.
only the logica. length of the records must be identical.
Therefore, a record output with a series of partial PUTs can be
replaced.
For a file whose record-type is ANSI-fixed (f), the
replacement record will be truncated to maximum-record-Iength, if the
replacement record exceeds ma.imu~-record-Iength.
The length of the
replacement
record
must
be
less
than
or
equal
to
the
maximum-btock~'ength
for a fite whose record-type is undefined (ut and

4-14

SOfTWARE RELEASE BULLETIN
85/fJ3129

NOSJVE Rl.l.2 LEVEL 630
4.0 OPERATING SYSTEM NOTES AND CAUTIQ~S
4.1.4.1 AMP$REPLACE_PREVIOUS_RS:ORD
whose block-type is user-specifi~d. Note that a record deleted by an
ampSdelete_prevlous_record request cannot be replaced because one cannot
position to the end of a deleted record. This request is not supported
for
a rile whose record-type is undefined (U) and whose block-type is
sYstem-specified.
This request requires 'modify· access to the file.

fORMAT:
AMP$REPlACE_PREVIOUS_RECORO
~DRKING_STORAGE_AREA,

WORKI~G_STaRAGE_lENGTH,

(FILE_IDENTIFIER,
STATUS)

fILE_IDENTIFIER:
(input) This parameter specifies the file access
jdentifier established when the file was opened.

WORKING_STORAGE_AREA: (input) This parameter specifies the address of
the record which is to replace an existing record of the file.
WORKING_STORAGE_LENGTH: (in~ut)
of the record to be output.
STATUSt

This parameter specifies the length

(output) This parameter soecffles the request status.

condition identifiers:
ameSring_validation_error,
ame$jmproper_'lle_id,
ameSimprope,_access_attempt,
ame$lmproper_ws'_value,
ame$improper_file_position,
ameSunrecovered_write_error,
ameSfi le_organi zation_confl let.
ame$improper_device_class,
ameSconflictinQ_access_lewel,
ameSrecord_exceeds_mbl,
ame$record_unequa._to_prevlous,
ame$unsupported_operatlon;
procedure declarationa
PROCEDURE [XREFl ampSreplace_prevlous_record (file_identifier'
amt$file_identifier;
working_storage_areal Acetl;
working_storage_lengthl amtSworking_storage_lengthJ
VAR status: ost$status);
.

4-15

SOFTWARE RELEASE BULLETIN
65/03/29

NOS/VE Rl.l.2 lEVEL 630
4.0 OPERATING SYSTEM NOTES AND CAUTI0~S
4.1.4.1 AMPSREPlACE_PREVIOUS_Re:ORD
11 PUSH (LISTEXT s- ON) 11
*copyc AMTSfIlE_IDENTIFIER
*copyc AMTSWORKING_STORAGE_1ENGTH
*COPYC OSTsSTATUS
*copyc AMCSCONDITION_CODE_LIMITS
*copyc AMESCONFLICTING_ACCeSS_1EVEL
*copyc AME$IMPROPER_FILE_ID
*copyc AMESPUT_VALIDATIDN_ERRQRS
*copyc AMESTERMINAL_VAlIDATION_ERRORS
.copyc AMESRING_VALIDATION_ERRO~S
.COpyc AMESIMPROPER_WSl
.copyc AME$PUT_PROGRAM_ACTIONS
11 POP 11

1. Loading files into multiple
attributes to be assigned.
PSR NVOC789

rings

may

cause

improper

ring

2. The load time for large programs is too high.
Solution: Pre-linked object

~odules.

large pro9rams take a tong timed to load. Analysis sho~s the
loader spending much of its time building addresses in static data
sections. This is especially true In large FORTRAN programs.
A
process of "Pre-link~nq" has been created to completely
eliminate the time spent in the loader building stati~ addresses.
A bound program and its destination ring brackets are given to the
virtual environment tinker (lI~VE) which pre-links the product
using a set of reserved segment numbers. All addresses in static
data secti~ns are built a~d stored with the static data for the
section.
This data can be simplY copied at load time into its
reserved segment.
The output of the linker is a single object module which can be
ptaced on an object .tbr~r, and/or executed. The Object Code
utilities handle this·ne~ ~odu'e as i t would any other object
modu, e.

All

OCU commands may be used wi th a upre-I inked" module.

4-16

SOfTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 lEVEL 630

4.0 OPERATING SYSTEM NOTES AND CAUTIONS
4.2 PRDGRAM MANAGEMENT
I

'link_virtual_environment
VEl/set_link_options mode=PRODUCT
VEl/add_obJect_file file=~OUND_PRODUCT ring_brackets:(ll,1l,ll)
VEl/generate_virtuat_memorj virtual_image=PRE_lINKED_PRODUCT
VEL/quit
I

Icreate_obJect_library
COL/add_module library=PRE_lINKED_PROOUCT
COL/generate_'ibrary library-PRODUCT_LIBRARY
COL/quit
I
I execut e._t ask

SP=PRODUCT_INTRY_~OINT

/execute_task

sp·PRODUCT_~NTRY_POINT

file=PRE_lINKED_PRODUCT
library·PRODUCT_LIBRARY

I

Care must be usedwnen bui Idi l'lf.Jprograms that are made UP of
multiple "pre-tinked" modules.
AI. pre-defined segment numbers
must be unique for the entire load sequence. The STARTING_SEGMENT
parameter on the linker command SET_lINK_OPTIONS can be used to
specify the first reserved segment number for a module.
This
parameter allows modules that have been "pre-linked" separately to
be used together at execution time.
By default, the first
reserved segment number is currently 36.
The operating system reserves segments 36 to 63 for "pre-linked"
products. Each product m~st fit into these segments.
linker
directives can be used to collect sections with simi lar attributes
into one segment to reduce t~e total number of segments.

With the current implement~tion, sporatic initialization
of
read/write data wil'
i,~rease
both fi'e space and load time.
During the coding and binding of a program, efforts should be made
to collect al' initialized data together near the beginning of a
segment.
A warning diagnostic is issued if the linker finds a text imbedded
library that has not been specified on a USE_OBJECT_LIBRARY
command. This warning ca1 be ; gnored and the loader wi II attempt
to sati sfy them at toad tl me.
A map is generated by the tinker containing diagnostics and
information on how the pr3gram was "pre-linked". The default file

SOFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630

4.0 OPERATING SYSTEM NOTES AND CAUTIONS
4.2 PROGRAM MANAGEMENT
name for the link map is SLOCAl.LINK"AP.
With the current implementation, only one module should be
"pre-linked".
A program should be bound Into a single module and
then "pre-linked".

The process of "pre-linkj~g" progr~ms can significantly reduce the
time spent loading products.
"Pre-tinking" one of the system
products resulted in a 35-40 percent reduction in page faults, CP
time, and elapsed time durlng loading. The reduction should be
even greater when loading lar~e FORTRAN products.

1. Tape usage is restricted to permanent file backup/restore and dump
analyzer operations for Rl.l.2.

1. The

SET_WORKING_CATALOG (SETWC) command has no effect upon files
whose names are created within ~pplications. For examples
SE TWC • jx t

execute_task
task generates file

na~e

a

Files created by programs are not subject to the working catalog.
The program should specify a complete path name. File.s referenced
as parameters of commands (i.e., files specified at command level)
wilt end up using working catalogs.
PSR NVEA027
2. Although the preset_value file attribute can be set bye the
set_rile_attribute command, this feature tis not supported.
New
pages assigned to segme~t access files are always initialized to
zero.

PSR NVOS204
3. File attribute MIN_RECDRD_LE~GTH Is not
set
properly
for
record_type
F
files.
MI~_RECaRO_lENGTH
should default to
MAX_RECORD_LENGTH if i t is allowed to default, but It is current'y
defaulting to O.
This affects SORT/MERGE when the sort key Is

4-18

SOFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630

4.0 OPERATING SYSTEM NOTES AND :~UTIO~S
4.4 BASIC ACCESS METHOD
... .-.....-- .... ......
...... .......................... ............

---- -.-----

..-~--,...--.-.---.-~.-.-

-

---... -.-----... ------...-.--.- ....

-

--~

....

-.--~

... --- ....--..-.-.-

omitted and the default is taken. The user should explicitly
mln_record_length : max_record_length.
PSR NVOD398
4. Skipping . forward/backward

by

always report the encounter
correct exception condition.
PSR NV00424

set

records and partitions does not
of boundary condi t ions with the

5. If a
then
who
file

FAP returns abnormal status to AMP$OPEN during an OPEN (new).
BAM still creates the local fite. In sifnpler terms, a user
makes a mistake in theiniti at OPEN of an indexed .sequential
will receive a proper diagnostic, but BAM wrongly goes ahead
and creates the local fite a"y~a,.
PSR NVOE150

6. File attributes
va.ue.

that

can

be changed cannot be reassigned a NIL

PSR NVEA003
1. The SET_FILE_ATTRIBUTE c01mand for an existing file accepts the
specification of a preserved attribute even if i t conflicts with
the present one.
No error wll' be seen and the preserved
attribute witl not be changed. Use DISPLAY_FILE_ATTRIBUTES to
verify attributes were set.
Also, a subset
of
preserved
attributes may be changed ~Ith the CHANGE_fILE_ATTRIBUTE command.
PSRs NVOC839, NVOD617, NVOD549, NVQ0536
8. COPY_FILE does not detect a
file connections.
PSR NVEAl18

COpy

of a file to itself via

circular

q. Fi les impl icitly attached are not i!llp'icitly detached.

PSRs NVOE322, NVOE29b
10. Attributes in the NOS/VE file label cannot be altered after
creation. This could affect some migrating applications using
indexed sequential files because fILE_LIMIT could be updated on
el70 but not on CISO.
P$R NVEA034

11. If a file has a file-access-procedure (FAP) associated with It,
the file can not be accessed from within the Job monitor task. If
this i sa t t em pte d, a message wi t 1 report the ina b i i i t y to
a d the
fAP from the tjbrary 11st. To get around the problem. enter a

'0

4-19

SOFTWARE RELEASE BULLETIN

85103/29

NOS/VE Rl.l.2 lEVEL 630
4.0 OPERATING SYSTEM NOTES AND CAUTIONS
4.4 BASIC ACCESS METHOD
util ity environment of your choice and then access the
an

example,

'ile.

As

if you do a COPY_FILE involving an indexed sequential

file and the error "unable to load FAP ••• "
Just experienced this problem.
PSR NVOC941

occurs, then

YOU

have

12. If a file was created by COLLECT_TEXT at NOS/Ve 1.1.1, i t was
created with 'ite content = legible and line number = (0, 0)
(length and location). Under 1.1.2, if you attempt to copy this
fi'e to another file which does not yet exist,
the copy aborts
with AM 160044
line number length and location are unequal.
Note that it is impossible to create these files under 1.1.2 since
(0
0)
are 0 u t of r an g e val u es for lin e n u mbe r an d ttl e de f au I t i s
(1 1).
PSR NV00521
4.5 .i.D!!lf8.
1. The length of large
100,000,000 bytes.

4.6

data

segllents

and

files

cannot

exceed

It!lERAC..lI}lf
an output
line for a display type terminal (CRTI Is exactly
equal to the page width attribute. overprinting of the tine will
occur if more output lines fol'ow. To remedy this, set the page
width differently or set the output_device attribute (00) to
printer.

1. If

2. Users are now able to Jnfor~ the OS of their terminal model by
using SETIA's terminal_model (TR~) parameter and specifying a 1-25
character name.
This attribute can only be changed by SETTA but
can
be
retrieved
by
IFP$FETCH_TERMINAl,
IFPSGET_TERMINAl_ATTRIBUTES, IFP$GET_DEFLT_TERMINAl_ATTRIBUTES and
can be displayed by DISTA. The login defaults for this attribute
are 'CDC721' for terminal class 3, 'VT100' for terminal class 1,
and
the
null name for all other
terminal
classes.
The
restrictions
which
define
valid
SCL names are the on'y
restrictions for specifyi~g the terminal_mode' parameter.
3. A new error code has been idded to Interactive Facility's
repetoire to indicate that a task has aborted a get operation
because an Interactive condition was received.
IF ESAB ORT_GE T

--ERROR-- gat operation aborted because

4-20
SOfTWARE RELEASE BULLETIN
85103/29

NOS/VE Rl.l.2 lEVEL 630
4.0 OPERATING SYSTEM NOTES AND CAUT10NS

4.6 INTERACTIVE
interactive condition received

1. A
new
function
SBACKUP_FIlE
is
available
under
the
restore_permanent_fi'es utility. The purpose of this function is
to interrogate the information on a backup_file produced by the
backup_permanent_fi Ie uti' Ity.AII
characters returned in the
string are in upper case. The $backup_file function causes the
backup file to be rewound, so only the first item on the backup
file may be queried.

S8ACKUP_FILE«file> (attribute))
The file parameter specifies the backup file to query.

attribute

result

IDENTIFIER

string

Returns the path name of the first item
on the backup file.
This is the default attribute.

IOENTIFIER_ TYPE

s tr j ng

Retur"s the type of the Item. Either'
'SET' t:AT4l0G' 'FILE' or 'CYCLE'
is returned.

Currently no abbreviations ~re supoorted for either
Or for the attribute keywords.

the

function

An example use for this function is In attempting to restore from
a backup fite for which the na~e of the catalog or file backed UP
is not known, but the destln3tJon of the restore is known. Note
that the value returned is a string, so that Sfname needs to be
used
to convert this to a file name, if this is to be used as a
parameter on the rest~re_cata'og Qr restore_file subcommands.
Ex amp Ie:

Suppose someone has sent YOU a backup tape produced bya single
BACKUP_CATALOG command, and that YOU want to restore the catalog
to your own catalog $USER.MY_C~TAlOG. You could do the following:
restore_permanent_fiJes I=Iist_tlle
restore_cata.og Sfname(SbackuP_"'e(backup_file,identifier»
bfabackup_file ncn=$user.~,_catalog

••

4-21

SQFTWARE RELEASE BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630
4.0 OPERATING SYSTEM NOTES AND
4.7 PERMANENT FILE UTILITIES
quit

:~UTIONS

5-1

SOfTWARE RELEASE BULLETIN

85/03/2.9

NOS/VE Rl.l.2 LEVEL 630
5.0 PRODUCT SET NOTES AND CAUTIONS

5.1

kY.alL
1. When using DEBUG to breakpoint on a multi-line statement, the line
number supplied to DEBJG must be the last line number of the
statement.
PSR CIL,A498

2. Run-time error messages, such as RANGE ERROR, do not

display

the

bad value.

PSR CILA515
3. If binary maintenance is required, the CeN parameter must be
specified as $SYSTEM.COM"JN.MAI~TENANCE.OlD_UNBOUNO_CCM. This CCM
interface will be updated for ~etease 1.1.3.
4. The largest negative integer value causes STRINGREP to abort with
arithmetic overflow.
PSR CIlAB38

5. It is not possible to share data variables between CYBIl and
an 0 t he r
I an g u age ( s ,3 y FO ~ TR ANt, bee au see va I l doe s not h a v e an y
mechanism to create a com~o" block.
b. Static initialization treats integers as 60

bits

Instead

of

64

bits.
PSR C[LA880

7. The
RUNTIME_CHECKS parameter is not accepted by the CYBIL
compiler. Currently, the CYBll comoiler looks for RUNTIME._CHECK
(no'S').
PSR CIL0005

8. Tag checking does not work.
PSR CIlAB86

9. Using

a

null

string

i~side

an Inline procedure gives a length

mi smatch.

PSR CILA9b9

10. Using unimplemented featur'es may cause eYaIL
error 38.

to

abort

with

CGl

;-2
SOFTWARE RELEAse BULLETIN
85/03/29

NOS/VE Rl.l.2 LEVEL 630
5.0 PRODUCT SET NOTES AND CAUTIONS

5.1 evarL

PSR CIlA619
5.2 C,LIBJl L

1. A deficiency in the COBOl/UE3UG i~p'~mentation does not allow the
MODULE and PROCEDURE parameter names to contain hyphens when
specified by the user. This prob'e~ can be avoided by omitting
hyphens in the PROGRAM-I) name in the COBOL source program, or by
relying on the default yalues for MODULE and PROCEDURE when using
the
DISPLAY_PROGRAM_VAlUE. CHANGE_PROGRAM_VAlUE and SET_BREAK
commands. (DISPLAY_MEMORY does not support default MODULE names.)
COBOL data_names may cOAtain hyphens, however, when specified as
the
NAME
parameter
of
the
DISPLAY_PROGRAM_VALUE
and
CHANGE_PROGRAM_VALUE commands.'
PSRs NVOF043, OB8A054

2. The KEY_TYPE attribute cannot be overridden any more.
PSR CB8A431
3. The utility routine CBPSSET_FILE_ATTRI8UTES has been deleted.
File attributes can be set in the COBOL program by doing ENTER
"ClPSSCAN_COHMANO_LINE" using "SETFA ••.•• ", STATUS.
The COBOL
usa 9 e 9 u ide con t ai n s
an
e( a11t pte
0 f
the
C L P $ SeA N_ CO 11M AN. D_ LIN E
routine.
4. COBOL cannot replace data items
"INSPECT ••• REPLACE" statement.

referenced

by

indices in the

PSR Ca8A537

5. When compiling with a worKing catalog set. and the compile file
contains COpy statements, the reference decks are not expanded.
PSR CB80006

1. Do not use the file name INPUT in batch mode. It is always a null
(empty) file with no data in it. Choose a different name.
Thi.s
affects migration of Jobs from NOS, where the name INPUT was the
Job's input deck. On NOSIVE 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 EXe:UTE_INTERSTATE COMMAND. This will clear
the FASlAVE procedure,fite and render CREIC inoperable.
PSR NVOF51b

5-3

SOfTWARE RELEASE BULLETIN
85/03/29

NDS/VE Rl.l.2 LEVEL b30
5.0 PRODUCT SET NOTES AND CAUTIONS
5.3 fILE MANAGEMENT UTILITY
3. The ICF connection wilt be ter~in.ted without any indication
( j .e.,
di agnostic or informati anal message) if an FMU .job aborts
within ICF. This occurs in batch Jobs only.
PSR NVOF320
4. When
using
VAX
migration
commands
(CREATE_VAX_REQUEST,
DISPLAY_VAX_REQUEST, DELETE_VAX_REQUEST1, it is recommended that
parameter specification b~ limited
exclusivel,
to
keyword
specification to allow for the addition of new parameters in a
subsequent release •

.1. A job using an indexed s e t1 u en t ia I f f , e may f ai'

due to entry point

errors from the .oader.
The

following

command

executed

earlier In the job

~il'

correct

this:

SET_PROGRAM_ATfRIBUTES TERMINATION_ERROR_lEVEL=FATAL
or SETPA TEl=F

PSR NVOE216
2. When the FILE_LIMIT attribute is set too small for accommodating
al' updates or inserts, the user runs the risk of the access
method aborting with an error A.eSFIlE_AT_FIlE_LIMIT.
In this
case, the file is destroyed.
PSR AA6A380
of
the XREF decks relevant to Indexed_sequential fi Ie usage
should be in one base library. At present, some of them are in
SSYSTEM.COMMON.PSFSEXTERNlL_INTERFACE_SOURCE ahd some of them are

3. All
in

SSYSTEM.CYBIl.OSf$PROG~AM_INTERFACE.

P$R NVOF191
4. The XREF deck AMPSGET_KEY_DEFINITIONS forgets to copy in type
declaration AMTSOPTIONAl_(EY_lTTRIBUTES. The workaround js to use
ARRAY [1 •• n] of AMTSOPTIONAl_XE'_ATTRIBUTE.
PSR NVOF938
5. The GET routine does not honor SKEY_RELATION nor update the
In SPRIMARY_KEY_ADDRESS.
PSRs ,ltA8A377

value

5-4

SOfTWARE RELEASE BULLETIN
85/0312.9

NOS/VE Rl.l.2 lEVEL 630
5.0 PRODUCT SET NOTES AND CAUTIONS
5.4 ADVANCED ACCESS METHODS

6. COPY_KEYED_FIlE aborts when copying any empty file.
PSRAA8A357
7. COPY_KEYED_FILE specifying output to a terminal causes
character of each line to be lost.
PSRAA8A353
8. COPY_KEYED_FIlE
aborts
when
copying
nonstandard collated key; the message is
T ABl e·'.

the

first

a file containing a
"CANtT LOAD COLLATING

PSR AA8A338

1. A

CYBIl

range

error

occurs

at

line

4747

of

SC MSCON VERT_UPDATE_ TO_SCU.!

PSR SC8A130
The workaround is to take out the lIST parameter.
2. A new source library for~at has been implemented to support
present and future performa"ce Improvements. This ~ill require
conversion of existing tibrar1~s with the command that follo~st

This command reads an SCU source library in 1.0 format and writes
it
in 1.1 format. There is no procedure to convert 1.1 back to
1.0.

convert_sculO_to_scull, CQNSIOTOSll [base=(file>l
[result=(fi Ie)]
Cstatus=.(pp)..***

where: severity
failure).

can

Entries

be

will

UF ( a n ra Oil v ere d f a i I u r e) or RF (recovered
appear in ASCII collating sequence of the

descriptive data string.
This report uses
the
DISPL~Y~~INARY_tOG
display_descriptive_data
sUbcommand.
The report provides UP to five sections depending on the
types of statistics contained in SENGINEERING_lOG. These sections can
be used to determine j f the number of statistics reported against a
subsystem warrant further inspection or maintenance activity.
The descriptive data in this report is also the first line in the tape
and disk detai I reports.
It will be truncated at 56 characters and
result in loss of message text when long <~f>, (controller),
or 

FeN TV E UN

(jul ian date)

GEN
CVL TK SC STAT

DETAIL STATUS
1

hh:mm:ss descr i pt j 've data
fen ty e un cyl tk sa statl
cyJ tk sc
ERROR PQS
I
statJ
FINAL STAT UNREC ERR
I

OpeD=

REQUEST RTY=

3
I
I
I
I

SECTOR

,
1

I
I
RTY.

7

456
I
I
I

I
I
I

I
I

I

I

J

I

I
J
I
I

10

8

I
I
I
1

I
I
I
I

J
I
I
J

RESIDUAL CNT-

where: descriptive data is the same as In the summary report (up to
characters long), and the remaining lines are described as foilowsl

80

 + det stat 1-10
ERROR POS
(cyl track sectortFAIlURE) + det stat 11-20
FINAL STAT UNREC ERR (gen stat(FAIlURE) + 2 X 10 det stat (only when UF)

This report uses the OISPLAY_SIMARY_lOG generate_group_file subcommand.
The report provides up to four $!ctions depending on the types of
statistics contained in $ENGI~£ERING_LOG. The entries In each section
appear In chronological order. The values in the descriptive data,
counts, oped and equipment type are decimate All other values are
octal. All fields are initia.ized to blankSI and only valid data is
qu an
f i ed.

t,

This procedure displays tape statistics in the following format.

81-4

SOFTWARE RELEASE BULLETIN
85103/2.9

NOS/VE Rl.l.2 lEVEL b30
NOS/VE Peripheral Maintenance

Pr~cedures

Bl.0 PERIPHERAL MAINTE"ANCE PROCEDURES
81.5 DISPLAY_HPA_TAPE_DETAIl (DISHTO)



opeD TVP

PP

CH

]

input: i: This parameter specifies the flte from which the generator is
to read the command table defintitton.
Omission causes SINPUT to be used.
output : o. This parameter specifies the file to which the generator is
to write the CYRIL declarations that represent the command table.
Omission causes $OUTPUT to be used.

status: See ERROR HANDLING.

The input to the generator is In the form of a series "commands" that
declare a new table or add entries to the "current table".

Tnere are three different commands: TABLE, COMMAND and FUNCTION.
Each TABLE "command" starts a ne~ command or fUnction table and and is
followed by any number of COMMAND "commands" or any number of FUNCTION
"commands". An empty table may be defined by omitting COMMAND and
FUNCTION "commands".
01.2.1 TABLE

The TASlE "command" declares a new table.
table name=(name)
[type=command : function]
[section_name-
processor=
processor=

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:13 13:30:56-08:00
Modify Date                     : 2011:08:13 15:34:38-07:00
Metadata Date                   : 2011:08:13 15:34:38-07:00
Producer                        : Adobe Acrobat 9.45 Paper Capture Plug-in
Format                          : application/pdf
Document ID                     : uuid:fddc730a-cfaa-480c-a6cb-f17eb962133c
Instance ID                     : uuid:82f31e73-f4be-4882-8c5e-295b519f99bb
Page Layout                     : SinglePage
Page Mode                       : UseNone
Page Count                      : 186