The CANCEL command is used to immediately terminate a job in execution, a TSO user, a MOUNT command or output processing for a job. Examples are:

The DISPLAY command is used to obtain information about system IO, job and console status, and time of day. You can display jobs in execution, device status and allocation, status of hardware configuration, time and date, number of active jobs, tso users, initiators, VTAM network activity and functions, dump options and system requests. Examples are:

The FORCE command is used when the CANCEL command fails. This command allows the operator to force termination of a mount command, force termination of a job in execution, force termination of external writer allocation, force termination of output processing for a job or force termination of a terminal session. Examples are:

The MODIFY command is used to change the existing parameters of an existing job, TSO/VTAM, or an external writer. MODIFY is also used to change the characteristics of a job. The specified parameters are modified only if the programmer has set the proper indicators. Examples:

The START command is used to start specific jobs from the console, start an I/O device (reader, writer), or to start online programs such as CICS, TSO, VTAM etc. The START command starts a cataloged procedure located in the "proc library" where the JCL for the procedure is stored. Examples are:

The SWAP command is used to move a volume to another device. For example, if a tape unit goes down or is receiving I/O errors, the operator has the choice of either canceling the job or swapping to another device to continue processing. Example:

The SWITCH command is used to manually switch the recording of SMF data from one data set to another. (SYS1.MAN1, SYS1.MAN2, SYS1.MAN3)

The VARY command is used to control assignments and configurations of I/O devices, channels, or CPU’s. By using the VARY command, the operator has the ability to vary I/O devices on or offline, vary channels on or offline, vary processors on or offline, change MCS assignments or place a path on or offline. Examples are:

When varying a device offline it is necessary to execute the DEALLOC procedure immediately after. Example:

On MVS we are running with a master console (device A00) and an alternate console (device 1E0). If for some reason the master console malfunctions, MVS should automatically begin using the alternate console as the main console. At anytime you can display the current console assignments by typing the command:

Whenever the master console is lost, it automatically switches to the alternate console (1E0). Display the current console assignments. On 1E0, type:

When the problem with the original master console has been remedied, vary A00 to become a console again. On 1E0, type:

Make the original console (A00) the master console again. On E0, type:

Display the current console assignments again. Type:

When the master console switches from 1E0 back to A00 the following message is displayed.

02E PRT2 TQ IBM 4245 1^st floor I/O

21D PRT3 BCD IBM 4245 room 205

210 PRT4 HIJ Xerox 4135 room 205

1. PDQ
2. QPD
3. PD
4. DP
5. S
6. F
7. O
8. E
9. C
10. U
11. T
12. L
13. XY
14. R

This is the general setup of the initiators and job class assignments after an IPL is performed. These initiators can be started, drained and the classes they service can be changed by using JES commands. This is the initial setup designed to give the best response time to our online users and the BISON library system. Initiators 1 through 4 are drained between the hours of 8am and 5pm, and then an automatic command will start these 4 initiators daily at 5pm. Weekend operations must start initiators 1 thru 4 on Saturday and Sunday when there are production jobs to be run. Type:

1. UBMVS is a guest virtual machine of UBVM. The UBMVS virtual machine is autologged by UBVM at IPL time and MVS is automatically IPL’ed. If for some reason MVS is down without UBVM being down, it is not necessary to IPL UBVM, but just autolog UBMVS. At the UBVM operator’s console, type:

2. Wait until the following messages appear on the MVS console.

IEA101A SPECIFY SYSTEM PARAMETERS FOR OS/390 01.02.00 JBB6602

3. At the UBVM operator’s console, execute the procedure MVSCPCMD. This procedure will execute a couple of SET commands. Type:

MVSCPCMD

4. At the MVS console, the following messages are still displayed.

IEA101A SPECIFY SYSTEM PARAMETERS FOR OS/390 01.02.00 JBB6602

Press the ENTER key.

5. The following message then appears.

IEE600I REPLY TO 00 IS;

6. After about 3 minutes, the following message should appear in white.

*nn $HASP426 SPECIFY OPTIONS – JES2 OS 1.1.0

Type:

R nn,WARM

This will perform a WARM start for JES2 and recover all queues.

$HASP400 ENTER REQUESTS

To initiate JES2 processing, type:

$S

