开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. H390-OSVS
  2. Topics

Separator pages? HASP?

 

Can one get separator pages on VS1 printed output with retrofitting HASP?

How bad is retrofitting HASP? I saw the doc in the files section (though no tape).
 

ok, let me fix this.

Can I do this WITHOUT retrofitting HASP?
 

This document is more valuable than I would have thought (as soon as I saw "planning" I thought it was for middle managers.

has details for all sorts of interesting questions, including how to get separators.
 

I'm not sure why you want separator pages, they aren't as use in as virtual environment.

May I suggest you look at . It knows a number of separator page formats (HASP, JES2, OS/360 external writer, and none), and automatically bursts jobs into unique files.
 

On Fri, Jul 7, 2023 at 03:52 PM, Drew Derbyshire wrote:

I'm not sure why you want separator pages, they aren't as use in as virtual environment

I want them so that I can use HercPrt to render my output.
 

The Planning and Use Guide is essentially the system programmer's guide for VS1. By MVS, system programmer documentation had been split across a number of manuals, but for VS1, a lot of it is in that one book.

--
 

I'm not enthusiastic about tackling refitting HASP for VS1. The existing effort I looked at seemed to be missing macros and I wasn't excited about writing them. Maybe everything was there and I just wasn't seeing something.

--
 

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.

--
 

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?

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.

--
 

Hi, Doug,

Did you include the "VM" option in your VS1 SYSGEN ? That way, you can
IPL and run OS/VS1 "stand-alone" on a "bare" machine (hercules), or you can
IPL and run VS1 in a VM/370 virtual machine. When you add that VM option,
the VM/VS handshaking code is included in the nucleus.

If you do not include that option, then VS1 will not "know" that it is
running in a virtual machine.

I think that's how that code gets added to IEFOSC05 ... when the VM option
is included, and when NIP detects it is IPLed under VM.

Hope that helps,

Mark


On Sat, Jul 8, 2023 at 1:48?PM Doug Wegscheid <dwegscheid@...>
wrote:

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?

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.

--
 

There used to be patches to retrofit HASP to VS1 back in the 80’s but by the time I heard about them I didn’t have a vs1 system. Hopefully they can be found.
Laddie Hanus

On Saturday, July 8, 2023, 11:46 AM, Kevin Leonard <groups-list@...> wrote:

I'm not enthusiastic about tackling refitting HASP for VS1.? The existing effort I looked at seemed to be missing macros and I wasn't excited about writing them.? Maybe everything was there and I just wasn't seeing something.

--

1 - 11 of 11