March 12,1990 M20-4, Part 11

Change 1

CONTENTS

CHAPTER 3. SYSTEM POWER UP/DOWN

PARAGRAPH PAGE

3.01
Purpose\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...
3-1

3.02 IPL (Initial Program Load)
Process\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...
3-1

3.03 Procedures for Startup and Shutdown of Systems on the
Network\...\...\..... 3-1

3.04 Initiators (Background
Tasks)\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\....
3-3

3.05 Network Startup and Shutdown
Summary\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...
3-5

3.06 Network Startup and Shutdown Summary (using WSNHALT) Post at the
CPU 3-5

3.07 Description of WSHALT
Procedure\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\...\.....
3-6

3-4

March 12, 1990 M20-4, Part II

Change 1

CHAPTER 3. SYSTEM POWER UP/DOWN

3.01 PURPOSE

This chapter supplements information found in the VS System Operator\'s
Reference and software bulletins.

3.02 IPL (lintel Program Load) PROCESS

a\. The purpose of the IPL process is to load operating software from
the system disk to make the system operational. The IPL process may
begin either directly from Control Mode, or after the CPU (Central
Processing Unit) has been powered up.

b\. It may also be necessary to perform an IPL on the system during the
workday to support system operational functions. When re-starting a
system that is operational, ensure that all disk files are closed, all
networking tasks have been stopped, and that all users have logged off.
Once an IPL has begun, the initialize button should never be pressed
until the IPL process is completed. If an IPL is interrupted in
progress, the system disk\'s VTOC (Volume Table of Contents) may be
destroyed, preventing access to all files on that disk. The program
controlling the IPL process automatically prompts the system operator
through the steps to completion.

c\. Problems encountered during the IPL process will be entered in the
Maintenance Log (see 2). Since \"fatal\" and \"non-fatal\" errors can be
generated during the IPL process, both need to be recorded and referred
to Wang Customer Engineering for guidance and interpretation.

d\. The procedures described in paragraph 3.03 for Network Startup and
Shutdown must be followed before and after every IPL. In the event of a
system failure, refer to paragraph 13.08 for Recovery Procedures.

3.03 PROCEDURES FOR STARTUP AND SHUTDOWN OF SYSTEMS ON THE NETWORK

a\. Network Startup

\(1\) An IPL will be performed on the system using the communications
configuration file (@CNSCOM@ in \@SYSTEM@). The system will require
approximately 15 minutes to complete the IPL process. Logons should be
inhibited at IPL (LOGONS = YES) and microcode should be loaded to all
devices at IPL (LMCODE = YES) (Fig. 3-1).

MESSAGE M001 BY SYSGEN

INFORMATION REQUIRED

Specify the name of the system configuration file and press (ENTER)

\*or

\*Press (1) to use one workstation and one disk.

\*

\*SYSFILE = \@CONFIG@

\*SYSLIB= SYSTEM@\
\*\
\* Specify the communications configuration file to be used, if any\
\*\
\* COMMFILE = \@CNSCOM@

