IBM Virtual Machine Facility/370: Operator's Guide 2
Page34(34 of 260)
April 1, 1981 18.2 VM/370 Operator's Guide
If the clocks should run out of low-order synchronization, after the clocks are synchronized (during or after system initialization), you will receive the following message: DMKCLK970W TOO CLOCK SYNC CHECK RECEIVED CLOCK SYNCHRONIZATION-PRESS 'TOO ENABLE SET' As before, press the TOO Enable SET Key to synchronize the clocks. VM/370 uses the interval timer to support time slicing; therefore, during initialization, the system verifies that the interval timer is running before virtual machine logon operations are performed. The system initialization routine will loop issuing the following message if the interval timer is found not running when tested: TURN ON THE INTERVAL TIMER TURN ON THE INTERVAL TIMER The messages cease when the operator complies by enabling the interval timer and the system initialization process continues. In attached processor application the text of the processor owning the disabled interval timer. follows: TURN ON THE { MAIN } PROCESSOR INTERVAL TIMER ATTACHED the message indicates This message reads as To continue, the interval timer must be enabled on the requested processor. CONSOLE DEFINITION The terms "system console", "primary system console", and "alternate system console" apply to those console devices that exercise primary control of the processor. The VM/370 primary system console can be a real system console, a real alternate system console, or a local 3270. The VM/370 alternate system console can be a real system console, a real alternate system console, a local 3270, or any VM/370 supported remote terminal on a leased line connected to a 270x transmission control unit (TCU). The VM/370 alternate system console cannot be a remote terminal connected to a 370x TCU. !Qte: If the 370x is loaded with the 270x Emulation Program prior to initializing VM/370, the 370x then appears to V8/370 as a 270x TCU. The following examples show the various configurations that can control YM/370 operations. Section 2. Initiating VM/370 Operation 19
If the clocks should run out of low-order synchronization, after the clocks are synchronized (during or after system initialization), you will receive the following message: DMKCLK970W TOO CLOCK SYNC CHECK RECEIVED CLOCK SYNCHRONIZATION-PRESS 'TOO ENABLE SET' As before, press the TOO Enable SET Key to synchronize the clocks. VM/370 uses the interval timer to support time slicing; therefore, during initialization, the system verifies that the interval timer is running before virtual machine logon operations are performed. The system initialization routine will loop issuing the following message if the interval timer is found not running when tested: TURN ON THE INTERVAL TIMER TURN ON THE INTERVAL TIMER The messages cease when the operator complies by enabling the interval timer and the system initialization process continues. In attached processor application the text of the processor owning the disabled interval timer. follows: TURN ON THE { MAIN } PROCESSOR INTERVAL TIMER ATTACHED the message indicates This message reads as To continue, the interval timer must be enabled on the requested processor. CONSOLE DEFINITION The terms "system console", "primary system console", and "alternate system console" apply to those console devices that exercise primary control of the processor. The VM/370 primary system console can be a real system console, a real alternate system console, or a local 3270. The VM/370 alternate system console can be a real system console, a real alternate system console, a local 3270, or any VM/370 supported remote terminal on a leased line connected to a 270x transmission control unit (TCU). The VM/370 alternate system console cannot be a remote terminal connected to a 370x TCU. !Qte: If the 370x is loaded with the 270x Emulation Program prior to initializing VM/370, the 370x then appears to V8/370 as a 270x TCU. The following examples show the various configurations that can control YM/370 operations. Section 2. Initiating VM/370 Operation 19
IBM Virtual Machine Facility/370: Operator's Guide 2
Page32(32 of 260)
Page of GC20-1806-9 As Updated April 1, 1981 by TNL GN25-0834 DKKKSS ENDING ERROR - MSS NOT INITIALIZED ExplanatiQn: The KSS did not get initialized as it should during the OS/VS IPL process. Either the virtual machine does not have access to the MSC, or there was an MSS error. OperatQ£ response: Correct the problem, use the OS/VS VARY command to initialize the KSS, then reissue the "start dmkmss" command. DKKMSS ENDING ERROR - DCB FOR COMM. DEVICE NOT OPENED ExplanatiQn: The DMKMSS program was not able to establish communication with the VK/370 control program because the OS/VS DCB control block could not be opened. The probable cause is the definition of the communicator device for the virtual machine. contact the system programmer. After the problem has been corrected, reissue the "start dmkmss" command. DMK!SS ERROR READING !SS CONFIGURATION TABLE DMK!SS attempted to read one of the !SS configuration tables (Configuration Index/Manufacturer's ID Conversion table or the Configuration Data Block) and an error was encountered. Contact the MSS system programmer. After the problem has been corrected, reissue the START D!KKSS command. DMKKSS CPUID NOT FOUND IN MSS CONFIGURATION TABLES DMKKSS has read one of the MSS configuration tables (the Configuration Index/Manufacturer's ID Conversion table) and searched it for a match to this cpuid, but no match was found. Contact the !SS system programmer. The !SS configuration tables may need to be updated. After the problem has been corrected, reissue the START DMKKSS command. D!KKSS ERROR CREATING !5S CONFIGURATION TABLE Expla.nation: DKK!SS has given CP a list of VUAs associated with the central server cpuid. CP has attempted to create its shared and nonshared SDG tables, but has encountered an error. OperaiQ£ Contact the system programmer. After the problem has been corrected, reissue the START D!KMSS command. Attached Processor Initialization In order for the installation to run with an attached processor, it must do the following: • Specify AP=YES in the SYSCOR macro during VK/370 system generation • Have the attached processor online during system IPL 18 VM/370 Operator's Guide
Page of GC20-1806-9 As Updated April 1, 1981 by TNL GN25-0834 If the attached processor was generated as part of the system but vas not online, the following message is issued if the multiprocessing feature is installed: DMKCPI959W ATTACHED PROCESSOR NOT ONLINE If the attached processor is not required, processing can continue. However, if the attached processor is required, the operator should ready the unit and reload the system. Assuminq AP=YES and the attached processor was online the following message is issued. DMKCPI958r PROCESSOR NOW OPERATIONAL No operator action is required; the system will now utilize the attached processor. If the installation is running with an attached processor, the system operator will be issued the following message when the clocks are to be synchronized. CLOCK SYNCHRONIZATION-PRESS 'TOD ENABLE SET' The operator will then press the TOD SET key on either processor to synchronize the TOD clocks. Note that once the clocks are synchronized, it will not be necessary to resynchronize the clocks on subsequent IPL operations unless: • FE diagnostics are run • Power is turned off on either processor • The clocks are running but not synchronized • A clock's error is encountered during initialization Section 2. Initiating VK/370 Operation 18.1
IBM Virtual Machine Facility/370: Operator's Guide 2
Page36(36 of 260)
Ii!§! £onfigy!gtion: Real systea console = '8/370 system console Real alternate system console = '8/370 alternate system console Real systea console = Batch virtual machine Real alternate system console = '8/370 system console Remote ter.inal = V8/370 alternate system console !hird Real systea console = V8/370 system console Reaote terminal = V8/370 alternate system ccnsole Real systea console = Batch virtual aachine Tvo locally attached 3277 Display Stations = '8/370 system console and alternate system console Enabled reaote terainal (not 3270) = '8/370 alternate systea console (10 valid V8/370 priaary system console is designated in SYSGEI) !2te: The real system consoles must be turned off to prevent V8/370 froa using thea. ConfigY!stign: Systea console = '8/370 systea console (No V8/370 alternate console designated in SYSGEN) The first four configurations allov disabling of the V8/370 priaary console and selection of an alternate '8/370 console; or, conversely, reselection of the '8/370 priaary console and disabling of the alternate console. Configurations five and six indicate that V8/370 specified no console substitution. Therefore, if the system console is inoperative at V8/370 startup, the vait state and cannot continue. After the console again, '8/370 aust be reloaded into the real systea. DISABLING THE '8/370 PRI8ARY COl SOLE system generation designated '8/370 system enters the becomes operative If the '8/370 primary system console is inoperative, V8/370 aatoaatically selects the first alternate console (specified in the RIOGEN macro instruction) as the console for Frimary systea operation. If the first alternate console specified is not operational, an atteapt viII be aade to start the next alternate console. If an operational console is found, it viII be used as the V!/370 system operator's console. 20 '8/370 Operator's Guide
Apr il 1, 1981 If intermittent errors occur at the V8/370 console, and all alternate consoles are unavailable (or not specified in the RIOGEN macro instruction), issue the DISCONN command and log on again at some other terainal. If the VM/370 system console becomes inoperative to the point where you cannot log off, press the System/370 external INTERRUPT button to disconnect you from the failing system console (or alternate console if that console is currently controlling the system.) This allows you to log on and reconnect to a terminal with a communications line that has already been enabled. This terminal can be another system console (Y8/370 supported device) or a reaote terminal attached to a 270x TCU. When the primary console is again operative, control can be regained from the alternate console by pressing the INTERRUPT button and reconnecting using the primary console. When the device specified as the alternate console is a communication line, Y8/370 enables the line. You can then establish a link with the processor through a terminal connected to the line. Once the line is established, Y8/370 proceeds with the normal system initiation. The alternate console must not be a telecommunications line on a real IBM 370x Communications Controller. If the alternate console is an IB8 2741 Communication Terminal, it must use the EBCDIC transmission code. Nate: Y8/370 370x supports multiple alternate console selection only in 270x emulator mode. SELECTING A Y8/370 ALTERNATE CONSOLE DURING V8/370 INITIALIZATION If the Y8/370 system console is inoperative, a Vft/370 alternate system console can start Y8/370. To do this, place the primary V8/370 system console in a not-ready status. Load V8/370 in the normal way (with the System/370 console switches and the LOAD key). When the primary system console (assuming it was generated as the V8/370 system console) indicates "not ready,n V8/370 rings the console alarm bell and enables the alternate system console (such as a 3210 Model 2, 1052 80del 7, or local 3270 if one is specified) or one 2701, 2702, or 2703 transmission control unit (TeU) line that has a leased line terminal attached, to allow system operator to log on. The TCU line address must be defined in the REALIO module during VM/310 system generation. If the real system consoles are dedicated to virtual machine use only, the system can be generated with a fictitious V8/370 primary system console address and the same results occur as the load operation with the not ready console described above. You can now establish a link with V8/370 by using the designated device. Once CP identifies the terminal in the normal procedure, the operator presses the BREAK, ATTN, RESET, or ENTER key, depending on the terminal type. The V8/370 system then performs automatic or manual logon procedures, as previously discussed. Controlling the 370x Communications Controller Because the 3704 and 3705 Communications Controllers are programmable devices, in order for them to be controlled by V8/370, they must be loaded with an appropriate control program before V8/370 uses them for system telecommunications. This loading is normally an automatic function of V8/370 system initialization, but it can be performed manually. Section 2. Initiating V8/370 Operation 21