开云体育

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

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

Thanks 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?

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

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.

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

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?

DIRENT is what you're looking for (it's is not a REXX exec)
--
Kris Buelens

I thought I remembered a discussion about there being a REXX program (CBT? VMSHARE?) that would read the minidisk the CP Directory was located and create a USER DIRECT file.

I can't seem to find the discussion or the program. Am I imagining things?

P.S. Merry Christmas & Happy New Year.

?... Mark S.

On 12.13.2023 15:37, Daniel L. Srebnick via groups.io wrote:

Can anyone refer me to a straightfoward document explaining how to configure NJE on my VM/370 CE 1.2 system?? I have NJE configured on my MVS 3.8j host (TK5) and used the excellent docs put together by Bob Polmanter.

I see that I have the RSCS virtual machine running on my installation, I just don't know what to do next to get the two hosts peering.

The developer of the NJE device support and RSCS modifications, Peter
Coghlan, is usually willing to share his in-progress work privately with
people who contact him and let him know they're interested in trying them
out. You can find his email address on his web site,


-Matthew

Thank you Bob.

Can anyone refer me to a straightfoward document explaining how to configure NJE on my VM/370 CE 1.2 system?? I have NJE configured on my MVS 3.8j host (TK5) and used the excellent docs put together by Bob Polmanter.

I see that I have the RSCS virtual machine running on my installation, I just don't know what to do next to get the two hosts peering.

Best regards,

Dan

I uploaded CMSBATCH EXEC to the files section.? Please feel free to use and critique.? So far, it covers Assembler, COBOL, and PL/1.? I suppose I ought to add at least Fortran.

Thanks again to those who helped me along as I get reacquainted with VM/370.

On Thu, Nov 30, 2023 at 03:09 PM, Bob Polmanter wrote:

CP SPOOL CONSOLE TO userid START

and the very last statement should be:

CP SPOOL CONSOLE STOP CLOSE

I wonder if it is necessary to explicitly START/STOP CLOSE. For sure I never did. :-) All my batch jobs starts with the statements:

/JOB userid 1234 jobname
CP SPOOL CONSOLE TO userid
CP SPOOL PRINTER TO userid

The spool console output is sent back to userid in a file of class T, while whatever is printed is sent in an other file of class A. Then I examine the content of those with the SFBROWSE command and choose to purge/print the content with subcommands purge/print of SFBROWSE. I also make sure one of the "real" printers handles class T.

Cheers,

Rene FERLAND, Montreal

Hi Daniel,

It has been a long time since Ive used CMSBATCH, but looking at the statements in your job submission, you didn't actually print anything.? You did direct SYSPRINT and SYSOUT to the terminal, but not to the printer.? And the printer is what you spooled to your userid.

In order to see terminal output, you should spool the console as well, at the beginning of your job:

CP SPOOL CONSOLE TO userid START

and the very last statement should be:

CP SPOOL CONSOLE STOP CLOSE

The added benefit of this is that you can see any errors in the commands in the job stream when the console log is returned to you at end of job.

In lieu of the console log, you could remove the filedefs for SYSPRINT and SYSOUT, and then after the COBOL command you could physically print them with a PRINT command, for example:

PR SYSPRINT LISTING

I'm not sure that is the filename and filetype but you could determine those by running a Cobol compile in your own userid and see what ends up on your disk.

Regards,
Bob

Yes, they are prefixed by CP.? Apologies for omitting that during my description.

/JOB DAN 1234 TESTJOB
cp spool prt system class a
cp link dan 191 191 rr
access 191 b/a
filedef sysprint terminal
cobol testprg1
global txtlib cob360r
load testprg1
filedef sysout?? terminal
start
release 191
cp detach 191
/*

On Thu, Nov 30, 2023 at 12:50 PM, Daniel L. Srebnick wrote:

In both cases, the output ends up being owned by CMSBATCH and queued in class T.

SPOOL is a CP command. In your job, you need to prefix it with CP:

CP SPOOL PRT TO SYSTEM CLASS A
CP SPOOL PRT TO MYUSER

Cheers,

Rene FERLAND, Montreal

CMSBATCH seems to be ignoring my attempts to redirecdt output to either the system printer or back to my reader.

I've tried both of the following at the beginning of my jobs, right after the job card:

SPOOL PRT TO SYSTEM CLASS A

SPOOL PRT TO MYUSER

In both cases, the output ends up being owned by CMSBATCH and queued in class T.

I'm using CE 1.2.? Any thoughts?