Failure to perform this step will result in the system sitting in an IDLE state. (Entering a $S a second time will not hurt anything.)

7. After approximately 3-5 minutes, he following message will be displayed in white.

*nn IEFTMS0 REPLY ‘U’ FOR CA-1 VERSION-5.2 INITIALIZATION OR ‘HELP’

Type:

R nn,U

8. One of the following messages will appear.

IEFTMS2 DATE MAY BE INCORRECT

*nn IEFTMS4 VERIFY DATE=yyddd

Verify that it is the correct date, and type:

R nn,U

If several days have elapsed since a previous IPL then four responses of ‘U’ may be required or

IEFTMS7 IPL DATE MORE THAN 8 DAYS FROM LAST IPL

*nn IEFTMS8 VERIFY DATE=yyddd

Verify that it is the correct date, and type:

R nn,HIGHDATE

9. After all of the subsystems (TSO, ROSCOE, STRTMUFD, STRTMUFP, STRTMUFT, STAM, CICSB, CICSD,CICSL, CICSP, CICST, CA7ICOM, or UCC7ICOM, CA7MAINT, HCP and NETVIEW) have successfully started automatically, type:

$DU

If any of these subsystems fail to start, bring them up manually.

10. Reboot the BIRD system. Be sure to IPL all four (4) machines. See the BIRD Overview section for detailed instructions. Also for information purposes this step can be performed anytime after VTAM is up.
11. When MVS is IPL’d, the operating system puts a hold on all jobs that were in the input queue to prevent them from starting and abending before all the MUFs are up. As soon as all the MUFs are operational release the jobs from the input queue. Type:

$A A,ALL

12. If the 3290 window A1D fails to come up with the UB logo, then issue the following commands on the UBVM console. Type:

VARY ONLINE A1D

VTAM V NET,ACT,ID=T041A1D

This should make the screen available for use by CA7.

13. Be sure to log on the MVS Netview console, CONSLOG console and CA7 console.
14. If the alternate console should fail to come up, for example if you notice the VM logo is displayed on the alternate console, type the following commands.

1. On the MVS console, shutdown each currently active CICS partition. Currently we have CICSB, CICSD, CICSL, CICSP, and CICST. Type:

S STOPCICS

This procedure will terminate all CICS regions. If for some reason you don’t want to terminate all of the CICS regions, you can terminate any region with the following procedure. Type:

S ENDCICSn

Where n = B for CICSB

D for CICSD

L for CICSL

P for CICSP

T for CICST

2. Several messages will be displayed. Some of the normal messages displayed are:

• + DFH1701 – C.I.C.S. IS BEING TERMINATED
• + DFH2305I TERMINATION OF VTAM SESSIONS BEGINNING
• + DFH2316I – VTAM ACB IS CLOSED
• IEC161I 152-061 applname,CICS,ADACTASG,,,ADISV.

• IEC161I ADISV.ACCTSGN.DATA,CATALOG.VUBMCAT
• + DFH1799 – DBDCCICS TERMINATION OF CICS IS COMPLETE
• $HASP395 applname ENDED
• $HASP150 applname OUTGRP=1.1.1 ON PRINTER2 nn

1. Shutdown the Ingres Gateways. If these are active, there will be a started task named INETD1 and INETI1. To terminate these tasks, type:

P DNET

P INET

Note: If these tasks are active, they will prevent the mufs from shutting down properly. You can tell if this is the case, if you do a status command on the muf. You can check the status of a muf, with the command:

F STRTMUFD, COMM STATUS

or

F STRTMUFP, COMM STATUS

or

F STRTMUFT, COMM STATUS

2. Shutdown Multi-user mode, type:

S STOPMUFD

3. The following messages will be displayed.

$HASP100 STOPMUFD ON STCINRDR

$HASP373 STOPMUFD STARTED

+DB13105I – COMM EOJ REQUEST ACCEPTED

$HASP395 STOPMUFD ENDED

+DB00202I – MULTI-USER DISABLED

$HASP395 STOPMUFD ENDED

4. Shutdown the production multi-user facility. Type:

S STOPMUFP

5. The following messages will be displayed:

$HASP100 STOPMUFP ON STCINRDR

TSS900W 153 J=STOPMUFP A=*BYPASS* T= F=STC

