I'm again playing with MVS (TK5 Update 2) under VM/370 CE 1.2.

I've succesfully submitted and executed a batch job from VM to MVS by punching it.? What I cannot figure out is how to tell the JCL to send the output back to my VM PRT device.? I vaguely remember doing this in school a lifetime ago.

Advice/pointers please?

You can spool 00E to your VM userid by logging on your MVS guest and issuing a
#CP SPOOL 00E to yourid CONT NOHOLD

Thank you Jim.

That did occur to me.? I'm hoping for a more "elegant" solution.? I know back in the day in a multiuser situation there was a way via JCL to get the output back to my VM.? I just don't recall what it was and if it relied upon additional software that we may or may not have access to.

Hi Daniel,

If you are using TK5 Update 2, you can spool MVS output back to your CMS userid automatically.? Basically, you need to put your CMS userid in your JOB statement (in the programmer name field), and you need to identify which printers and/or punches are to have the VM spooling capability in JES2PARM.

Please see the documentation titled "MVS_VM Installation and Use" PDF in the files contained in the TK5 update 2 (mvstk5-update2.zip) package.? That document tells you how to enable and use the capability.

If you are not using Update 2 of TK5, please download a file named 'mvs_vm.zip' from the files section of this message board (H390-Vm) and follow the instructions there.

Regards,
Bob

Hi Bob:

All the pieces appear to be installed already with TK5 Update 2.

In JES2PARM, I see:

PRINTER1?????? CLASS=A,SEP,AUTO,DSPLTCEL,NOPAUSE,UNIT=00E,DRAIN,?????? +
?????????????? UCS=QN,FCB=6,VM?????????????????????????????????????????

Is the "VM" parameter at the end of the PRINTER1 definition what you are referring to when you say to identify the printers needing VM spooling capability?

Class A is defined thusly:

$$A PRINT,SYSOUT,NOHOLD,TRKCEL????? STANDARD OUTPUT CLASS

Is there anything else that I need to define?

Working!? I already had what I needed, other than getting the jobcard correct.

Thanks Bob!

Hi Daniel,

Yes, the 'VM' keyword on the PRINTERx definition in JES2PARM is what enables that printer to be eligible to spool output back to the VM spool.? You can use the keyword on any and all PRINTERx definitions, and on punches too, if you choose.

Regards,
Bob

On Sun, Dec 17, 2023 at 11:24 AM, Daniel L. Srebnick wrote:

In JES2PARM, I see:

PRINTER1?????? CLASS=A,SEP,AUTO,DSPLTCEL,NOPAUSE,UNIT=00E,DRAIN,?????? +
?????????????? UCS=QN,FCB=6,VM

You might also consider replacing SEP by NOSEP as VM/370 already provides a separator page when printing. :-)

Cheers,

Rene FERLAND, Montreal

开云体育

That is probably not a good idea for the TK5 distribution at large as it is meant to be run standalone, outside of VM, where this would not be true.

Adding VM is basically ignored when not running under VM so that is safe, but changing SEP to NOSEP should probably be documented as a recommendation for users who are in fact running it under VM, as changing it in the distribution would impact users using it outside of VM.

On Sun, Dec 17, 2023 at 03:29 PM, Frank D. Engel, Jr. wrote:

Adding VM is basically ignored when not running under VM so that is safe, but changing SEP to NOSEP should probably be documented as a recommendation for users who are in fact running it under VM, as changing it in the distribution would impact users using it outside of VM.

You have a point and I agree. My suggestion was for the specific case of Daniel, and I used the verb "might consider" as, indeed, such a modification has an impact when TK5 is run standalone and would not survive the next update. :-)

Cheers,

Rene FERLAND, Montreal

Context is everything, as the question is about MVS as a VM guest, asked in VM group.

All working nicely here and thanks to the group for the assist.