\* COMMLIB = SYSTEM(@-\
\*\
\* Inhibit logons at all workstations? LOGONS = YES\*\
\* Load Microcode to all Devices? LMCODE = YES\*\
\* Inhibit Continuable Dumps? CMDUMP = NO \*\
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\
Figure 3-1. SYSGEN Configuration Screen

3-1

M20-4, Part II March 12,1990 Change 1

\(2\) Once the Operator Console screen is displayed and the QUEVER
(queue verification) message appears, verify that both the Wang OFFICE
volume (VI) and the system volume (SI) are mounted as \"SECURE\" by
pressing PF10 (Disks) from the Operator\'s Console. Position the cursor
at the volume name and press PF11 (Owner Information). If the volumes
are mounted as \"SECURE\" proceed to subparagraph (3); otherwise, press
PF10 (Change Restrictions) and tab over to the SECURE option and type
\"YES\". Press ENTER. These volumes must be mounted as \"SECURE\" before
running WSNSTART to ensure that special program privileges are
maintained for network and Wang OFFICE programs.

\(3\) Press PF1 to return to user mode and log on with a User ID that
has full System Security Administrator and File Access Privileges. This
User ID should be set up so that all background tasks are submitted to
Job Class A (which is the default).

\(4\) Press PF1 (Run A Program). Run the program \"WSNSTART.\" The
following background tasks will be submitted by \"WSNSTART\":
\@RMTIPC@,\$CNSTSK\$, \$DSMGR\$, \$LOGTSK\$, \@RATTSK@,\$WOAMGR\$,
\$SFMGR\$, and \$SYNDIR\$. The background task \$SYNDIR\$ controls the
directory synchronization process and will be automatically removed from
the Procedure Queue when the synchronization program has completed.

\(5\) Wait at least 10 minutes and run WSNMON. Verify that the TYMNET
transport is enabled and, if applicable, the Wangband transport. Exit
WSNMON and enter Operator Mode. Press PF12 (Telecommunications). Press
PF3 (Communications Access), and then PF2 (Allow Communications). The
\"Allow Communications\" function will require approximately 5 minutes
to complete. Release File Transfer and retrieve requests from the
appropriate queues.

\(6\) Press PF13 (Manage Workstations). The cursor will be positioned at
Unit 0. Move cursor down to the next unit. Press PF13 (Logon/Logoff
Control). Then press PF10 (Control Logon Service). Press PF2 (Allow
Logons).

\(7\) Q-SUBMIT should now be submitted to background through the
System-Minder software (see par. 9.04 below).

b\. Operator Console Messages following IPL

\(1\) FT (File Transfer) Manager Messages. The primary function of the
Wang VS CNS (Communications Network Service) is to provide a common
network interface that allows applications (such as the FT Manager and
Wang OFFICE) on one system to establish and maintain multiple
communication sessions with corresponding applications on remote
systems. Any application that uses the services of CNS must attach (by
identifying itself to the network via a network access program) to the
network before initiating or accepting a session request. Since FT is a
dedicated system task, the FT Manager tries to attach to CNS immediately
following IPL unless the FT service has been inhibited. If this occurs,
the \"attach\" process fails because CNS has not yet been started
(WSNSTART has not been run). Due to the attach failure, error messages
(\"FTM Communication with Network Server Failed\" and \"Will try to
Re-attach to Network Server when it is Running\") will be displayed on
the Operator Console and the FT service will be set to inhibited. The
messages should be removed from the Operator Console screen by
acknowledging them and FT service to all systems should be allowed from
the Operator Console (PF12 Telecommunications) after WSNSTART has been
run. (See subpar. a(5) above.)

\(2\) Procedure Incomplete Prior to IPL Messages. If WSNSTOP or WSNHALT
is not run prior to system IPL, the network and Wang Office background
tasks (such as @ RMTIPC @, \$CNSTSK\$, \$LOGTSK\$, \$WOAMGR\$, \$SFMGR\$
and \$DSMGR\$) do not complete execution. When this happens, the
Operator Console will display a message for each background task that
was still executing prior to the IPL process (i.e., \"Procedure
\$CNSTSK\$ Incomplete Prior to IPL\"). These messages should be removed
from the Operator Console screen and PF3 (Procedure Queue) should be
examined so that any background tasks showing an INCOMPLETE status can
be removed from the queue with PF12 (Remove).

c\. Network Shutdown

\(1\) From the Command Processor, press PF11 (Enter OPERATOR Mode).
Press PF13 (Manage Workstations) to inhibit logons. The cursor will be
positioned at Unit 0. Move it down to the next unit. Press PF13
(Logon/Logoff

3-2

March 12,1990 M20-4, Part 11

Change 1

Control). Then press PF10 (Control Logon Service). Press PF5 (Logoff
User At Program Completion). Verify that logon has been inhibited for
all workstations, including any remote workstations (i.e., device
numbers 254, 253).

\(2\) Press PF6 (Interactive Tasks) to see if any users are logged on to
the system. If there are users logged on, call or broadcast a message
asking users to logoff. Wait until all users are logged off the system.

\(3\) Press PF12 (Telecommunications). Press PF3 (Communications
Access). Press PF3 (Inhibit Communications).

\(4\) Place all FT and Retrieve requests on hold.

\(5\) From the Operator\'s Console, press PF3 (Procedure Queue). Verify
that the directory synchronization background task (\$SYNDIR\$) is NOT
listed in the procedure queue with a Status of Running. If the
\$SYNDIR\$ task is running, the system is exchanging directory
synchronization records with its Area Control Center or the Network
Control Center. It is recommended that the \$SYNDIR\$ procedure be
allowed to terminate normally (the procedure will drop from the queue
when the session has terminated) before proceeding to the next step.
This will prevent the directory synchronization process from restarting
when the networking tasks are restarted, and will insure that the
directory and synchronization files are closed property.

\(6\) Run WSNMON and press PF5 (Transports). Each transport should be
disabled by selecting each transport by cursor position and pressing
PF12 (Disable Transport) and then pressing ENTER. Wait for the status of
each transport to become disabled.

\(7\) Stop WSN (Wang Systems Networking) by running the program
\"WSNHALT.\" It is the mandatory method for stopping WSN because it
guarantees that all background tasks are closed and the Directory will
not be damaged. To run the WSNHALT program, the following steps will be
completed:

\(a\) Run the program WSNHALT. The following message will appear on the
terminal for approximately 10 minutes:

\"WSNHALT Procedure is running now.

Warning: IPL will cause file damage!

Do NOT IPL until this procedure finishes.\"

\(b\) When the procedure is finished the Command Processor will appear.
Check to make sure all background tasks are removed. From the
Operator\'s Console, press PF7 (Non-Interactive Tasks). View each screen
and look for the following: \@RATTSK@, \@RMTIPC@, \$LOGTSK\$, \$CNSTK\$,
\$WOAMGR\$, \$SFMGR\$, \$DSMGR\$, and \$SYNDIR\$. If any task is listed,
wait a few more minutes until it is removed from the procedure queue.
Refer to paragraph 3.05 for detailed instructions for using the
\"WSNHALT\" procedure.

\(8\) Press PF1 (Run A Program). Run the program \"WSNREORG.\" A message
that WSNREORG has already been run today may appear. If so, press ENTER
to scratch the old copy. If the program does not run successfully, check
to make sure that the system date is correct and all volumes are
mounted. If there is still a problem, note any error messages and report
the problem to the VBA (Veterans Benefits Administration) Network
Coordinator. The Network Coordinator will determine the corrective
action that should be taken and is responsible for reporting the problem
to the OASIS (Office Automation System Integration Service) Network
Administration. Under no circumstances should the VBA System
Administrator or Operator assume responsibility for restoring the
directory (@DIRECT@) and directory synchronization (@ DIRSYN @) files
from a back-up volume or the WSNREORG library. Failure to restore these
files correctly may result in directory synchronization errors that may
be propagated throughout the network.

3.04 INITIATORS (BACKGROUND TASKS)

a\. The Operator facility is used to create Initiators that begin the
execution of an active background task. The following steps are used to
create an Initiator:

\(1\) From the Operator\'s Console press PF7 (Non-Interactive Tasks).

3-3

M20-4, Part II March 12,1990

Change 1

\(2\) Press PF11 to display the Initiator Control Screen, Figure 3-2.

Initiator Control

11:01 am Friday November 14, 1986

\(1\) RETURN to display.

\(5\) Make Initiator NOT AVAILABLE for procedures.

\(6\) Control Initiator Scheduling.

\(7\) Create new Initiator.

\(8\) Delete Initiator.

Figure 3-2. Initiator Control Screen

\(3\) From the Initiator Control Screen, press PF7 (Create new
Initiator) to create a new Initiator. This screen allows the SA to
define the procedure class, dump option and modifiable data area to be
allocated for each task. For all CNS background tasks, the procedure
class should be set at A, dump option at P and modifiable data area
equal to 2048K (Fig. 3-3). Once the information is entered on the Create
Initiator Screen, press ENTER to create the Initiator. A minimum of
fourteen initiators (background tasks) should be created on VBA systems.

.\*\
\* Create Initiator\
\* 11:08 am Friday November 14, 1986\
\*

\* Highest \-\-\-- PRIORITY \-\-\-- Lowest

\* PROCEDURE CLASS . . .
A\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

\* DUMP OPTION . . . . .
P\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

\*

\* DUMP OPTIONS: Y. - Force a DUMP on program abnormal termination\
\* \'N\' - Force NO DUMP on program abnormal termination\
IP, - Dump option is to be under program control

Modifiable data area \*2048 KB

(Modifiable data size must be 64-8128K, in 128K increments)

Press:

\(1\) to return to display (ENTER) to create initiator

\(2\) to define permanent job to run

Figure 3-3. Create Initiator Screen

b\. The following nine Initiators are required for networked OFFICE,
CNS, and System-Minder software:

Task Description

\@RMTIPC@ Remote Inter-process Task for Remote Logons

\$CNSTSK\$ Network Access Task

\$LOGTSK\$ Task to read and write network records to the current log
file

3-4

March 12, 1990 M20-4, Part 11\
Change 1\
\
Task Description\
\
\@RATTSK@ Remote Attachment Task\
\$WOAMGR\$ Local Mail Delivery Task for OFFICE

\$SFMGR\$ Remote (Store and Forward) Mail Delivery Task for OFFICE

\$SYNDIR\$ Directory Synchronization Task

\$HSKPING\$ Wang OFFICE Purge (Housekeeping) Task

Q-SUBMIT System-Minder Task

Two of the above Initiators (\$SYNDIR\$ and \$HSKPING\$) will only run
on a periodic basis. The \$SYNDIR\$ task will automatically be submitted
when modifications to the Directory File (@DIRECT@) are being
synchronized (disseminated) throughout the network. The \$HSKPING\$
Initiator is submitted by the Node Administrator when the OFFICE
Housekeeping (Administrative Functions) menu selection is executed. Both
of these Initiators will automatically be removed from the Procedure
Queue upon program completion.

c\. The following dedicated system tasks will be running in background
on the VS when a communication file is used during the IPL process.
Dedicated system tasks are identified from the Operators Console
Non-Interactive Tasks Screen (PF7).

Task Description\
\[SYSTSK\] System Task\
\[SHARER\] Sharer Task\
\[TSKMGR\] Dynamic Task Manager\
\[PRTTSK\] Printer Task

\[LOGGER\] Security Logger Task

\[TWOLIH\] Secondary Level Interrupt Handler

\[FTMTSK\] File Transfer Manager

\[SESMGR\] Session Manager

3.05 NETWORK STARTUP AND SHUTDOWN SUMMARY

The following is a summary of the network startup and shutdown
procedures. These procedures should be printed and posted by the CPU.
The procedures must be understood and followed by all personnel
responsible for starting and stopping the system. The procedure using
WSNHALT is mandatory. For efficient operations the WSNHALT and WSNREORG
procedures should be run daily and must be completed before the daily
backup and disk reorganization tasks have been scheduled through the
System-Minder software (see par. 9.04 below).

3.06 NETWORK STARTUP AND SHUTDOWN SUMMARY (USING WSNHALT) POST AT THE
CPU

a\. Network Startup Summary

\(1\) Perform and IPL on the system using the communications
configuration file (@CNSCOM@ in \@SYSTEM@). (Approximately 12 minutes.)

\(2\) Verify that both the Wang Office volume (VI) and the system volume
(SI) are mounted as \"SECURE.\" If the volumes are mounted as \"SECURE\'
proceed to subparagraph (3); otherwise, press PF10 (Change
Restrictions), and tab over to the SECURE option and type \"YES\". Press
ENTER.

\(3\) Logon as a System Security Administrator.

\(4\) Press PF1 (Run A Program). Run the program \"WSNSTART\".

3-5

M20-4, Part 11 March 12,1990

Change 1

\(5\) Wait at least 10 minutes and run WSNMON. Verify that the TYMNET
transport is enabled and, if applicable, the Wang band transport. Then
press PF12 (Telecommunications) from the Operator\'s Console. Press PF3
(Communications Access), and then PF2 (Allow Communications). The
\"Allow Communications\" function will require approximately 5 minutes
to complete. Release File Transfer and retrieve requests from the
appropriate queues.

\(6\) Press PF13 (Manage Workstations). The cursor will be positioned at
Unit 0. Move cursor down to the next unit. Press PF13 (Logon/Logoff
Control). Then press PF10 (Control Logon Service). Press PF2 (Allow
Logons).

\(7\) Q-SUBMIT should now be submitted to background through the
System-Minder software (see par. 9.04 below)

b\. Network Shutdown Summary

\(1\) Press PF13 (Manage Workstations) from the Operator\'s Console to
inhibit logons. The cursor will be positioned at unit 0. Move it down to
the next unit. Press PF13 (Logon/Logoff Control). Then press PF10
(Control Logon Service). Press PF5 (Logoff User At Program Completion).

\(2\) Press PF6 (Interactive Tasks) to see if any users are logged on to
the system. Insure that all users are logged off the system.

\(3\) Press PF12 (Telecommunications). Press PF3 (Communications
Access). Press PF3 (Inhibit Communications).

\(4\) Place all File Transfer and Retrieve requests on hold.

\(5\) From the Operator\'s Console, press PF3 (Procedure Queue). Verify
that the directory synchronization background task (\$SYNDIR\$) is NOT
listed in the procedure queue with a Status of Running. If the
\$SYNDIR\$ task is running, it is recommended that the procedure be
allowed to terminate normally, (the procedure will drop from the queue
when the session has terminated) before proceeding to the next step.

\(6\) Run WSNMON and press PF5 (Transports). Each transport should be
disabled by selecting each transport by cursor position and pressing
PF12 (Disable Transports) and then pressing ENTER. Wait for each
transport to be disabled.

\(7\) Run the program WSNHALT. The following message will appear on the
terminal for approximately 10 minutes:

\"WSNHALT Procedure is running now. Warning: IPL will cause file damage!
Do NOT IPL until this procedure finishes.\"

When the procedure is finished the Command Processor will appear. Verify
that the background tasks have been completed.

\(8\) Run the program \"WSNREORG\". A message that SWNREORG has already
been run today may appear. If so, press ENTER to delete the old copy. If
the program does not run successfully, note any error messages and
report the problem to the VBA Network Coordinator immediately.

3.07 DESCRIPTION OF WSNHALT PROCEDURE

a\. The WSNHALT procedure will run on VBA systems in lieu of the WSNSTOP
procedure. WSNHALT will assure that all background tasks are stopped,
before the operator shuts the system down. The Directory will be
protected.

b\. The WSNHALT procedure requires the following files:

\(1\) READVTOC in USERSUBS on SI

\(2\) DATE in USERSUBS on SI

3-6

March 12,1990 M20-4, Part 11

Change 1

\(3\) PAUSE in USERSUBS on SI

\(4\) WSNHALT in \@SYSTEM@ on Si

\(5\) LOGSCR in \@SYSTEM@ on SI

\(6\) WSNSTOP in \@SYSTEM@ on SI (Wang\'s procedure)

c\. WSNHALT runs the LOGSCR procedure which deletes WSN log files from
library @ LOG@ that are over 2 days old. If log files must be retained
for more than 2 days, the &DAYSOLD variable in the LOGSCR procedure can
be modified to meet the station\'s needs.

3-7