TSS730I SECURITY BYPASS ACTIVE FOR JOB=STOPMUFP ACID=*BY

$HASP373 STOPMUFP STARTED

+DB13105I – COMM EOJFREE REQUEST ACCEPTED

$HASP395 STOPMUFP ENDED

STRTMUFP:240:2:DB00202I – MULTI-USER DISABLED

STRTMUFP:240:2:DB06001I – SUBTASK I/O COUNT = nnnnnnnn

$HASP395 STOPMUFP ENDED

6. STRTMUFT need not be shutdown per Lou Scott. If you do shut STRTMUFT down, be sure to bring it back up after the backups.
7. Terminate ROSCOE processing. Type:

F ROSCOE, SHUTDOWN NOW

8. Some of the messages which will appear are:

• ROS315I SHUTDOWN INITIATED BY RO ON CONSOLE
• ROS137I TOTAL ROSGBL SRB’s ISSUED = 00000000
• ROS138* TOTAL ROSGBL SRB’s RETRIED = 00000000
• 00- ROS093I ROSGBL CSA STORAGE FREED AT 0974000 FOR
• ROS300I SHUTDOWN COMPLETE
• - $HASP395 ROSCOE ENDED

1. Terminate ICOM (Independent Communications Manager) task. The following outstanding message should appear at the top of the display.

Nn UCC7.574 ENTER ICOM DATA

Type:

R nn,STOP

where nn = reply id

2. The following messages will appear.

IEE600I REPLY TO nn IS;STOP

+UCC7.578 SASSJES2 SUBTASK ENDED. TCBCMP = 00000000

+UCC7.578 SASSICSM SUBTASK ENDED. TCBCMP = 00000000

+UCC7.578 SASSICTR SUBTASK ENDED. TCBCMP = 00000000

$HASP395 ICOM ENDED

$HASP250 ICOM PURGED

3. To terminate CA7 (Automated Production Control System), logon CA7 from an MVS VTAM terminal screen on the CA7 PC. Type:

UCC7

/LOGON MASTER

/SHUTDOWN,Z1

The Z1 option will cause CA7 to shutdown immediately even if there are still terminals logged onto CA7.

4. The following message will appear on the CA7 console.

Enter /SHUTDOWN to verify shutdown.

Press the ENTER key to continue the shutdown.

5. The following messages will appear on the MVS console.

+UCC7.V266 I V044 (0334) DISCONNECTED DSN = SYS2.CA7.PRO

+UCC7.V266 I V044 (0334) DISCONNECTED = SYS2.CA7.PRO

+UCC7.V266 I V044 (0334) DISCONNECTED DSN = SYS2.CA7.PRO

+UCC7.V267 I V040 (0660) DISCONNECTION COMPLETED SUCCESS

+UCC7.928 – LOG DATASET CLOSED

+UCC7.510 – UCC – SEVEN SHUTDOWN COMPLETE

6. Shutdown STAM (Shared Tape Access Method). Type:

F STAM,STOP

7. Shutdown TSO (Time Sharing Option). Type:

P TSOAUTO

If there are any TSO users logged on, you will receive the following message:

*nn IKT010D nnnn USER(S) ACTIVE, REPLY ‘SIC’ OR ‘FSTOP’

Type:

R nn,FSTOP

8. Reply to the outstanding message TCAS TERMINATION IN PROGRESS –

SPECIFY ‘U’ OR ‘DUMP’. Type:

R nn,U

9. The following messages will be displayed.

• IKT006I TCAS ENDED
• $HASP395 TSO ENDED

0. $HASP250 TSO IS PURGED

1. Shutdown HCF (Host Communications Facility), Type:

R nn,CLOSE IMMED

in response to the CHF001A HCF/LCV CONTROL COMMAND message.

2. Terminate MVS NETVIEW operations. From the MVS NETVIEW console, type:

CLOSE IMMED

3. Shutdown VTAM (Virtual Terminal Access Methods). Type:

Z NET,QUICK

4. This may take 3 to 5 minutes. Some of the messages you may receive are:

IST097I HALT ACCEPTED

IST133I VTAM TERMINATION IN PROGRESS

IST617I DEACTIVATION IN PROGRESS FOR UBMVSCPU

