NOS_VE_1.1.3_Level_644_Software_Rel_Bulletin_Oct85 NOS VE 1.1.3 Level 644 Software Rel Bulletin Oct85
NOS_VE_1.1.3_Level_644_Software_Rel_Bulletin_Oct85 NOS_VE_1.1.3_Level_644_Software_Rel_Bulletin_Oct85
User Manual: NOS_VE_1.1.3_Level_644_Software_Rel_Bulletin_Oct85
Open the PDF directly: View PDF 
.
Page Count: 47
| Download | |
| Open PDF In Browser | View PDF |
1
85/10/02
NOS/VE 1.1.3 OPERATING SYSTEM
L2VEl 644
SOFTWARE RELEASE BULLETIM
:ontrol Data Corporation recommends that the Software
~elease Bulletin be read in its entirety orlor to any
HJ3 I Vf.. I os t "~ I I t~ t j on •
1
85/10l02.
Table of
Contents,
•••••••••••••• •
••••••••••• •
1.2 POST iRS PROBLEM NOTIfICATION • • • • •
1.:3 Sf S TE~ !; DNTEI,rr • • • • • • • • • •• •
l.~
OVERVIE~
1.1 ?URPOs E OF SR13
1.3.1 DPERATING SYSTEr1
••
•• • • • • • • ••
• • • • • • • •• •
• • • • • • • • • •
• • • • • • • • • •
• • • • • • • • • • • • • • •
• • • • • • • • ••• • • • • •
• • • • • • • • • • • • • • •
• ••• • •• • • •• •• • •
• •
1.3.,2 ?R 00 He T SE T • • • • • • •
1.3.3 or Hi: RPR DOUC TS
••• • •
1.4 WARNINGS AND RESTRICTIONS • •
2.0 £y.:;r:::1 Ir"~STAlLArIaN NOTE'S • • • • • • • • • • • • • • • • •
2.1 INSTALLATION • • • • • • • • • • • • • • • • • • • • • • •
2.1.1 NOS INSTALLATION • • • • • • • • • • • • • • • • • • •
;2 .2 N:3 S I VE: 1 • 1.2 - NOS I vf: 1. 1 • 3 I r~ STA l L Ar I ON,i\ Ni) UPG RA{) E
DIFFERE~CES • • • • • • • • • • • • • • • • •• • • • • • •
2.~.1 SYST2M START UP COMMANDS
• • • • • ••• • • • • • ••
2: • ~ • 2 :3 Y Sri: M S}'j UT [) 0 ¥I NCO ~H1 AND S • • • • • • • • • • • • • • •
2.2.:3 S£ TE C:JfiH/,NO l 18R~!RY
• • • • • • • •• • • • • • • • •
Z.2.4 OPiRATOR COMMAND LIBRARY • • • • • • • • • • • • • • •
Z.2.j R2LJADING FILES • • • • • • • • • • • • • • • • • • • •
2.2.6 USliG NDS/VE WITH 834/639 PERIPHERALS • • • • • • • • •
2:.3 NO:; I Vi::. INSTf.~tLATION • • • • • • •
• • • • • •
2.4 J1Alt/Vi: INSTALLATION • • • • • • • • • • • • • • • • • • •
;2.;;; C1 '] () CJ!'HHJN PROD Hers • • • • • • • • • • • • • • • • • • •
,2.6 N:)S/aE rNSTAlLAT ION • • • • • • • • • • • • • • • • • • ••
2.7 OPtRAfOR COMMANDS • • • • • • • • • • • • • • • • • • • • •
0
2.8
CUN.Frl;UR.;~T!\]N
MANAG;:;r·U:rrr
•
•
•
•
•
•
•
•••••••••••
• • • •
•
•
•
2.9 DEVICE MANAGEMENT/RECOVERY • • • • • • • • • • •• •
2.10 PERMAN2NT FILl UTILI1IES • • • • • • • • • • • • • •
2, .11 CJ ~1 ttl A \~ uLAN GIJlt GEST ;\ T I .s T r c • • • • • • • • • • • • •
~.12 ONLINE MANUALS • • • • • • • •• • • •• • • • • • •
• •
• •
1-1
1-1
•
1-'
•
•
•
•
•
•
•
• •
• •
• •
• •
• •
1-1
1-2
1-2
1-2
1-3
2-1
2-1
2-1
• •
2-4
2-4
2-5
2-5
2-5
2-6
2-7
2-9
• •
2-16
• •
• •
• •
• •
• •
• •
• •
• •
• •
• •
•• • •
• • • •
• • • •
• • • •
2-18
2-20
2-21
2-27
2-27
2-28
• • • • •
2-28
2-29
3.0 OP~RATI~G SYSTEM NOTES AND CAUTIONS. • • •• • • • • • • • • •
3.1 PHYSICAL 110 (TAPE) • • • • • • • • • • • • • • • • • • • • • •
3-1
3-1
· '. . . . . . . . . . . .
4.0 PRODUCT SET NOTES ANO CAUTIONS • • • • • • • • • • • • • • • •
4.1 ACCQUNTI~G AND VALIDATION UTILITIES.
4-1
It-l
HJST SYSTEM NOT~S • • • • • • • • • • • • • • • • • • • • • • •
NO~ 2.4.2 LEVEL b4Z nPEPATING SYSTEM
• • • • • • • • • • • • •
NOS/BE L2V~L 6~7 JPERATING SYSTEM •• • • • • •• • • • • • • •
5-1
5.~
5.1
~.2
b.U FCA LEVSLS
•• •.• • • • • • • • • • • • • • • • • • • • • • •
APpendix A NOS/VE
A1.0
AI.l
41.2
P8rtphtir~1
M~jntenance
and Support
5-1
'-1
6-1
• • • • • •
A-I
OUAL STATE DEVICE MANAGEMENT • • • • • • • • eo • • • •
WHICH IS CUMMON TO NOS A1D NOS/BE. • • • • • • • •
IO!O$YNCRASIES • • • • • • • • • • • • • • • •
Al-l
Al-l
.A1-2
~OS/VE
PROC~SSING
;~;JS nUAL STATE
2
NOS/Vf:. 1.1.3 lavel 644
8;/10/02
So ft 'W liir
Al.3
t~
Rei ;ease thlll e t j n
~OS/8E
Appendix B
0UAL STATE IDIOSYNCRASIES • • • • • • • • • • • • • • •
Support of 7154 Controller
81.0 SUPPORT Of 7154
CO~rFOlLER
••• • • • • •
• • •
Al-3
• ••
i3-1
••••• • • • •• • • • • • • • •
81-1
1-1
NDS/VE l.1.3 Level b44
85/10/02
Software
BulJetin
~e'e8se
----~----------------------------------------------------~-------~-----,
l.~}
...
"u.-,"-
.z..
d,"
,_',-,'::
;,~''''
';I,', ',Wi ,~,',• •
!.~
.. :';';2.
.l,
'
The NOS/V£; 1.1.3 Lev f.! I 644 Software Relt!ase Bulletin (5R8) Is to be used In
conJunction
with tha
NOS/VE
Instal 'itt on and Upgrade M'anua' (!UM) for
install in(J NOS/V'£. and its software prorlucts.
Control Oata recommends
the SRB baread in its entirety prior to software Installation.
that
The SR8 is the vehicle In which any cha~ges to the rUM, after It has gone
to print, Ira document~d. Althoulh features are not 'ul'y documented in
this SRB, major changes In the system are highlighted with emphasis placed
on instatlation dependent and configuration management data.
This
Leve.
docum~?nt cont·alns
~44 iystem.
'nrOrm~iJtJon
n!~c·ess~ry
to lostelt
thi!
NOS/VE
1.1.3
Any
sij;Ji1I'Ficant
problems that occur after publication of this SRS wltl be
document+.:din Installation Bulletins £Ivai lableon SOLVER.
PI'sase note that
Instal Jation Bulletins are the vehicle used by Cents. Software Support to
notify sites of siJnl'lcant
it
system,
The
$R3
as wei.
also
so'tw~re
problems Identified during the life of
process.
as problems·with t;he installation
documents
of system deficiencies. qafer to the
latl i • lty
au Ilat I n f o r a comp' ete
description of dual state partner combinations support~d with this release.
NOS/VL 1.1.j L-r~v e If;,4 ti
a
number
SO'jltwlilre
Av:~i
1-2
NO S I \I £ 1 • .i. • 3 l eve I 6 44
85/10/02
1.0 O\HERVIEW
1.3 SYSTEM :ONTENT
This section
lists the
enhancements~nd
newf!!;atures of
Leval 644 system.
1.3.1 OPERATiNG SYSTEM
o b3 Char acter Scat
o tilero ri Ie Transfer feci .tty (p[=TrF) Support
o
o
o
o
o
o
o
AAA Concurrency Support
BASIC and PASCAL Support
FO~TRAN Argument Chacklng
Recovered Tape rrors
Loader Table Extensions
fSP:$l)PEN_FIlE
Processing
~ord
(FS~)
o Scan J:oken Upgrade
o
o
o
o
o
SM/TDU Support of Scrolting
fAPs on Command Files
SCU 1.1 Enhancements
FuJI Path PF Errors
INCLUD~ Command
o Pe.rfor:nance Enhancements
o
o
o
o
o
o
Screen Management Performanca Enhancements
NJS/3e Dual State Pack8Je Souraa Code Support
NOS 2.~.2 Level b42 Verification
NOS/BE 1.5 level 627/631 Verification
CY:31L 85.2
Corrective Code
o t\ ;~$l C
o P,ASCAl
o PROL] G
o
o
o
o
o
o
o
1~1/Z'2U:)
AAM Enhancements
COBOL 2nhancements
Debug 2nhancements
FORTRAN Enhance~ents
FMU ~nhancements
FHA
~nhancements
o 1MI0'1
o Corrective Code
l.~l.~
U'fHJ:R PRODUCTS
o MAIL/Vi:
the
NOS.lVE
1.1.3
NOS/VE
~.1.3
Level
1-3
6~4
85110/02
Software
~elease
BulletIn
1.0 OVk;RVIEfl
1.4 WARNINGS AND RfSTRICTIONS
The following
release:
w.rnln~s
1. Chao;;,1e:s
to
the
CVB r l me du I at S •
and restrictions 3re
proI~:RATDK_COr1MAND_lI~3RARY)
pfoolam, unless you want to use a restore procedure different from the one
suppJjad by CDC. In this case, pl~ce your procedure on the NOS rile SITECP
(just
like the CDC restor e r • y e)( is t s j nus e rA P LJ a san In d 1 r e c ta ndp u b' 'C
file.)
APL),i s
FAILED '
SET_LINK_ATTRIBUTES US~R·(APLO NOS) PASSWDRO=APlO
R2PLACt_FIlE FROM=$SYSTEM.APL.MAINTENANCE.AFIFIX ••
TO=AflfIX DC=BotJ
3. Intarim Remote Host partner jobs are submitted 8S batch origin Jobs
with the advent of NOS 2.3. Problems with the commands GET_FILE and
R2PlACc_FILE occur when the NOS system batch job limit Is set too
low. This could cause GET_FILE and REPLACE_FILE to fail with the
error message "UNA8L~ TO COMMUNICATE WITH MOS 110 REMOTE HOST". What
happl"ns Is th;at wh,n doinlJ ona or these comm!lndSf 8 partner Job
gets
spun off and is submitted as a batch Job to NOS. If there are enough
batcl'l jobs runnin,'l to reach the batch job I imlt, the partner Job wi II
be put In the NOS Input queue to walt for one of the batch Jobs to
finisn. The 180 side Naits for th! Plrtn~r Job to 'inlsh.
If the
2-10
8;5/10/02
Software
~elease
Bulletin
2.0 SYSTEM INSTALLATION NOTES
2.3 NOS/VE INSTAllATION
180 sida do~s not Jet a response from the partner Job within 10
minutes, then it wi'. time out and Issue the error message above. To
gat around this problem, we recommend that the batch limit be set to
2~ to 50 or more depending on the use of 'I'e transfer through Remote
Host and Interstate Communication in your system. The ma~tmum number
of Remote Host and Interstate Communication Jobs that can be running
at one time is 50.
NOTEt CREATE_INTERSTATE_CONNECTION (CREIe) commands do not
" n the lSi;} s i da.1 hey will
time
out
walt un til the partner Job get.s r 0 I • e di n
and finishes before they continue on.
4. 00 not do a INITDD on a TERMINAT~_SYSTEM as stated in Item 6
NOS/VE Analysis Manual, page 2-5.
of
the
5. CIPL004,speciflcally the contro'ware that (s used for the 834 disk
subsyste.m, ,~ontains a ;jefectwhich wilt be encountered b,Y sites which
configure more than four 834 control modules per channel to NOS/VE.
This defect wi"
cause a control module to master 01 ear all control
modul::.son Its channel, requiring a redeadstart of NOS/VE. Itls
stron~ly suggested that no site configure more than four a3~
control
modules per channel, and that the unit numbers or the control modules
be 0, 1,2, and 3. CIPL004A and CIPl005 will conte)n corrective
code.
6. The d8f~ult value of MAXI~UM_SEGMENT_lENGTH has been changed to
150000JOO(10) bytes.
This Is tlso
the
minimum
value
that
SET_SYSTEM_ATTRIBUTE will allow for this parameter.
7. In
addition
to
the
Va 1I d:a tJ on Uti I I ties r
Incl~de
steps
~~ fer
listed
in
the
NQS/VE
Accounting and
e nee mg n U 9 I, s I tits us I n g the tJ t I I I tie s must
the following entry in their NOS LIBOECK.
*PROC SYNCACC,SYNCVAL
It defines SYNCACC and SYNCVAL
executable as NOS commands.
9S
procedure files and makes them
8. The 834 disk subsystem and the 639 tape subsystem are new peripheral
produots supported by NUS/VE Rl.l.2 feve. 638. These products are
fully described in the NOS/VE Installation and Upgrade manual.
NOS/V~
when running in a d~al state environment with NOS/BE does not
support the 834 disk subsystem.
To ba used by NOS/VE, the 834 device must
entry j n tt'H~ NOS fr~Q~Oi;~CK.
not
be
assigned
an
EST
2-11
NOS/VE 1.l.3 Level 644
----... --.-.-.
2.0 SYSTEM
Software
:85/10/02
Rele~se
.....
~.-----
Bulletin
.....
---- ...--............-...-...----- -...
.....
-.-..........
INSTALLATION NOTES
2.3 NJS/VE INSTALLATION
---- ..........-....
..-- ....
_.....- ......---_ ... _--- ...-_ ......_--
EQPOECK only If th3 sIte wJshas to b~ able to use the tape unit on
both NOS and NOS/VE (via the CHANGE_ELEMENT_STATE command). NOS/VE
whan funning in a dual state environment with NOS/BE does not support
the b39 tap~ subsystem.
The tape unit does not need to be defined In the NOS EQPDECK if only
NUS/VE Hj" be usIng It I but car. must be taken to assure that NOS
>tAlET
do~:s
not
conf I let wi til
i:~f.JS1VE
I nfunct i onlniQ th!
tlPe
:5 iJbs
ys t em.
MANAGE_LOGICAL_CONFIGURATIDM subcommand, CHANGE_ELEMENT_STATE,
produces the 'ollowJn~ mass$ge at the NVE control point on
9. The
somatim~s
NDS.
EQUIPMENT NOT AVAILABLE/NOT ASSIGNED
This
~essage
should be ignored.
P S R. hi \IHJS/VE sjstemconsol e enter:
usln'J
the
contents
the
of
UPGRADE_SOfTWARE.
At the
uPGRADE_SDfTWARE
INSTAll_PROOUCT aMLIN2_~A~UALS_I
(Respond to the tape mount request and wait for the tape
un' oad.)
It'4$ TALL _fiR GDUf; T ON L!t'-4C: _i'tAN
i"
to
~~LS_II
(Respond to the tlpa mount request.)
QtJ!T
g. Repeat the set of commands described In step e.
n. Allot the NOS/VE software is now Installed and the system has
a reasonable ammount of 1isk space 8vaileble for user programs
,~n d
da t Si •
You
s h ou I dpr 0 C e d e with step 14 (E s tab' Is h fa mI Iv
iJ s er1.t d ml n Js tri tor .s. )
12. NOS/VE supports
memory
sizes
UP
to
128
megabytes.
The
NOS/VE
de~dst~Lrt
input file CTPXXXK) Included with the release materials is
built to optl~jza performance on a system with 16 m~gfbytes ot
memory.
ThIs results in measurable performance degradation on
systems with 32 megabytes ot memory because of frequent "page table
rull" conditions.
Systems with memory sizes signlrictntly larger
th6t 32 megabytes t-J.d " not run at a.I.
NOS/V~
1.~.3
Level 644
85/10/0.2
Software Rei ease Bulletin
2.0 SYSTEM INSTALLATION NOTES
2.3 NOS/VB INSTALLATION
In order to run MOS/VE on a farge
mega6ytes or
lar;\)ar) incorporat,e the following step.s In your installation process.
a. i4h-en you
re~·ch
CRedeadstart
step
NUS)
10
of
select
memory
the
the
system
NtlS/VE
(32
installation
proce·ss
P (DEADSTART PANEL PARAMETERS)
option of eTI.
D. At the NDS system console anter:
•
c. Continue with the NOS/VE Installation process described in the
NOS/VE Inst·all!Jtionaod Up~ri1de manual through step 13 (Instal t
NOS/VE standard and optjona. products).
d. Before terminating UPGRADE_SOFTWARE wIth the QUIT command use
the MAKE_YE_OEADSTART_FILE subcommand of UPGRADE_SOFTWARE to
build a neM NOS/VE deadstart input fife that is optimized for
your memory size. At the NOSJVE system console enter
SETLA (un,t,nlt;) pw
MAKE_VE_DLADSTART_FIlE PS=8192 MS=memsize
un
and
pw
specify the user name and password you are us I n9 to
install NOS/VE.
memsiza is the actuat physical memory size
of
your s.ys tern.
The MAKE_VE_ ADSTART_FIlE command presumes that SITECP and
DeFILE are Ival13bl. on the NOS or NOS/Be catalog specified
\III j th
the SETLA command.
If they ar e not present or if the
S~TLA command was Incorrect, MAKE_VE_DEADSTART_FILE wi "
return
~n
error.
If this happens you should correot the problem and
reissue the MAKE_VE_D~ADSTART_FILE command.
MAKE_Vf_DEADSTART_FILE places a new NJS/VE deadstart Input fl Ie
on NEWTPXK In the oataloJ you specified with SETLA.
e. Terminate
UPGRADE_SOFTWARE
and
NOS/VE.
At the NOS/VE system
,;onsole enter:
QUIT
TERMINATE_SYSTEM
r.
Redeadst~rt NOS.
tjm~ to restrict
This tlm~ do NOT use the
memory us~.
eM
option
at
ell
g. Login to the NUS catalog that you are using to instal) and
deadstart NOS/VE. Ch~nge the name of TPXXXK to something else
t~ClS/v;ci
1.1.·j level 644
8:5/10/02.
Software ?tel,ease Bulletin
2.0 SYSTEM INSTALLATION
243 NUS/VE INSTALLATION
~OTES
(OTPXXXK for example.)
Ch~nge
the name
0'
NEWTPXK to TPXXXK.
h. Redeadstart NOS/VE using the NOSVE deadstart procedure fl Ie
(NVExxxx) that you built in step 11 (Generate NOS/Ve deadstart
pro cad u r eft Ie) •
j.
NOS/V6 is now up and running with your full memory.
Continue
the installation starting with step 14 (Establish family user
administrators).
NOS/VE 1.1.3 Level &44
85/10/02
Software
Release
Bulletin
2.0 SYSTEi INSTALLATION NOTES
2.4 HAIL/Va INSTALLATION
1. The Installation of MAIl/VE begins with the
but must be completed as follows:
instalJatlon
of
NOS/VE
a. The fol'owing catalogs and fites should be present under master
catalog SSYSTEM.MAILVe after complet'on of NDS/VE Installation.
tiAl NTi:NANC E
COM"1ANO _LIB ft}\K Y
Fide containing the bound MAIl/VE
bin ar y.
Catalog containing the fo'Iowlng'
System Admlnistrltors command
library.
System Administrators HelP ont Jne
man iJ a I •
b. To continue with installation of MAIL/VE enter from the SSYSTEM
consol\9:
SET_COMMAND_LIST
AOD=$SYSTEM.MAILVE.MAINTENANCE.COMMAND_LISRARY
This command adds the System Administrator command
library
to
the command list.
c. Then install MAlt/VE by entering the fo.lowing command'
'I'~s, create the
and register the first
MAIL/VE usars - $SYST~H and "AIlVE. This procedure Is fun once
after NDS/VE Is installed but not to subsequentl, reinstall
MAIl/VE.
This comm3nd wll' build the MAIL/Ve
necessary file and catalog permits,
datab~se
folJowjng the comp'~tJon of the INSTAll_MAIL procedure, these
addlt.onal sub-cata'oJs should exist under SSYSTE~.MAIlVEI
C.AIALDG
I~AIL
(lACK. UP
Cata10g where the live database files
~r;3 stored.
Catalog where backup copies of the
database fIfes are stored.
The files and catalogs should have the following
contents
and
NOS/VE 1.1.3 llvel 644
85/10/02
z.o
SYSTEM INSTALLATION NOTES
2.4 MAILIVE INSTALLATION
permit::;:
$$YST E~* .r1AIlVE
Cat:alog -
G=USER USER=MAIlVE
FN=fam II y_o:ame
AM-(ALl CYCLE CONTROL)
SM=NONE
This is the master
MAIL/V~
catalog.
S$YSTEM.~AILVE.BOUND_PRaDUCT
Fi I e
G=P UBL Ie
AM=(READ iXECUTE)
SM=(REAO EXECUTE)
SSYSTEM.MAILVE.BACKUP
Cat,af O:J
NO Pl;IRMITS
This catalog should be empty.
S$YSTEM.MAIlVE.MAIL
Catalog
G=PUI~LIC
AH=(R2AO SHORTEN APPEND MODIFY)
SM=NONE
This catalog contains the seven central
rna I Idat -~b as 'i~ -rl I es.
SSYSTEM.MAIlVE.MAINTENANCE
C at at 0 9
"ND PERMITS
This oatalol contains the System
Administrators onlina manual and the
System Administrators command library.
2. T he \"1 A 1 t I VE S y s t em Aom i n i s t r~ t \) r 'm us t r un
$SYST~M.
MA I LV;: C i3n
Since
hE;
Cr
as
us ern am e MA. I l VE 0 r
SSYSTEM must run from the NOSIVE console, user name
eat e d
\of hie h·.,.
i 1t
a I low
ri
S Y S t em
Adm I n 1st rat () r
t
0
p;arform the maintenance opperatlons -from anjnteractlve terminal. In
order for user MAILVE to run MAIL/VE malntennance routines, the
com~and library must be attached vJal
SET _CLH1MAND_LIST
ADil=$SYSTEM.MAILVE.MAINTENANCE.COMMAND_LIRRARY
2-18
NOS/VE 1.1.3 Level 644
85/10/02
Softwar'e Release 3ullet1n
2.0 SYSTEM INSTALLATION NOTES
2.4 MAIL/VE INSTALLATION
3. The MAINTAIN_MAIL utility registers
users
In
the
MAIl/VE
system.
This 4tility is accessed via the command:
MAI~TAIN_"AIl
(MAIM)
Pw='VU NY
The passMord for MA1NTAIN_HAIL and ror at. Its subcommends Is VtiNV.
The various
Ii steed from
followed by
commands
to the System AdminIstrator can be
uti I • ty b yenter in 9 HELP
return.
The System Administrator online
available
wi tni n the
a carriage
MAINTAIN_MAIL
IHl accessed tor additlon!1 Informatlono!1
commands by entering the followings
maniJalc~n
the
IV.' I able
The
~Inual
mQY
aJso
be
iccessad
directly
by the System
Admininstrator, funning with user name SSYSTEM or HAIlVE, via:
4. Other procedures available on the System Administrator command
I ibrary and
descr ibed
in detail in the System Adminlsttator online
manual are:
:a. BACKtJ? _riA,! L
This procedure backs UP the MAIl/VE database files.
This
procedure can be run as often as needed to backup the database
r I I es.
b. Ri:STORf_MAIL
This procedure reloads the MAIL/V~ database files
baen becked UP using the BACKUP_MAIL procedure.
that
have
c. DiSPLAY_MAll_STATISTICS
This procedure creates a graphical usage listing of the usage
ot H~IL/VE over the current usage period.
The current usage
period is deft ned as that amount of time since the last
deadstart of NOS/VE.
d. CHANGE_f;#\!L
This procedure can be used to replace the MAIL/VE binary.
procedure may never have to be run.
1. ~
i;s rest:artad by enterin;,:
MOTEa Changes were made to procedure RUNJOBS to allow for
PASSON
to
whene"lIer it ,harts :abnormally.
If PASSON aborts
abnor~ally, the system wll.
attempt to restart PASSON automatic.tly.
If NAM goes down, PASSON wil' not be automatically restarted.
restart
3. fh·{i
Itself
i:iDSllppl jeatl on
('VEIAF)
th~ltconnects NDS/VE jobs to 'NAMwi J I
sometimes produce the flash'ng console mess,get
"PASSON ABN [HH1AL 18"
This message means PASSON is discarding an unsolicited message
1eneratedbetwean VEIAF and the first read request from NOS/VE.
This should ba ignored.
Clear the mess.ge with fGO,jsn.·
See Section 3.14 ror PASSON diagnostic messages.
4. The operator
thatr:aquire:s
should not enter any command at the operator's console
m~gnetjc tape.
This wjllgenerally yield a deadlock
All
r'equests should come from other than the system job.
}1
condition.
This wi II permit assjlnment of equipment from the operator's consol e.
5. Restarting IRYF on the NOS/BE side.
To
make provision for restarting IRHF,
procedure has been provided. Simply typeS
en
operator
initiated
n n • X RIJ NI RHF •
~her
b.
e nn I s a clear control point number.
PASSO~
Abnormal Processing (NOS/BE)
Durin~
periods of heavy jnteractlve usage, the message'
miY
on the ~OS/aE Job status (8) display. Unless related to a
that a user has reportgd, this massage does not necessari tv
indicate an error condition.
appe~r
problem
When PASSON A3NORMAL $ppe8rS on the system consol. screen, record the
number of the message for your site anatyst'i use.
2-23
NOS/VE 1.1.3 level 644
85/10/02
So ·r twa re Rei e as e Bu I 1e tin
2.0 SYSTEM INSTALLATION NOTES
2.7 OP~RATOR COMMANDS
If your analyst asks you to examine the dayfile of
enter the tollowing command:
the
PASSON
Job,
A=NN.
~N
the control poInt number of the PASSON Job.
is
~xamlne
The message formet ist
the dayfile for the messtge.
HEX DATA FOR PASSON CJNDITIDN=MESSAGE NUMBER
Th,e
~hich
mas.saga's 'rollowed by one or more lines of hexadecimal data
your site analyst m~y aSK you to record.
See Section 3.14 for PASSON diagnostic messages.
INITIALIZ2_DEADSTART_DEVICE system
core
commlnd
,nd
the
INITIALIZE_MS_VOLUME Lo~lcal Confi~uratlon Utility subcommand do not
warn the operator that the volume has been previously injtJatlzed.
This is of particular concern In INITIAlIZE_MS_VOlUME because the
7. The
opar ,tor
m!~y
misspell
th .l
;el
ament_n~me
of
the
davle/!
and
inadvertently destroy permanent 'iles.
t~~.
In order to fr(~e:ze the display on the NOS/Vi~ opera,tor's cansol e while
i t is rapidly updating, we sugaest using the 'SETUP'
key.
Pressing
the 'ShTUP' key will cause the console to stop accepting data from
th:e host which wit' immediately halt
the
dispL~y.
The
lower ,two
lines will be temporarily overwritten with the setu~ optIon display.
Prassjno th'~'Fl' key~i
the display to resume updating.
":3.'0"
'::). If tha ope ratiJ race i d'ent a8. yassi gns a VE tape to the wron;, "f Job,
no Indication of this situation Is given and the tape remains
littachad to th~ ('"ron;) Job until
i t ands.
Ifanothe.r drive is
:avai tab je the tape can be mov;adand reassigned.
?SR NVJl:a,4
10. Tnere ere
Thes ear e
t~o
~perator
commands available for manuat Job swapping.
) wAPGUT an d
SWi~PIN
Is the system Job name of the job to be swapped.
If tha Job is to be s~iPped In, using the OISSJ command wilt provide
the JSN necessary for the SWAPIN comm~nd. When a Job Is swapped out
using the S~APCJUT cornmanr." it
.:)1'IAPn4 commend is I!xecut,gd.
wll'
remain
swapped
out
until
the
NOS/VE 1.1.3 Level
2-24
b44
8511 f)IOZ
2.0 SYST~M INSTALLATION NOTES
2.7 OPERATOR COMMANDS
....
...--.- .......
.... .....-- ...
--~-.-",,-
--_
~---
--- ---.- -- -...---.....
---.~
.. ... ...-................--....
-.
~
.---.-.-.-~
... .-.-... .-.-.- ---- ..-.
.
11. The STOP key on the NOS/VE console provides the operator with a pause
break utility.
Yawever, thd system is unable to de •• with this
correctly during deadstart.
If the STOP key is pressed during
;,j;esdstart,
the system will
t:ermi nate withe fatal error lTH~ss8ge.
Users should avoid pressing this key during the de~dstart process.
If .t is accidently pressed and the system aborts, deadstart must be
started over.
If the STOP key is pressed during the latter part
process, the console mQy respond with the prompt:
of
the
deadstart
PI
If tnls happens,
immediately.
the
RESUME_COMMAND
command
should
be
entered
12. If a system crash is caused by a fatal disk error, only the Jist
lines
of
the
failure
two
de:scrJptlon ar,)! visIble In the main operator
\IIindo~.
Thus,' t i s Impor'tint after any system 'raJ lure to expand the
main operator window and record any error information present.
The information dlspJayedin the window should be written down
In Its
entirety. The information will be necessary to repair the problem.
:4ttemptjn!:,J to "get around" the problem by deadstartlng the NOS/VE
system will destroy the contents of the main operator window. If the
NiJ S·, 'Vi:. s y s te m 'f a I 'S due t 0 a d t s k pr 0 b I em, NOS 1 VE IS En g I '" ear I n 9 Log
is unavailable to the Customer Engineer; thus, the Information
written to the system console is the only evidence of the failure.
13. If during NOS/VE
error is r,!turned:
deadstart
PPs
cannot be assigned, the following
PP NOT AVAIlABl2/NOT ASSIGNED
~a
~ttry
PP AVAILABLE.
the deadstart.
P:) R N'\I QG29 :)
14. The mass
4':;Je
teQAC
c()ntrof point.
PSR N\lOG307
A controlware
not r
4
173
173
LOO4
1 7~';
cya;'~
Z
L·:)04
173
R
~j6()
1~13
NaS
,.4t
,. • 2-btt2
.'.'~
,
.... .4 • 2-642
t:: • 4- • 2-642
'L'~':lr
2.. 4. 2-642
.;
2 . ' t • 2-642
")
'ioo
....... 2-642
,t.
Z. 4. .2-642
.4. 2-642
2.4 • Z-642
"'1
:'-
2 • 4 • 2-b42-
NOS IV\~
NOS/BE
-- ... -----
--------
1 .1 • 3-644
1 .1 • 3-644
:1 • 1 • 3-644
1 • 1 • 3-644
1 .1 • 3-644
1. 1. 3-644
1 .1 • '3-644
1 .1 • 3-644
1 • 1. 3-644
1 • 1 • 3-644
1 • '-631
1.5-631
1 • 5-631
...... .5-631
1. • 5-627
1 • 5-631
1 • 5-621
1 • 5-031
1 • 5-627
1 • 5-631
the
NOS/WE 1.1.3 level
6~4
85110/02
Software
Reld8se
Bu.'etln
A1.0 NJS/VE DUAL STATE DEVICE MANAGEMENT
In the j'fDS .lVE. dual state system, ··13 I I thee I aments (chsone Js, contra II er s,
storage d~v1aas) which belong to th~ NOS or NOS/BE system which .r8 likel,
to be used by NOS/VE may be described in the NOS/VE physical configuration
for tne mainframe.
It is a requirement that at least the subset of the
physlcat configuration which is to be Inc'ud~d In NOS/VEts 'ogicil
conrjg~ratlQn must be described in NOS/VE's physicat configuratIon.
When ,x8cuting In a dual-state environment, NDS/VE acquires its PPs,
channels and certain types of peripherals trom Its NOS or
NOS/BE
counterpart as dictated by the most recently installed physlca' and logical
configurations. TerminatJon or NOS/VE execution wit. cause the resources
acquired by NOS/VE to revert back to the NOS or 4DS/BE system.
NDS/YE does not share a mainframe channel with a NOS or NOS/BE system but
NOS/VE wi' I share a $715~_lx or a $7021_32 controller with a NOS or NOS/BE
systeJf1.
However,)~a.chstate
must
have a unique channel access to the
eo n t r 0 I I er •
A mass stora~e or tape storage device cannot be accessed concurrentl, by
both dual-state systems) ane state must have exclusive ownershjp of the
stor~g8 dsyice at I time.
The Information recorded on 8 mass storage device by ona state is not
directly readable by another state should a mass storage device be
alternately o~ned by the d~al-5tata systems; the
volume
must
be
re-Injtial 'zl~d by the system to use it next. However, itis not necessary
to reformat $u65_1x, S144_4x, nor $834_12 mass storaqe devices when
atternatinl the use
the stora~e davlo~s betwesn states.
0'
8y using the CHANGE_ELEMENT_STATE subcommand of the leU, one cen toggle the
ownership of a tape subsystem ele~ent bet~een the NOS or NOS/BE system and
NOS/Va without requiring a ds@dst.rt 0' eithar st4te.
41-2
NOS/VE 1.1.3 Level 644
85/10/02
Software Rei
i~ase
!3ulletin
A1.0 NOS/VE DUAL STATE DEVICE MANAGEMENT
Al.2 NOS OUAL STATL IDIOSYNCRASIES
and
The fo'lo~lng t~b'e summ~rjzls the
configuration
requirements when configuring a NOS dual-state system'
•
••
Product
:Must be In
JNOS EST
:To Sa Used
:81 NOS/VE
: C,an be In
:NOS EST
t
:
•
••
t
:Ownersh1p
1May be
:Toggted
:Setween
:States
+.....-----.-.. . . --..... --...--.+-.--..--....- ....... --.. . . +-:... -~--~-- ......-+--~
'(
$b3 ii-l
$679_)(
I
••
•
$,
••
••
1'4 (3 )
•
Y
Y
y
•
'(
$\344_ ... )(
:$ '7fJ2.'l_ ;31
$'702 1_32
$715,_11
$715,_12
$'1155_13
$71'5 ,_14
)
Y
:93 ... _12
$ Saj _1)(
(1
J
••
•
••
••
$1;~}39j_ll
+-......-.-.-,--~-----.+.----.--
I
•
J
•
I
••
•
f
Y
y
'f
•
t
1
N (3,4 )
.....
•
••
•,
••
••
1'4
y
N
(
(
3)
2)
y (2)
if
(2 )
y
f
Y
Y
(2 )
( 1)
''(
y
'101
(1)
( 1)
( 1)
( 1)
. .-.y . .
•
y
J
•
t
•
•••,
••
•••
-----~+-
(1
. . . .----..--..
)
"-
N
y
y
N
N
N
••
:
••
N
••
__ . -, +:
•,•
•
•
••
N
N
N
~.,_.
N
N
N
t
•
:Can be
IShared
:Setween
:States
I
N
N
N
y
N
••t
•
y
Y
y
1
N
------+-..--.~.--~-----+~------.-----.-+---------------------+
Notasl
1. The ~OSJVE channal
NOS configuration.
to the element must be In the DOWN
2. The element and the channel connecting it to NOS/Ve must
OUW~ stat~ In the ~OS contiJUr9tion.
3. The
~OS
st~te
be
In the
In
the
NOSIVE channel may be in either the UP or the DOWN state in the
configuration and must not have any elements connected to It.
4. If the ~jamant is connected to two chlnn!'s then both channels must
be described in the NOSIVE logical configuration, I.e. NOS cannot be
allowed to use either channel concurrent with NOS/VE use.
NOS/YE 1.1.3 Level
:s 0 f
twa ra Re I e a sa
Al-3
b44
8;/10/02
au 1 • e tin
Al.O NOS/Vc DUAL STATE DEVICE MANAGEMENT
Al.3 NUS/BE DUAL STATE IDIOSYNCRASIES
The
following
table
summarizes the
configuration
capabjlltles
NaS/BE dua'-state system1
and
requirements when configuring a
+--....-...,--..- ... \----+ ..---.-----..
ICan be in
:ES T
••
:
$;1)]9-1
$679 _iC
•
••
$Sa4_12
$844 _i-f. x
$885_1 x
:~102 1_31
$ 7021_32
•
••
I
1
~-~:
f
Y (') }
Y ( 2)
Y ( 2)
••
••
V
~(
N
z.
t
•
<:3, 4) •
I
I
-~-----
~O$/iE
channal
NOS/B~ configuration.
1. rhe
•
'{
y
N
Y
N
2)
['l
.J;"
y
I
1
3)
N
Y
N
y
•• $'115 5_12
$7155_13
•
•• $ 71j ,_14
•• $103 95 _11 ••
+-,-...
......---... +.....-.......
(
(
N
Y
N (3 )
y
$11;!i ;~~_11
..... -----.--.. +
. . .-.. .
-~.---.-+ ... ----~.-.-.---~+..-,--lHust be in :Own~rship : Can be
:Shared
:NOS/SE
:"ay be
ISetween
:EST To Be
:Togoled
:Us~d by
:Between
: S ta te s
:NOS·/VE
:States
INDS/Sf:
••
t
----+......
y
(
f
(1 )
Y (
y
y
N
1)
"'!
L )
;'~
y
••
y
••
N
( 1)
(1)
.. --+.-....---.~--....... --~+--
N
N
N
N
•
,'•.
t
t
N
••
••
••
••
t
•
••
N
N
N
N
•
•
t
t
N
y
N
y
Y
Y
N
I
. . . . --------.----.+-.
. . .------.-.-.. .
to the ejement must
••
••
t
t
-~+
b~
in the DOWN state In the
The element and the channel connecting It to NOS/VE must
itate in the NOS/BE configuration.
be
in
the
DUW~
3. The ~OS/VE channal may be in either the UP or the DOW~ state In the
NOS/BE configuration and must not have any elements connected to it.
~.
tne. element Is connected to two channels than both channels must
'o;;Jtcal configuration., I.it. NOS/BE cannot
ba 1110wed to use either channel concurrent with NOS/VE use.
If
oe described In the NCJS/VE
81-1
NOS/VE 1.1.3 level 644
85/10/0Z
Software fCefeasa Bultetln
Support of 7154 Controller
81.0 SUPPORT OF 7154 CONTROLLER
information Is provlci
Source Exif Data:
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:23:23-08:00
Modify Date : 2011:08:12 22:05:15-07:00
Metadata Date : 2011:08:12 22:05:15-07:00
Producer : Adobe Acrobat 9.45 Paper Capture Plug-in
Format : application/pdf
Document ID : uuid:626aae6e-c8f0-48f8-8b7a-f4cfb339b4b2
Instance ID : uuid:05a6015b-967b-4e65-8db3-c9562599e98e
Page Layout : SinglePage
Page Mode : UseNone
Page Count : 47
EXIF Metadata provided by EXIF.tools