Service Manuals, User Guides, Schematic Diagrams or docs for : IBM share SHARE_61_Proceedings_Volume_1_Summer_1983 B549 OK, VM Is Installed, Now What; Patterson
<< Back | HomeMost service manuals and schematics are PDF files, so You will need Adobre Acrobat Reader to view : Acrobat Download Some of the files are DjVu format. Readers and resources available here : DjVu Resources
For the compressed files, most common are zip and rar. Please, extract files with Your favorite compression software ( WinZip, WinRAR ... ) before viewing. If a document has multiple parts, You should download all, before extracting.
Good luck. Repair on Your own risk. Make sure You know what You are doing.
Image preview - the first page of the document
>> Download B549 OK, VM Is Installed, Now What; Patterson documenatation <<
Text preview - extract from the document
iSHAREii:
Refer to Firure 20
=
SHARE SESSION REPORT
Our Marketing Division consists of System Engineers (SE2 and
Marketing Representatives. The Marketing Representati.ve is. respon- 61 B549 Ok, VM is Installed, Now What? 150
sible for sales and the SE assists customers in installation plan-
ning and procedures. SHARE NO. SESSION NO. SESSION TITLE ATTENDANCE
CMS Larry Graziose BAM
PSRs and CEs work in the Field Engineering Division. PSRs
PROJECT ';'J.:oo,;).Lvn CHAIRMAN INST. CODE
provide software support and the CE is responsible for hardware
performance. Bank of America, 1455 Market St., San Francisco, CA 94103 (415) 622-1881
In addition we have added the IBM Support Centers. This is SESSION CHAIRMAN'S COMPANY, ADDRESS, AND PHONE NUMBER
an expedited software support service comprised of over 3,000 people
across the country with a commitment to provide quality service
to each of IBM's many customers. The development of remote support
has proved to be an outstanding achievement for IBM. I sincerely
hope the information I have provided will assist you in making the OK, VM IS INSTALLED,
Support Center work for you!
NOW WHAT?
Tips and Techniques for Running a VM System. and Changing
N Cp's Page, Spool, T-Disk, and Free Storage Areas
~ Figure 20
...:I
IBM
SUPPORT CENTER August 23, 1983
SHARE Ses s ion 8549
(
\ IBM
IBM
CUSTOMER Ben Pettersson
Boston M&D Office
IBM Corporation
\ LOCAL ."
\ FIELD " IB~1 / 610 Lincoln Street
Waltham, MA 02254
LOC\L
\ E:\GI:\EERING MARKETING;'
\",-
"
'..""
// VM New Users Project
". -----------/" Permission is granted to SHARE, Inc. to publish this presentation
paper in the SHARE proceeding in SHARE 6,. IBM retains the right
to distribute copies of this presentation to whomever it chooses.
4/C/rcg/3
Reducing the SIZE of TEHP and T-DISK Areas
INTRODUCTION TAILORING AUTOLOG1'S PROFILE EXEC
This presentation is primarily aimed at VM/SP customers who have" in- In a SIPOE system, when VM is IPLed, the AUTOLOGI machine is auto-
stalled the VH/SP System Installation Productivity Option-Extended matically logged on, and the following functions occur:
(SIPOE). and who are running VM "as is" with little or no tailoring.
I will be covering the following topics today: The virtual machine is put to sleep for ten seconds to allow
the VH Operator to force off the AUTOLOGI machine i f something
MISCELLANEOUS TOPICS is seriously wrong with its PROFILE EXEC.
Tailoring the AUTOLOGI Machine's PROFILE Autolog various SIPOE virtual machines such as CMSBATCH, ROUT-
ER, and RSCS.
Tailoring VMUTIL' s WAKEUP PARHS File
Enable all local 3270s Cand remote ASCII teletype and
Virtual Control Unit Interference start/stop terminals).
Making Batch Spooling tlore Efficient You might want to consider the following changes if you have not
made them already:
Putting a Test DOS or VSl SYSRES on a Hinidisk
Reduce the sleep interval to 2 to 3 seconds, or eliminate sleep.
Why Hulti-Write Update is a Problem in CHS
Put an asterisk C"') in front of the AUTO LOG statements for ma-
DMKSYS CONSIDERATIONS chines that you are not currently using (changes the statement
to a comment).
New Hissing Interrupt Handling Function - SYSHIH
~
c...:I If you want your guest DOS/VSE or as batch machine to own most
00 Adding CP-Owned Volumes to SYSO\{N of the terminals, replace the CP ENABLE ALL statement with a
I f You Ivant To Change VH's SYSRES Address of "123" CP ENABLE CUU CUU CUU ...
Automatic T-Disk Clearing to put the VH LOGO on only a few specific 3270s.
Paging/Spooling on Two Different Types of Disks If you don't know what the address of a particular terminal is, is-
sue CP ENABLE ALL, then press ENTER at the terminal to clear the VH
Free Storage Considerations - What it is and why CP EXTENDS may LOGO and, without logging on, issue
make you change it.
PAGING, SPOOLING, AND T-DISK CONSIDERATIONS
MSG * HI
to send a message to yourself. CP will display on your screen:
How CP Handles CP-Owned Volumes
MSG FROM LOGONXXX HI
T-Disk Areas
where XXX is your terminal address.
Page/Spool Areas
To find the RESID (resource ID) address of a remote 3270 terminal,
Separating Paging from Spooling issue CP NET\IDRK E:-iABLE ALL and send a message to yourself. CP will
display
Adding i1 New TE:1P Disk
HSG FRml LOGNxxxx HI
Looking at CP SYSRES's Alloca~ion Information
where XXXX is your terminal RESID address.
2
VMUTIL'S WAKEUP PARM FILE
Other things you might want to add to AUTOLOG1'S PROFILE EXEC are:
If your VM system operator would like to eliminate the
I f the Vl'1 Real Time Monitor (SMART) is installed:
"THE THIE IS NOW
add near the beginning of the PROFILE:
message from appearing an OPERATOR'S console every two hours) edit
CP AUTOLOG S~IART password CP SET RUN ON WA..
'EUP PAlmS and globally erase the
Insert near the end: "MSG01"
EXEC SMINIT SMART operand from the file by doing the following:
to set up SMART's threshold values.
c IMSG0111 **
I f you want to run HONITOR twenty-four hours a day, during the week,
If V~I Performance/Honitor Analysis Program (V~IAP) is installed: but wish to get Vl'IAP output bv shift for example,
1st - Midnight to 9 a.m.
and you want to run Monitor twenty-four hours a day, add the follow- 2nd - 9 a.m. to 5 p.m.
ing statements:
3rd - 5 p. m to ~Iidnight
CP ~IONITOR ENABLE PERFORM USER DASTAP add the following commands to the WAKEUP file:
CP MONITOR START SPOOL M-F CP MONITOR ENABLE PERFORM USER DASTAP
00:02:00 02/24/83
N M-F 00:02:00 02/24/83 CP MONITOR START SPOOL
~ Then, regardless of "hat time of day VM is IPLed, ~Ionitor "ill be
CCl enabled. M-F 09:00:00 CP MONITOR CLOSE
02/24/83
If VM is at VM PUT 8207 or higher, and you want to turn off VM' s ne" M-F CP MONITOR CLOSE
17:00:00 02/24/83
Missing Interrupt Handler function which was made available in PUT
8207, add: M-F 23:58:00 02/24/83 CP MONITOR STOP
CP SET MITIME OFF
Note: CLOSE tells CP to send all accumulated Monitor
data to Vl'IAP, but continue collecting tlonitor data. STOP
stops collection of Monitor data.
6
5
MAKING BATCH MACHINE SPOOLING MORE EFFICIENT
VIRTUAL CONTROL UNIT INTERFERENCE
If you dedicate your system printer to a guest batch virtual
Does the conso-Ie of your batch virtual machine mysteriously hang and
machine,~--mak.e sure your spool blocks are as large as possible, oth-
then fre-e up_ fairly often?
erwise, when your virtual machine' 5 time slice ends, your printer
channel program may terminate before your virtual machine is dis-
One of the common causes of this condition is VIRTUAL CONTROL
patched again, slowing down the effective print speed.
UN IT INTERFERENCE, which is caused by having incompatible de-
vices logically attached to the same virtual control unit, that is,
For example, in DOS/VSE POWER, POWER spool blocking defaults to
some devices require SHARED Unit Control Words (UCWs) while other
800-1000 bytes, depending on the type of disk being used, whereas
devices require UN SHARED UCWs.
the maximum. allowable blocking is 2008 bytes. By specifying a value
as close to 2008 as possible, the printer's channel program will
I have seen this situation occur many times with many customers when
continue for a longer period of time after time-slice end, driving
the guest batch machine has its console in full screen (DOC) mode on
the printer at closer to its rated speed.
a 3270 at virtual address OIF, and one or more of the following vir-
tual devices within the address range:
To Double Spool or Not to Double Spool
010 TO 01F
If two or more batch machines as well as CHS uers need to share the
same printer, rather than attaching and detaching the printer for
010 3705
specific virtual machines, it might be better to have CP own the
OIC Diskette Reader
printer. You might think that double spooling would not be very ef-
DID CP Spooled Punch
fiCient, but in fact it is a very good performer. The alternative
DIE CP Spooled Printer
of not using the batch machine's spooling mechanism but rather as-
signing separate virtual readers, punches, and printers to each
My usual recommendation is to change the batch machine's virtual
partition or region would cause 7 TO 8 TIMES the number of Start
console from OlF to somthing else.
I/Os (SIOs) that CP would have to handle since every 3D-character
~
reader and punch record and every 120- to 133-character print line
Another not-50-obvious example of virtual control unit interference
"'"
Q is:
would cause an SIO. Such a large number of SIOs would substantially
increase the CP overhead, since SIOs are one of the most significant
causes of overhead in a VH system.
Disks on 358 (uses SHARED UCWs)
Tapes on 350 (uses UNSHARED UCI,s)
The disks will hang until tape I/O operations are finished.
3
STORE onto an incorrectly initialized minidisk, you will get a vague
PUTTING A TEST DOS OR VSl SYSRES ON A MINIDISK
error message stating that the function did not work.
Minidisk Restrictions
A DOS, OS, or C~IS minidisk cannot start in real cylinder zero of a
WHY MULTI-WRITE UPDATE IS A PROBLEM IN CMS
CP-owned pack (that is, a pack with CP paging, spooling, and T-disk
or VM directory areas on it), since Cp's Volume Table of Contents
Since CMS does not provide any form of multi-update support such as
(VTOC) is incompatible with those of DOS/VSE and OS. A major dif-
RESERVE/RELEASE or ENQ/DEQ, if two or more CMS users have
ference is Cp's Allocation Bit Map which is located on cylinder
multi-write links and accesses to the same minidisk, bad things are
zero, track 0, record 4. (How to eliminate this incompatibility is
likely to happen to that minidisk. You take the risk of losing one
beyond the scope of this session.)
or more files and perhaps the whole minidisk if double updating oc-
curs.
VS1 Minidisk Considerations
When two users LINK and ACCESS the same minidisk, CMS gives each
VSl minidisks must start in real cylinder zero of each disk i f a
user a STATIC view of the contents of the disk, including a bit
multi-track VTOC is used because the VSl Locate Catalog Management
map that shows which blocks of the minidisk are used or available. A
function uses a "Search ID equal or high" channel command word (CCW)
file erased by one individual is still seen, and can be accessed by
to find the end of the VTOC. Therefore, you cannot put CP-owned
the other user. A file added by one user is not seen by the other.
functions such as paging, spooling, or T-disk space on this pack.
If one user updates an existing file, the other user will see the
OLD copy of the file. The first person to write his file back on
If the VSl minidisk started on other than real cylinder zero. the
disk MAY have that file overlaid when the second user writes a file
search ID equal or high would always occur after only the first
on the disk. Whether or not both users write on exactly the same
track of the VTOC is searched. If you have ~ a one-track VTOC,
area depends on i f a user ERASED an old file prior to creating a
the VS1 minidisk can be placed anywhere.
new file. Depending on where the erased file's blocks were located,
the newly created file may re-use some or all of the erased file's
l\O The Device Support Facility (DSF) is required to initialize a mini-
blocks. Even if neither user erased a file before creating a new
disk on 3375 and 3380 disks. For all other disks, you may optionally
"""
..... use the IBCDASDI program. In either case, you should use the "Cyl-
one, i t is very unlikely that both people wrote exactly the same
size file, so CHS I 5 pointers to available areas on the minidisk are
inder" option to define the number of cylinders to be a'llocated for
now permanently messed up. If the first user tries to write out an~
the minidisk.
other file, CMS will detect that the pointers are bad and will
ABEND. The user can IPL C~IS again, but he can't write on the file
DOS Minidisk Considerations
again.
DOS, DOS/VS, or DOS/VSE minidisks can be located anywhere (except on
If you do not have a current tape backup of the files on the mini-
cylinder zero of CP-owned volumes) and can be initialized by DSF
disk, you can define a T-Disk and use FLIST/FILELIST to copy over
with the number of cylinders or blocks option specified.
all UNCHANGED files. (Any attempt to copy a changed file that
Optionally, the DOS Initialize Disk Program (INITDISK) could be
has messed-up pointers will cause CMS to ABEND again.) When you are
used to initialize minidisks on all DASD types except 3370, 3375,
done copying, you must reformat your minidisk with the CMS FORMAT
and 3380s. If INITDISK is used, you must use the QUICK DASDI
command to clean up the pointers. Then copy the files back from the
function: T-Disk to your reformatted minidisk.
II UID IS Many customers encounter this double update problem when they try to
update the 191 minidisk of a disconnected virtual machine that is
to put the correct number of cylinders in bytes 19 and 20 of the
also periodically updating its own disk; for example, VMUTIL's
VTOC. WAKEUP PAR~IS file. Therefore, i f you want to update a file such as
WAKEUP PARMS, first do a QUERY NMIES. I f VHUTIL is running, force
WARNING: Do NOT use the IQ initialization function of INITDSK,
it off, update the file, and then AUTOLOG VHUTIL back on again.
or IBCDASDI to initialize DOS minidisks. since both place an incor-
rect value for "number of cylinders" in, bytes 19 and 20' of the VTOC,
To avoid this double update problem, edit your VH directory and
making the minidisk unusable for DOS ~YSRES System or Private Li-
change all non-essential multi-write (HW) modes to Hulti-Read (aR)
brary functions. If you try to use a DOS function to COpy or RE-
8'ad eliminate tfte associated 1f~IULTI" passwords.
10
9
USER MAINT password
DMKSYS CONSIDERATIONS MDISK 123 3350 000 555 VMSRES MW
New Missing Interruot Handling Function - SYSMIH
Since IPF has the virtual address "123" hardcoded in many mainte-
With PUT 8207 or later, a new ~lissing Interrupt Handling function nance EXECs, if you do not find and change all occurrences of "123"
has been added to DMKSYS. If you apply such a PUT tape and reassem- to your real SYSRES address, you will not be able to use IPF for
ble DMKSYS without adding the new SYSMIH macro statement, you will those maintenance functions. Also, unless you move the modified IPF
get a mildly reproachful ~~OTE saying that the default values for EXECs to a different disk, the next PUT tape -for IPF that is in-
SYSMIH will be assumed. The TEXT deck created is OK, though. stalled on your system will wipe out your changes.
With the new Missing Interrupt Handling support in VM, if CP detects After you reassemble DMKSYS, but before you can generate a new CP
a missing interrupt condition for some I/O device attached to the nucleus, you must redefine "123" to your new address (cuu):
guest virtual machine, CP passes an INTERFACE CONTROL CHECK
condition back to the virtual machine. Since DOS and VSI do not CP DEFINE 123 cuu
handle interface control checks very well, you might want to turn
the new function off by adding to AUTOLOGI's PROFILE the following otherwise, your CP nucleus build and load process, which is looking
statement: for your new SYSRES address, will fail with an obscure "I/O error"
because it can't find the new virtual address.
CP SET MITIME OFF
Automatic T-Disk Clearing - A Security Feature
Adding New CP-Owned Volumes to SYSOWN
SIPOE's DMKSYS file has a parameter in the SYSRES macro called
If you want to spread paging and/or spooling space over more disks, SYSCLR
you must use CP Format/Allocate to format and allocate the new
N packs. This procedure .is described in detail later in'this session. SYSRES SYSCLR=YES,
11:>0 The new VOLIDs (assumed to be VMPK02 and VMPK03 on 3350s) should be
N added to the END of the SYSOWN statement. Reassemble DMKSYS and This SYSCLR operand tells CP during WI Initialization to clear, in
generate a new CP nucleus. When VM is shutdown and reIPLed, the VM small groups of cylinders, ALL T-Disk space on ALL CP-owned vol-
operator can then specify a WARM start, so no existing spool files umes. A C~IS user must still invoke the CHS FORMAT program before
will be lost. using the T-disk area. When the user detaches the T-Disk space or
logs off, the area is cleared by CP again. If you are not that con-
Old SYSOWN Statement: SYSOWN VMSRES,VMPKOI cerned about privacy and security of temporary data, and you want to
eliminate some CP overhead, you might wish to change SYSCLR to "NO."
Updated SYSOWN Statement: SYSOWN VMSRES, VMPKOl, VMPK02, VMPK03
SYSRES SYSCLR=NO,
Changing VMSRES's Virtual Address from '123' NOTE: Do not just eliminate the SYSCLR operand, because the default◦ Jabse Service Manual Search 2024 ◦ Jabse Pravopis ◦ onTap.bg ◦ Other service manual resources online : Fixya ◦ eServiceinfo