IST617I DEACTIVATION IN PROGRESS FOR M40

IST617I DEACTIVATION IN PROGRESS FOR CENCDRM

IST105I M40 NODE NOW INACTIVE

IST105I CENCDRM NODE NOW INACTIVE

IST105I UBMVSCPU NODE NOW INACTIVE

IST105I M41CDRM NODE NOW INACTIVE

IST105I ISTCDRDY NODE NOW INACTIVE

IST105I APPLDEF NODE NOW INACTIVE

$HASP208 TPEND SCHEDULED FOR LOGON1 SNA, VTAM, 04

IST105I M41CDRSC NODE NOW INACTIVE

IST105I ALFCLU NODE NOW INACTIVE

IST105I APPLS NODE NOW INACTIVE

$HASP097 LOGON1 IS DRAINED

IST105I TSOTERM NODE NOW INACTIVE

IST105I DEF7171 NODE NOW INACTIVE

IST105I P041040 NODE NOW INACTIVE

IST105I SNA NODE NOW INACTIVE

IST105I UBNCP NODE NOW INACTIVE

IST526I ROUTE FAILED FROM 41 to 42 – DSA 11

IST526I ROUTE FAILED FROM 41 to 42 – DSA 12

IST526I ROUTE FAILED FROM 41 to 42 – DSA 40

IST526I ROUTE FAILED FROM 41 to 42 – DSA 42

IST105I B80-S NODE NOW INACTIVE

IST105I ISTGROUP NODE NOW INACTIVE

IST105I ISTGROUP NODE NOW INACTIVE

IST412I VTAM COMMAND PROCESSING TERMINATED

IST412I VTAM COMMAND PROCESSING TERMINATED

$HASP395 NET ENDED

IST102I VTAM IS NOW INACTIVE

$HASP250 NET IS PURGED

5. Shutdown RMF (Resource Measurement Facility), type:

P RMF

6. The following messages will be displayed.

ERB102I ZZ : TERMINATED

$HASP150 RMF OUTGRP=1.1.1 ON PRINTER1 nn RECORDS

ERB102I RMF: TERMINATED

$HASP160 PRINTER 1 INACTIVE – CLASS=AJ

$HASP150 RMF OUTGRP=2.1.1 ON PRINTER1 nn RECORDS

$HASP160 PRINTER1 INACTIVE – CLASS=AJ

$HASP395 RMF ENDED

$HASP250 RMF IS PURGED

7. Halt the operating system. Type:

Z EOD

This command will record statistics and then stop the system. The following message will be displayed.

IEE334I HALT EOD SUCCESSFUL

8. From the UBVM console, force off UBMVS. Type:

A Stand-Alone Restore (SAR) is performed whenever the MVS system is both not operational and not ipl-able. SAR is only done by someone from Technical Services.

Before any type of recovery action such as a Stand-Alone Restore is performed, as much information as possible must be gathered for the Systems staff to be able to debug the problem. This information is to be recorded in our REMEDY database. When MVS crashes, the operator should minimally record specific items. Some of these items are:

1. What is on the master console? What message identifiers and messages are present?

2. Is the console operational?

3. What was the last MVS action by an operator and how close was this action to the outage?
4. Are there (or were there) any hardware device problem messages on the VM console?

Incremental backups are taken daily and full-volume backups are taken weekly. In addition, the sysres volume, OS9RES, is full-volume-dumped daily in job BKPRES00. Stand-Alone Restore uses only full-volume dumps.

Backup listings may, depending on the time of day, be located in the first floor printer area (office 116C).

Job BKPRES00 is run daily and full-volume dumps the sysres volume. If you are restoring the sysres volume it is usually best to find the most recent BKPRES00 listing and determine which backup cartridges to use for the SAR. Copy the tape volume numbers (keep them in sequence) from this listing.

If you choose not to use BKPRES00 output to restore from, job BKPFDR contains a listing of the latest FDR/ABR backup tapes for each dasd volume. Locate the dasd volume (to be restored). Copy the tape volume numbers (keep them in sequence) from the same line (top line) as the dasd volume; this is always the most recent full-volume backup (but it may be as much as a week old).

Ask the computer operator to retrieve the desired cartridges.

