posting your separator would be wonderful! I saw the information in the Planning and Use Guide, didn't want to start from scratch (my assembler skills are very very rusty). I was going to try to disassemble the stock IEFOSC??, as well as the VM writer one, but I'd prefer to start with yours.
I'm not running VS1 under VM, but the VM writer is interesting because it was putting information into the CP CLOSE command, but it sounds like your writer shows how to find that information anyway.
As I recall, the VM writer is on a bootable system named VSXRES, and gets started on 00F ('S VMWTR'?) Are the original materials stowed away somewhere?
toggle quoted message
Show quoted text
On Saturday, July 8, 2023 at 07:04:48 PM GMT+2, Kevin Leonard <groups-list@...> wrote:
A separator routine would probably be the way to go, and the Planning and Use Guide is the book that tells you how to do it.? For something like this, it seems like you might want to write a single control line at the beginning of the data set with the information you would need (in VS1, the information available is pretty much limited to job name and SYSOUT class).? I wrote a separator routine that can be used to create a single HASP-like page that's useful in separating output being viewed online.? I don't think I included it in the interim VS1 system package I created.? If you'd like I could post it here as a sample of a separator routine.
Of course, if you're actually printing output from VS1 using a VM writer, there's the hack I used to use that puts the VS1 job name in the VM separator page in block letters.? You zap the CP CLOSE command in IEFOSC05 so instead of saying "CLOSE ddd NAME jjj" it says "CLOSE ddd DIST jjj".? DMKSEP in VM/370 writes two values in block letters:? the first is the virtual machine user ID, and the second is the distribution code.? If you set the distribution code for a particular print spool file to the job name, you get the job name in block letters.
--
