开云体育

1. Access to VM/370: You need a running VM/370 system, either on original IBM hardware (e.g., System/370) or emulated via Hercules, a popular emulator for mainframe systems.
2. Tape Image: A virtual tape file (e.g.,?tape.aws?or?vmfplc2.het) in a supported format (AWS, HET, or VMFPLC2) must be available. Physical tapes are unlikely in modern contexts.
3. Tape Device: A virtual tape drive must be defined in your VM/370 user’s virtual machine, typically at a specific virtual address (e.g.,?181?or?580).
4. CMS Knowledge: Familiarity with CMS commands is helpful, as most tape operations are performed in the CMS environment.
5. Tape Format: You need to know the tape’s format (e.g., labeled or unlabeled, VMFPLC2, TAPE DUMP, or standard OS format) and contents (e.g., CMS files, OS datasets, or other data).

• Log into your VM/370 user ID (e.g.,?MAINT?or a user ID with tape access privileges) using a 3270 terminal emulator (e.g.,?x3270?or?c3270?in Hercules).
• At the VM/370?CP READ?prompt, type?IPL CMS?to load the CMS operating system:
  IPL CMS

• Press?Enter?to enter the CMS environment. You should see the CMS prompt (READY;).

• Check if a tape drive is attached to your virtual machine at a specific virtual address (e.g.,?181, a common default for tape devices).
• Use the CP command?QUERY VIRTUAL TAPES?to list attached tape devices:
  QUERY VIRTUAL TAPES

• Expected output might look like:
  TAPE 181 3420 ONLINE

  This confirms a tape drive is attached at address?181?and is a 3420 model (or similar).
• If no tape drive is attached, attach one using the CP?ATTACH?command (requires appropriate privileges, often restricted to the?MAINT?user or system operator):
  ATTACH 580 TO userid AS 181

  Replace?580?with the real device address and?userid?with your user ID.

• In a modern emulation like Hercules, the tape image (e.g.,?tape.aws?or?vmfplc2.het) must be mounted to the virtual tape drive.
• If running Hercules, at the Hercules console (outside VM/370), attach the tape image to the tape drive address:
  attach 580 tape.aws

  Replace?580?with the tape drive’s real address and?tape.aws?with the path to your tape image file (ensure it’s in the correct directory, e.g., the?vm1?directory for Hercules setups).
• In VM/370, confirm the tape is mounted by querying the device:
  QUERY TAPE 181

  The output should indicate the tape is ready or online.

• If the tape contains multiple files or datasets, you may need to position it to the desired file using the CMS?TAPE?command with the?FSF?(Forward Space File) option:
  TAPE FSF 181 n

  Replace?n?with the number of files to skip (e.g.,?1?to skip to the second file). This is critical for multi-file tapes, such as those created with?TAPE DUMP.
• For single-file tapes or the first file, this step may not be needed.

• If the tape was created using the CMS?TAPE DUMP?command, use the?TAPE LOAD?command to restore files to a CMS disk (e.g., your A-disk at virtual address?191):
  TAPE LOAD 181

  This reads the tape and copies files to your A-disk, overwriting any existing files with the same name.
• To list files on the tape without loading them, use?TAPE SCAN:
  TAPE SCAN 181

  This displays the file names and attributes stored on the tape.

• If the tape is in?VMFPLC2?format (used for collections of CMS files), use the?VMFPLC2?utility to read it:
  VMFPLC2 LOAD 181 * * A

  This command restores all files (* *) from the tape at address?181?to your A-disk (A). Replace?A?with another disk (e.g.,?B?for?192) if needed.
• To list files on a VMFPLC2 tape:
  VMFPLC2 SCAN 181

• If the tape contains OS-formatted datasets (e.g., partitioned datasets or sequential files), use the CMS?MOVEFILE?command to copy data to a CMS disk:
  MOVEFILE 181 TAPE TO 191 DISK

  This transfers the tape’s contents to your A-disk. You may need to specify the dataset format or use additional utilities like?COPYFILE?for conversion to CMS format.
• For partitioned datasets (PDS), additional steps may be required to convert members to individual CMS files, often using custom EXEC scripts or utilities like?PDSLOAD.

• For?labeled tapes, ensure the tape has a valid VOL1 label. Use the?TAPE WVOL1?command to initialize or verify the volume label if needed:
  TAPE WVOL1 181 volid

  Replace?volid?with the tape’s volume identifier.