Weekly full-volume dumps (i.e., the cartridges) are stored in a safe in Fronczak Hall. All other backups (including the daily BKPRES00 cartridges) are in the tape library.

MVSP03 (F1E), ADMN03 (F16), BSON33 (D03), RFP003 (FC2) & RF0003 (FE2) contain SAR IPL text.

SAR IPL text is also on the FDR/ABR installation tape maintained in office 335 with the FDR/ABR documentation. It is much easier and faster, however, to use the customized SAR IPL text on dasd.

1. Logon UBMVS from the UBVM logon screen (use console-area VM terminal) and enter the following commands. Type:

LOGON UBMVS (no password is required)

ACC (NOPROF

2. At least one cartridge drive is required. 791 & 792 (991 & 992) are specified in the SAR IPL text but may be changed during the SAR IPL; they must be assigned to the SAR IPL from the UBVM console. On the UBVM console (if 991/992 is in-use, select different drives), type:

VMTAPE ALLOC 791-792 (RDEV 791-792 FOR UBMVS)

Sometimes this command fails with a reason of "unauthorized", do not worry about it. Continue with:

VMTAPE STAM VARY 791-792 NOTAVL UBVM

This keeps VM from trying to use the drives during the SAR.

3. Insert the first of the cartridges being restored in the allocated tape drive.
4. Load the stand-alone dump program. Type:

#CP IPL F1E CLEAR (or, address F16 or D03)

This will take about 3 seconds and produces no messages.

5. Go to the MVS console usually (A00) and reply with the requested information. All fields are described and documented in the FDR/ABR manual (located in office 335) in Section 30, beginning on page 301.

You’ll need to know the address of the dasd volume being restored to and the tape drive address, if other than 791-792 / 991-992.

Merely depress "ENTER" for options you do not wish to change.

Console messages will tell when to mount subsequent tapes. A message on the console will indicate a successful restore.

6. Return to the UBVM VM logged-on account UBMVS and type:

#CP LOGOFF

7. Change the MVS IPL address if desired.

Logon to the VM system with your user account.

Enter: TKSUTIL ADMIN UBMVS

And, then your password.

Change the address of the sysres volume.

Logoff

8. Autolog UBMVS from the UBVM console.

A Standalone dump should be performed whenever MVS is not operational (is "hung") for whatever reason. If an unscheduled MVS IPL is done, a standalone dump must be taken first.

Before any type of recovery action such as an IPL or a Standalone dump is performed, as much information as possible must be gathered for the Systems staff to be able to debug the problem. This information is to be recorded in our REMEDY database. When MVS crashes, the operator should minimally record specific items. Some of these items are:

1. What is on the master console? What message identifiers and messages are present?

Copy the pertinent message identifiers and messages.

2. Is the console operational?

Are there any "symptom" symbols in the lower left-hand corner (boxed 4 with an A over a dash connected to a solid box is normal; all other symbols are abnormal)?

If the console is not operational, is the alternate MVS console operational?

3. What was the last MVS action by an operator and how close was this action to the outage?
4. Are there (or were there) any hardware device problem messages on the VM console?

Information you need to be aware of is:

Also there are four initialized, non-labeled cartridges in the tape library. Currently, these four tapes are located on the top shelf of the Systems 8000 series of cartridges located in the main computer room. They are affixed with external labels of MVSDP1, MVSDP2, MVSDP3 and MVSDP4 (probably only one cartridge will be needed for actual dump).

1. Logon UBMVS from the IBM P200 console UB logon screen which is next to the IBM 9-track tape drive and enter the following commands.

LOGON UBMVS

#CP SPOOL CONS START TO TKSCMR

#CP TRACE ALL

The following message will be displayed:

HCPTRI1027I An active trace set has turned RUN off.

#CP TRACE RUN

#CP TRACE END ALL

The following message will be displayed.

Trace ended

#CP SPOOL CONS STOP CLOSE

2. A cartridge drive is required. 791 (991) is specified in the SAD IPL text but it may be changed during the SAD IPL; it must be assigned to the SAD IPL from the UBVM console. On the UBVM console (if 991 is in-use, select a different drive), type:

VMTAPE ALLOC 791 (RDEV 791 FOR UBMVS)

NOTE: Type in the complete line above including the parentheses and data within the parentheses.

The following message will be displayed:

VMTACL183I Allocating UBMVS 0791

Then insert unlabeled cartridge (MVSDPn) in drive 791.

3. Go back to the P200 console where you logged onto UBMVS and type:

#CP CPU 00

The following message will be displayed:

HCPCCP1454I CPU 00 DOES NOT EXIST

4. Type:

#CP SYS STORE STATUS

The following message will be displayed:

STORE COMPLETE

5. Load the stand-alone dump program. Type:

#CP IPL F1C

or

#CP IPL F24

The following message will be displayed:

The virtual machine is placed in CP mode due to a SIGP STOP and store status from CPU 01.

6. Go to the MVS console (A00) and press the ENTER key. The following messages will appear on the MVS console.

AMD083I AMDSADUMP: STANDALONE DUMP INITIALIZED

AMD001A SPECIFY OUTPUT DEVICE ADDRESS(1)

Type the cartridge address where dump tape is loaded (probably 991)

The following messages will appear:

AMD101I OUTPUT DEVICE: 0991

SENSE ID DATA: FF 3480 22 3480 22 BLOCKSIZE: 29,120

AMD011A TITLE=

Type a unique, informative title line. (Include the date & time of dump in the title line). Example: test dump – date & time

Note: You will see LED light activity on the tape drive after the next message is displayed.

AMD005I DUMPING OF REAL STORAGE IN PROGRESS

AMD005I DUMPING OF REAL STORAGE COMPLETED

At this point several other messages will be displayed during the dump process.

Example:

AMD095I Buffers written = nnnnnn

It is important to look up any messages in the MVS Error Messages Volumes which need an action or decision. These messages are suffixed with the A or D indicator. The I indicator just indicates that it is an informational type message.

It is possible that an additional tape will be required for the dump, if so the following message is displayed.

AMD004A End of Reel – Mount an additional output tape.

Mount another tape and dump will continue processing.

If the screen fills, the following message is displayed.

AMD029D REPLY W TO WAIT AFTER NEXT FULL SCREEN, ELSE REPLY N, REPLY =

Enter W for the reply which just means to fill up another screen of information and pause again.

AMD056I DUMPING OF VIRTUAL STORAGE COMPLETED

AMD104I DEVICE VOLUME USED DATA SET NAME

1 0991 *TAPE* 1 N/A

This indicates successful completion of the dump. Also the tape will rewind and unload at this point. Be sure to label the tape with such information as title of dump, date & time and operator initials. If these messages do not appear, take another standalone dump with another tape.

7. Return the MVSDPn cartridge to the tape library.
8. Make an entry in REMEDY stating that a stand-alone dump was taken, noting the tape label (e.g., MVSDP1) along with the name of the person authorizing the use of the stand-alone dump.
9. Return to the UBVM logged-on account UBMVS and type:

#CP LOGOFF

10. Autolog UBMVS from the UBVM console as is normal and follow the MVS IPL procedures or follow special directions of shift supervisor or the systems programmer.

As you know, messages on the MVS console often scroll off the top of the screen before the operators have a chance to read them. To provide a way to redisplay these messages, a window is used on the PC located to the right of the MVS console using the IBM Personal Communications software. SDSF is a utility of MVS which allows the display and search of the MVS log. See the section on PC’s for basic information on using the IBM Personal Communications software.

VTAM will autolog SDSF onto session E of the IBM Personal Communications software on the PC. However if for any reason it is not logged on use the following procedure.

1. With the mouse, select Programs, then IBM Personal Communications and then session E. The MVS logon logo will appear.
2. Type:

TSO CONSLOG

3. The screen will change and the cursor will be positioned in the PASSWORD field of the TSO sign on screen. The password is not checked, enter any letter and press the ENTER key.

1. Use the PF7 key to scroll the log back and the PF8 key to scroll forward. Note the display will not scroll unless the PF7 or PF8 key is used.
2. To scroll to the top or bottom of the log place the letter M at the COMMAND INPUT === > prompt at the top of the display. The tab key will quickly bring you to the COMMAND INPUT === > line of the display. Note the log may be several days long. The date is entered into the log every day at midnight. (See SEARCH)
3. To the right of the COMMAND INPUT === > prompt and on the same line you will find SCROLL === > area. If you enter the word:

To search for a particular character stringer enter:

Where xxxxxx = the string you wish to locate

Note: The search will only advance forward from the current position of the cursor. Only an exact match will be found. If there are spaces in the string you wish to find, enclose the string in quotes. To search backward, type:

Some additional commands are:

Frequently, you will want to start of the bottom of the log and scroll backwards.

To turn on auto-update mode, click on the SDSF window. Next to the COMMAND INPUT field, type &# (where # is any number from 1-9 which will be the amount of time between updates in seconds).

Example: &5 (automatically updates the screen every 5 seconds)

To turn off auto-update mode, click on the SDSF window. Click on the ASSIST button on the top menu bar on the SDSF display. A drop down menu will appear, select DISPLAY POP-UP KEYPAD and click on it. Another menu will appear, select RESET and click on it. Then click on PA1. This sequence will turn off auto-update mode. Note: The DISPLAY POP UP KEYPAD won’t disappear until you quit it.

BIRD is the University’s online touchtone registration system.

NORMAL BIRD HOURS

Mondays 0830-2100

Tuesdays 0830-2100

Wednesdays 0830-2100

Thursdays 0830-2100

Fridays 0830-2100

Saturdays 1200-2100

Sundays 1200-2100

The BIRD system is located in room 116A in the left back portion of the room in a vertical cabinet with CCS Computer Communications Specialist, Inc. on front of unit. Actually if you entered the room from the door to the back stairwell, you would walk right into the unit. On the front of the unit is a window allowing you to view the monitor. Approximately half way down is a 3 inch gray area that by pulling down the top of this area you can reach in and slide the keyboard out. To access the machines open the front door of unit which opens on the right side. Machines are labeled from top to bottom 1 through 4. To access the switches on these units a key must be used in the keylock opposite the machine number id. The key is clipped to side of cabinet to the left of the monitor. Insert the key to unlock and drop down the front panel cover. You will then see a RESET, KEYLOCK, and POWER switch. RESET is the only switch you should ever need concern yourself with.

This system must be IPL’d whenever MVS is IPL’d.

The IVR console controls all four (4) production machines through a single display tube and keboard. Control can be switched from one system to another by pressing the CNTL (Control) key releasing it and then pressing 1, 2, 3 or the 4 key. A 01, 02, 03, or 04 will appear in the upper right corner of the display screen indicating which of the four systems are being monitored.

To IPL the IVR system press the RESET button located behind the front panel door. If necessary a power cycle can be used to restart the system, however RESET should be tried first.

Although the IVR system is basically a PC and can be IPL’d with CTRL+ALT+DEL, it should never be IPL’d for production using this method.

Call the IVR system on a touch tone phone at 645-7800. Following the instructions given to you by the IVR system, enter any student number or PIN number. If the IVR system responds "YOU NEED ASSISTANCE" the system has determined that the student number and PIN number are not on record on the mainframe and therefore the path between the phone line and the host system is intact and functional. One important point to stress here is that this procedure can only be performed during the regular BIRD hours. If you dial this number at other times of the day, you will get a constant ringing.

Using the following table any suspect phone line can be tested by dialing its phone number and repeating the above procedure.

In order to trace or attempt to pin down problems, it is sometimes necessary for operators to log in to BISON through an MVS terminal and check if BISON appears to be working properly. He/she can check if other libraries are up through the option cats. This allows them to go to UB’s, BING’s or CRLC libraries. Usually a code number is not needed, but it seems that sometimes a code is requested. Mark Ludwig has given us a code to use for all of Operations. The code number is

TCPIP and TCPIPL are started automatically at IPL time but if problems are encountered and it is necessary to restart either of these procedures, here’s the procedure.

To restart TCPIPL, type the following command:

When TCPIPL ends the following message will be displayed.

To start TCPIPL up again, type:

To restart TCPIP, issue the following command to first stop TCPIP.

Three other started tasks will be stopped automatically. They are:

The following messages will be displayed on the system console.

Restart TCPIP, type:

FTPSERVE, PORTMAP and MVSNFS will be started automatically. The following are some of the messages that will be displayed.

See URL http://acsnt.cit.buffalo.edu/calllist/

And also http://acsnt.cit.buffalo.edu/staff