CP Command Reference for General Users (Rel 6 PLC 17 Apr81)
Page153(165 of 213)
SYSTEM ITse the SYSTEM command to simulate the action of the RESET and RESTART buttons on the real computer console, and to clear storaqe. The format of the SYSTEM command is: r----------- L SYStem I , I { CLEAR } RESTART I I I J CLEAR virtual storage and virtual storage keys to binary zerDS. RESET clears all pendinq interrupts and conditions in the virtual machine. RESTARr simulates the hardware system RESTART function by storing the current PSi at virtual location eiqht and loading, as the new PSi, the douhleword from virtual location zero. Interrupt coniitions and storage remain unaffected. 1. The function and the CLEAR function leave the virtual machine in disabled wait state. Both CLEAR and RESET clear pending interrupts. Both functions load a PSi that is all zeroes except for the wait bit which is set on. 2. After issuinq the SYSTEM command with RESET or CLEAR specified, either STORE a PSi and issue BEGIN or issue BEGIN with a storage location specified, to resume operation. The virtual machine automatically restarts at the location specified in the new PSi (which is loaded from the doubleword at location zero) after the SYSTEM RESTART command is processed. STORAGE CLEARED - SYSTEM BESET is the response given if the command SYSrEM CLEAR is entered. SYSTEM RESET is the response qiven if the command SYSTEM RESET is entered. If the c3mmand SYSTEM RESTART is entered, no response is given; the virtual machine resumes execution at the address in the virtual PSi loaded frDm virtual storage location zero. Section 5. Format of CP Commands 153
TAG Use the rAG to associate file information with a VM/370 file. The format of the TAG command is: r----- DEV TAq PUnch DEv CONsole [tagtext] vaddr FIle spoolid [tagtext 1 rrinter} PUnch DEv CONsole OUery vaddr FIle spoolid PClt CONSOLE vaddr with t.he queried. a spoolinq device whose output is to be associated taq information or whose tag information is to be Note: when a qeneric device name, such as PRINTER or CONSOLE in the TAG command, all current virtual devices of that type are affected. FILE spoolid t aqtext specifies a previously closed spool file whose tag information is to be replaced or aueried. This form of the TAG command can only be used for reader spool files that are queued on virtual reader. The spoolid operand is the spool file identification, a number 1 and 9900 and assigned by CP when the spool file was closed. is the information (up to 134 characters in length, including imbedded that is to be associated with the specified spool device or spool file. The contents and format of this data is cOIDPletely flexible and is the responsibility of the file originator and the end user. certain control and addressing information, meaningful to the RSCS component of VM/370, can be specified in this field. For details on how to use the taqtext operand when transmitting files across the RSCS network, refer to the following "Usage Not e s " sect ion. 154 IBM VM/370 CP Command Feference for General Users
STORE Decimal !gg£g§.§ 216 224 256 352 384 448 Hexadecimal Add£g§§ __ _ 08 EO 100 160 180 1CO Lengt h 1:1LMig§ 8 8 8 32 64 64 CPU Timer Clock Com para tor Current PSW Floating-point registers 0-6 General registers 0-15 Control registers 0-15 1. First level storage is real main storage. Jnly second-level storage (storage that is real to the virtual machine) can be stored into. systems running in a virtual machine such as and OS/VS have virtual (third level) storage of their own. This third-level storage cannot be stored into directly. The user or the virtual operating system is responsible for converting any storage locations to second-level storage locations. 2. The may be combined in any order desired, separated by one or blanks, for up to one full line of input. If an invalid operand is encountered, an error message is issued and the store function is terminated. However, all valid operands entered, before the invalid one, are processed properly. 3. If combine the operands for storing into storage, registers, the PSW, or the status area on a single command line, all operands must be specified; default values do not apply in this case. 4. 5. If the STORE command is used by your virtual machine to alter the of a shared seqment, you receive a warning message and your virtual machine is unshared from (qiven a private copy of) the system. Other users of the segment continue to operate with an unchanged copy of that segment. with the STORE command, data is stored with fullword boundary alignment or in alignment. either in units of one word units of one byte without 6. The STORE STATUS command stores data in the extended logout area. The STORE STATUS command stores CPU Timer and Clock Comparator values that may then be displayed at the terminal via the command. The procedure is the only way to get timer information at the terminal usinq CP commands. STORE COMPLETE is the response at the successful completion of the command. IBM VM/310 CP Command Reference for General Users
SYSTEM ITse the SYSTEM command to simulate the action of the RESET and RESTART buttons on the real computer console, and to clear storaqe. The format of the SYSTEM command is: r----------- L SYStem I , I { CLEAR } RESTART I I I J CLEAR virtual storage and virtual storage keys to binary zerDS. RESET clears all pendinq interrupts and conditions in the virtual machine. RESTARr simulates the hardware system RESTART function by storing the current PSi at virtual location eiqht and loading, as the new PSi, the douhleword from virtual location zero. Interrupt coniitions and storage remain unaffected. 1. The function and the CLEAR function leave the virtual machine in disabled wait state. Both CLEAR and RESET clear pending interrupts. Both functions load a PSi that is all zeroes except for the wait bit which is set on. 2. After issuinq the SYSTEM command with RESET or CLEAR specified, either STORE a PSi and issue BEGIN or issue BEGIN with a storage location specified, to resume operation. The virtual machine automatically restarts at the location specified in the new PSi (which is loaded from the doubleword at location zero) after the SYSTEM RESTART command is processed. STORAGE CLEARED - SYSTEM BESET is the response given if the command SYSrEM CLEAR is entered. SYSTEM RESET is the response qiven if the command SYSTEM RESET is entered. If the c3mmand SYSTEM RESTART is entered, no response is given; the virtual machine resumes execution at the address in the virtual PSi loaded frDm virtual storage location zero. Section 5. Format of CP Commands 153
CP Command Reference for General Users (Rel 6 PLC 17 Apr81)
Page151(163 of 213)
STORE Greg 1 [hexword2 ••• 1 stores the hexadecimal data (hexword 1 [hexword2 ••• ]) in successive general registers starting at the register by reg. The reg operand must be either a decimal namher from 0 through 15 or a hexadecimal digit from 0 through F. The hexword1 (hexword2 ••• 10perand each represents up to eiqht hexadecimal digits. If the value being stored is less than a :uLiword (eight hexadecimal digits) , it is riqht-adjusted in the word and the high order bytes of the word are filled with zeros. If two or more hexwords are specified, they must be separated by one or more blanks. 'lrreg 1 r hexword2 ••• 1 stores the hexadecimal data (hexword 1 [ hexword2 ••• ]) in successive control registers starting at the register bv reg. The reg operand must either be a decimal number from 0 through 15 or a hexadecimal digit from 0 through F. Jf the virtual machine is in basic control mode, you can data in register 0 only. The hexword1 :hexword2 ••• ] operand each represents up to eiqht hexadecimal digits. If the value beinq stored is less than a fullword (eight hexadecimal digits), it is right-adjusted in the word and the hiqh order bytes of the word are filled with zeros. If two or hexwords are specified, they must be separated by one or more blanks. Yreg hexdword 1 [hexdword2 ••• 1 stores the hexadecimal data (hexdword1 [hexdword2 ••• ]) in successive floating-point registers starting at the register bV reg. The reg operand must be a digit from 0 7. If reg is an odd number, it is adjusted to the preceding even number. The hexdword1 [hexdword2 ••• ] operand each represents up to 16 hexadecimal digits. If the value beinq stored is less than a doubleword (16 hexadecimal diqits), it is left-justified in the doubleword and low order positions are filled with zeros. If two hexdwords are specified, they must be separated by one or more blanks. PSW hexword2 stores the hexadecimal data in the first and second words of the virtual machine's program status word (PSW). If only hexword2 is specified, it is stored into the second word of the PSW. The [hexword1] hexword2 operand each represents up to eight hexadecimal digits. These operands must be separated by one or more blankse If the value being stored is less than a fallword (eight hexadecimal digits), it is right-adjusted in the word and the high order bytes of the word are filled with stores selected virtual machine data in certain low storage locations of the virtual machine, simulating the hardware store status facility. These locations are permanently assiqned locations in real storage. To use the STATUS operand, your virtual machine must be in the extended control The SrATUS operand should not be issued for virtual machines or for DOS virtual machines generated for a CPU smaller than a System/360 Model 40. The STATUS operand stores the following data in low storage: Section 5. Format of CP Commands 151
STORE Decimal !gg£g§.§ 216 224 256 352 384 448 Hexadecimal Add£g§§ __ _ 08 EO 100 160 180 1CO Lengt h 1:1LMig§ 8 8 8 32 64 64 CPU Timer Clock Com para tor Current PSW Floating-point registers 0-6 General registers 0-15 Control registers 0-15 1. First level storage is real main storage. Jnly second-level storage (storage that is real to the virtual machine) can be stored into. systems running in a virtual machine such as and OS/VS have virtual (third level) storage of their own. This third-level storage cannot be stored into directly. The user or the virtual operating system is responsible for converting any storage locations to second-level storage locations. 2. The may be combined in any order desired, separated by one or blanks, for up to one full line of input. If an invalid operand is encountered, an error message is issued and the store function is terminated. However, all valid operands entered, before the invalid one, are processed properly. 3. If combine the operands for storing into storage, registers, the PSW, or the status area on a single command line, all operands must be specified; default values do not apply in this case. 4. 5. If the STORE command is used by your virtual machine to alter the of a shared seqment, you receive a warning message and your virtual machine is unshared from (qiven a private copy of) the system. Other users of the segment continue to operate with an unchanged copy of that segment. with the STORE command, data is stored with fullword boundary alignment or in alignment. either in units of one word units of one byte without 6. The STORE STATUS command stores data in the extended logout area. The STORE STATUS command stores CPU Timer and Clock Comparator values that may then be displayed at the terminal via the command. The procedure is the only way to get timer information at the terminal usinq CP commands. STORE COMPLETE is the response at the successful completion of the command. IBM VM/310 CP Command Reference for General Users
STORE Use the srORE command to alter the contents of specified registers and locations of the virtual machine. The contents of the following can be altered: • virtual storaqe locations (1st level virtual storage only; see "Usage Notes") • General reqisters • Floating-point registers • Control registers (if available) • Pruqram status word The STORE can also save virtual machine data in low storage. The format of the STORE command is: r STore L hexloc Lhexloc hexloc Lhexloc hexword1 [hexword2 ••• ] Shexloc hexdata ••• { Greg} Xreq hexword1 [hexword2 ••• ] {Yreq} hexdword1 [hexdword2 ••• , psw [hexword1] hexword2 STATUS rhexword2 ••• ] stores the specified data (hexword1 successive fullword locations starting by hexloc. The smallest qroup of that can be stored using t.his form is one form (hexloc or Lhexloc) can be used. (hexword2 ••• ]) in at the address hexadecimal values full word. Either If hexloc is not on a fullword boundary, it is rounded down to the next lower fullword. The operands hexword1 [hexword2 ••• 1operand each represents up to 16 hexadecimal diqits. If the value being stored is less than a fullword (eiqht hexadecimal digits), it is right-adjusted in the word and the hiqh order bytes of the word are filled with zeros. If two or more hexwords are specified, they must be separated by one or more blanks. hexdata ••• stores the data specified (hexdata ••• ) in the address by hexloc, without word alignment. The shortest strinq that can be stored is one byte (two hexadecimal digits). If the strinq contains an odd number of characters, the last character is not stored, an error message is sent, and the function is terminated. rhe hexdata ••• operand is a strinq of two or more hexadecimal digits with no embedded 1S0 IBM VM/370 CP Command Reference for General Users
STORE Greg 1 [hexword2 ••• 1 stores the hexadecimal data (hexword 1 [hexword2 ••• ]) in successive general registers starting at the register by reg. The reg operand must be either a decimal namher from 0 through 15 or a hexadecimal digit from 0 through F. The hexword1 (hexword2 ••• 10perand each represents up to eiqht hexadecimal digits. If the value being stored is less than a :uLiword (eight hexadecimal digits) , it is riqht-adjusted in the word and the high order bytes of the word are filled with zeros. If two or more hexwords are specified, they must be separated by one or more blanks. 'lrreg 1 r hexword2 ••• 1 stores the hexadecimal data (hexword 1 [ hexword2 ••• ]) in successive control registers starting at the register bv reg. The reg operand must either be a decimal number from 0 through 15 or a hexadecimal digit from 0 through F. Jf the virtual machine is in basic control mode, you can data in register 0 only. The hexword1 :hexword2 ••• ] operand each represents up to eiqht hexadecimal digits. If the value beinq stored is less than a fullword (eight hexadecimal digits), it is right-adjusted in the word and the hiqh order bytes of the word are filled with zeros. If two or hexwords are specified, they must be separated by one or more blanks. Yreg hexdword 1 [hexdword2 ••• 1 stores the hexadecimal data (hexdword1 [hexdword2 ••• ]) in successive floating-point registers starting at the register bV reg. The reg operand must be a digit from 0 7. If reg is an odd number, it is adjusted to the preceding even number. The hexdword1 [hexdword2 ••• ] operand each represents up to 16 hexadecimal digits. If the value beinq stored is less than a doubleword (16 hexadecimal diqits), it is left-justified in the doubleword and low order positions are filled with zeros. If two hexdwords are specified, they must be separated by one or more blanks. PSW hexword2 stores the hexadecimal data in the first and second words of the virtual machine's program status word (PSW). If only hexword2 is specified, it is stored into the second word of the PSW. The [hexword1] hexword2 operand each represents up to eight hexadecimal digits. These operands must be separated by one or more blankse If the value being stored is less than a fallword (eight hexadecimal digits), it is right-adjusted in the word and the high order bytes of the word are filled with stores selected virtual machine data in certain low storage locations of the virtual machine, simulating the hardware store status facility. These locations are permanently assiqned locations in real storage. To use the STATUS operand, your virtual machine must be in the extended control The SrATUS operand should not be issued for virtual machines or for DOS virtual machines generated for a CPU smaller than a System/360 Model 40. The STATUS operand stores the following data in low storage: Section 5. Format of CP Commands 151
CP Command Reference for General Users (Rel 6 PLC 17 Apr81)
Page155(167 of 213)
QUERY DEV PRINTER" PRT oCH CONSOLE vaddr FILE spoolid 1isplavs, at your terminal, the current tag information associated with a given virtual device or spool file. The operands used with the TAG QUERY command correspond to the operands used with TAG itself. 1. The RSCS control program interprets the tag information as being addressinq and control parameters. When you spool a file to the RSCS virtual machine to be transmitted to a remote station, code the taqtext operand as follows: locid fuseridl [priority] loci1 is the location identifier (one to eight alphameric characters) of the location to which the file is being transmitted. Your system programmer can give you the locids of remote stations accessible to your virtual machine. userid is the userid of the VM/370 virtual machine (a one-to eiqht-character user identification) to which a file is beinq transmitted. This operand is used by remote stations when they transmit files to the RS:S virtual machine and want the files sent to a particular VM/370 virtual machine. YoU can ignore this operand if you are not specifyinq a priority. However, if you are specifying a priority, you must code some userid operand; it is iqnored by RSCS. priority is the requested transmission priority, a decimal number between 0 and 99. The highest transmission priority is 0, next hiqhest is 1, and so on. If you wish to specify this operand, you must also specify a userid operand. 2. If enter the TAG command with no taqtext information, the tag area associated with the device or file is set to all blanks. 3. A spool file that you have created and spooled to another virtual machine is owned by the other user as soon as the file is closed. If you want to query or chanqe the tag data, you must first reclaim the file via the TRANSFER command. 4. the buffer that contains TAG information is 134 characters in length includinq imbedded blanks, only 126 characters of it are usable because of input command line limitations. Section 5. Format of CP Commands 155
{ PRINTER} QUERY DEV PUNCH CONSOLE Displays the contents of the tags associated with each device of the specified class, as follows: { OFT} , repeated for • PUN vaddr TAG: I each device in CONS I the specified tagtext ••••••••••••• I class J TAG QUERY DEV vaddr Displays the contents of the tag associated with the specified devi=e, as follows: { ORT } PUN vaddr TAG: CONS taqtext •••••••••• if tag data exists TAG NOT SET if the TAG command was never issued to that device. QUEFY FILE spoolid Displays the contents of the tag associated with the specified file, as follows: taqtext •••••••••• if taq data exists (TAG BLANK) if the tag is all blanks (TAG if the file did not contain a tag because it was either an input file the real card reader or was an output file generated prior to Release 2 PLC 11. cP Command Reterence for General Users
TAG Use the rAG to associate file information with a VM/370 file. The format of the TAG command is: r----- DEV TAq PUnch DEv CONsole [tagtext] vaddr FIle spoolid [tagtext 1 rrinter} PUnch DEv CONsole OUery vaddr FIle spoolid PClt CONSOLE vaddr with t.he queried. a spoolinq device whose output is to be associated taq information or whose tag information is to be Note: when a qeneric device name, such as PRINTER or CONSOLE in the TAG command, all current virtual devices of that type are affected. FILE spoolid t aqtext specifies a previously closed spool file whose tag information is to be replaced or aueried. This form of the TAG command can only be used for reader spool files that are queued on virtual reader. The spoolid operand is the spool file identification, a number 1 and 9900 and assigned by CP when the spool file was closed. is the information (up to 134 characters in length, including imbedded that is to be associated with the specified spool device or spool file. The contents and format of this data is cOIDPletely flexible and is the responsibility of the file originator and the end user. certain control and addressing information, meaningful to the RSCS component of VM/370, can be specified in this field. For details on how to use the taqtext operand when transmitting files across the RSCS network, refer to the following "Usage Not e s " sect ion. 154 IBM VM/370 CP Command Feference for General Users
QUERY DEV PRINTER" PRT oCH CONSOLE vaddr FILE spoolid 1isplavs, at your terminal, the current tag information associated with a given virtual device or spool file. The operands used with the TAG QUERY command correspond to the operands used with TAG itself. 1. The RSCS control program interprets the tag information as being addressinq and control parameters. When you spool a file to the RSCS virtual machine to be transmitted to a remote station, code the taqtext operand as follows: locid fuseridl [priority] loci1 is the location identifier (one to eight alphameric characters) of the location to which the file is being transmitted. Your system programmer can give you the locids of remote stations accessible to your virtual machine. userid is the userid of the VM/370 virtual machine (a one-to eiqht-character user identification) to which a file is beinq transmitted. This operand is used by remote stations when they transmit files to the RS:S virtual machine and want the files sent to a particular VM/370 virtual machine. YoU can ignore this operand if you are not specifyinq a priority. However, if you are specifying a priority, you must code some userid operand; it is iqnored by RSCS. priority is the requested transmission priority, a decimal number between 0 and 99. The highest transmission priority is 0, next hiqhest is 1, and so on. If you wish to specify this operand, you must also specify a userid operand. 2. If enter the TAG command with no taqtext information, the tag area associated with the device or file is set to all blanks. 3. A spool file that you have created and spooled to another virtual machine is owned by the other user as soon as the file is closed. If you want to query or chanqe the tag data, you must first reclaim the file via the TRANSFER command. 4. the buffer that contains TAG information is 134 characters in length includinq imbedded blanks, only 126 characters of it are usable because of input command line limitations. Section 5. Format of CP Commands 155