• For?unlabeled tapes, CMS assumes no label processing unless your program explicitly handles labels as data.
• Use?TAPE DUMP?or?TAPE LOAD?for unlabeled tapes created with CMS utilities, as described above.

• After loading files, use the CMS?LISTFILE?command to verify that files were transferred to your disk:
  LISTFILE * * A

  This lists all files on your A-disk.
• Open or inspect files using CMS commands like?TYPE?(for text files) or?BROWSE:
  TYPE filename filetype A

• When finished, detach the tape from your virtual machine to free the device:
  DETACH 181

• In Hercules, unmount the tape image at the Hercules console:
  detach 580

• Tape Formats: VM/370 supports specific tape formats like AWS (used in Hercules), HET, and VMFPLC2. Ensure your tape image matches the expected format. If the tape is in an incompatible format (e.g., modern 3590 tapes), VM/370 cannot read it directly.
• BLOCKTAP Utility: For certain tapes (e.g., VMSHARE or WATERLOO), the?BLOCKTAP?utility can intercept tape I/O to read non-standard formats. Use:
  BLOCKTAP LOAD 181

  This is specific to VM/370 Community Edition V1R1.2 or custom setups.
• Error Handling: Common errors include:
  • Tape not mounted: Ensure the tape image is attached in Hercules or the physical tape is loaded.
  • Wrong format: Verify the tape’s format (AWS, HET, or VMFPLC2) and use the correct utility (TAPE,?VMFPLC2, or?MOVEFILE).
  • Device offline: Check with?QUERY TAPE?and attach the device if needed.
• Hercules Environment: Most modern VM/370 users run on Hercules. Place tape images in the Hercules working directory (e.g.,?vm1/) and ensure the Hercules configuration file (hercules.cnf) defines tape devices at the correct addresses (e.g.,?0580 3420 tape.aws).
• Privileges: Some commands (e.g.,?ATTACH) require system operator or MAINT privileges. If you lack access, coordinate with your system administrator.

1. Start Hercules and attach the tape:
   attach 580 vmfplc2.het

2. Log into VM/370, IPL CMS, and check the tape drive:
   QUERY TAPE 181

3. List files on the tape:
   VMFPLC2 SCAN 181

4. Load files to A-disk:
   VMFPLC2 LOAD 181 * * A

5. Verify files:
   LISTFILE * * A

6. Detach the tape:
   DETACH 181

• VM/370 Constraints: VM/370 is a 1970s system and does not support modern tape hardware (e.g., 3590 or LTO). Emulated tapes in AWS or HET format are standard for Hercules.
• Documentation: Refer to the?IBM Virtual Machine Facility/370: CMS Command Reference?or?Operator’s Guide?for detailed command syntax. These are available online at sites like bitsavers.org.
• Practice Required: As noted in VM/370 tutorials, proficiency with CMS and tape operations requires hands-on practice.

Source trace instructions at?

users guide -> programming -> debugging -> KEDF -> source trace

CMS vsam is DOS/VS vsam not MVS vsam so yes different

?

Is that different from the VSAM that we have with MVS 3.8j? Hmm…

might be useful to run it with source trace...

Anyone with some thoughts on this?

after having connected my two MVS installations via Bob's ingenious NJE38 a while ago, with one link to the hosting Raspberry OS via funetnje, I thought it was about time to attach my VM/370 system to this network, too. I'v tried to catch up with what has been posted here about RSCS but still do not get it right. My attempt of "configuring" RSCS according to RSCS.MEMO blew up my CP kernel custom DMKBOX logon screen but luckily I could gen it again. I wonder if the defaults of RSCS are good to go and one just has to add the device statement in the hercules config for dev 040 2703. I also noticed that in some post the connection to MVS is a RJE connection. Is that what RSCS is about when talking to MVS? I noticed that the NJE links are configured with the additional flag "tcpnje" and the example of RSCS talking to JES2 do not have that flag with the 2703 device. If RSCS is able to talk to NJE38, what does it take? Just that link config flag or is there more to it? I reckon that also a routing table must be set up. Is there a thorough documentation available from which I could piece everything together?

quite a while ago you've shown me how to change the "logon screen" for VM to a custom version. I recently made some minor changes, performed the steps and now VM starts with that minor change to the login screen. However, the print output still shows the customised but previous "banner" and I wonder if there is some other place to make changes which I simply forgot. The system has been re-ipl'ed of course.?