开云体育

I figured out the issue with LISTIO - I was missing an argument.

Changing that line to // LISTIO ALL fixed that problem.

I tried shutting down DOS/VS and re-IPLing it to see if that would clear up the "off-by-one" submission issue, but sadly it persists after the IPL.

Compared to the instructions in the DOSVS readme that is bundled with CE, I have modified my DOSIPL EXEC as follows:

CP SPOOL PUNCH *????????????????????????? ?
PUNCH NOTHING JCL A ( NOH?????????????????
CP SPOOL PUNCH OFF??????????????????????? ?
CP SPOOL 00E CLASS A????????????????????? ?
CP SPOOL 00E TO CMSUSER?????????????????? ?
CP DEFINE 1403 00F??????????????????????? ?
PRT? 00F DEFINED????????????????????????? ?
CP SPOOL 00F CLASS R????????????????????? ?
CP SPOOL 00F TO CMSUSER?????????????????? ?
CP IPL 360????????????????????????????????

I added one command to the end of the IPL procedure to support the class R printer that is set up by that:

S PRT,00F,R

My LISTIO JCL now reads:

// JOB LISTIO
// LISTIO ALL
// PAUSE??? ?
/&??????????

I created a SUBDOS EXEC to submit the JCL decks correctly:

CP SPOOL PUN TO DOSVS
PUNCH &1 &2 &3 (NOH?

It remains the case that:

subdos listio jcl

* nothing jcl actually processes (the one submitted by the DOSIPL EXEC???)

subdos nothing jcl

* listio jcl processes

subdos listio jcl

* nothing jcl processes

etc.

开云体育

Thank you!

That clears up one problem, though I am still seeing the one-submission lag.? That is, if I take turns punching NOTHING JCL and LISTIO JCL, then when I punch one of them, it is the other that processes.? If I punch LISTIO JCL now, it is NOTHING JCL that processes, and the LISTIO JCL that I punch now will not process until I punch something else (or a second copy of it).

The // LISTIO statement in my LISTIO JCL also gets flagged as invalid (though it is documented as valid in one of the IBM books I found), but that one doesn't seem to be a VM issue...

On Tue, Dec 26, 2023 at 03:01 AM, Frank D. Engel, Jr. wrote:

spool pun to dosvs
Ready; T=0.01/0.01 05:38:19
punch nothing jcl
PUN FILE 0263? TO? DOSVS??? COPY 01 NOHOLD

Hello Frank,

I think your problem comes from the fact that you punch the job with a header. Punch without a header instead:

punch nothing jcl ( noheader

Cheers,

Rene FERLAND, Montreal

I am trying to run DOS/VS under VM/370 using the "5pack" downloaded from the same site as VM/370 CE.

I was able to IPL successfully (as far as I can tell - new to DOS/VS so still wrapping my head around parts of this) and was able to direct the printer to spool output to CMSUSER under VM.


I am not sure if the issues I am facing are purely VM issues or are DOS/VS issues so wasn't sure if best to ask here or on the DOSVS list but it looks to me like I may have some sort of handshaking issue between them; hoping someone can point me in the right direction or let me know if I should join the DOSVS list to ask over there...


I created a copy of the NOTHING JCL as a file owned by CMSUSER:


type nothing jcl

// JOB NOTHING
/&

Ready; T=0.01/0.01 05:37:51


When I try submitting that to DOS/VS:


spool pun to dosvs
Ready; T=0.01/0.01 05:38:19
punch nothing jcl
PUN FILE 0263? TO? DOSVS??? COPY 01 NOHOLD
Ready; T=0.01/0.01 05:38:23



I am getting this on the DOS/VS console:


18 BG :READ? NOTHING? JCL????? A1 CMS191 12/26/23?? 5:33
19*BG 1S01D? INVALID STATEMENT.
20
0D07D? ENTER RESPONSE




I press ENTER at that point (on the DOS/VS console) and get this:


05 BG
06 BG EOJ NO NAME
07??? DATE 12/27/23,CLOCK 05/39/20
08 F1 1Q34I? LST WAITING FOR WORK ON 00E
09 BG // JOB NOTHING
10??? DATE 12/27/23,CLOCK 05/39/20
11 BG EOJ NOTHING
12??? DATE 12/27/23,CLOCK 05/39/20,DURATION 00/00/00
13 F1 1Q34I? LST WAITING FOR WORK ON 00E
14 F1 1Q34I?? BG WAITING FOR WORK



At that time CMSUSER receives *two* files on its reader from DOS/VS:


PRT FILE 0264 FROM DOSVS??? COPY 01 NOHOLD
PRT FILE 0265 FROM DOSVS??? COPY 01 NOHOLD


These contain:


?--- OK????????????????? ID=0264 AUTONAME????????? LINE=000001 OF 000003 CASE=U
:READ? NOTHING? JCL????? A1 CMS191 12/26/23 5:33
1S01D? INVALID STATEMENT.

EOJ NO NAME DATE 12/27/23,CLOCK 05/39/20


?--- OK????????????????? ID=0265 NOTHING?????????? LINE=000001 OF 000002 CASE=U
// JOB NOTHING DATE 12/27/23,CLOCK 05/39/20
EOJ NOTHING DATE 12/27/23,CLOCK 05/39/20,DURATION 00/00/00



I have another JCL deck I had tried putting together based on some commands I found in one of the DOS/VS manuals on bitsavers; this deck specifically:


type listio jcl

// JOB CMSUSER
// LISTIO
// PAUSE
/&

Ready; T=0.01/0.01 05:51:42



If I then try submitting this to DOS/VS:


punch listio jcl
PUN FILE 0272? TO? DOSVS??? COPY 01 NOHOLD
Ready; T=0.01/0.01 05:52:12


I get another round of this:


16 BG :READ? NOTHING? JCL????? A1 CMS191 12/26/23?? 5:33
17*BG 1S01D? INVALID STATEMENT.
18
19
20
0D07D? ENTER RESPONSE
BG



****?? NOTE that in spite of the fact that I punched "LISTIO JCL", DOS/VS is reading "NOTHING JCL" - it looks like there is a delay and it reads one JCL deck after I submit the next one???



If I press ENTER to clear that one out then submit NOTHING JCL again, then I get this on the DOS/VS console:


14 BG :READ? LISTIO?? JCL????? A1 CMS191 12/26/23?? 5:48
15*BG 1S01D? INVALID STATEMENT.
16
17
18
19
20
0D07D? ENTER RESPONSE
BG



Now I get the LISTIO JCL...? after ENTER:


?01 BG
?02 BG EOJ NO NAME
?03??? DATE 12/27/23,CLOCK 05/54/39
?04 F1 1Q34I? LST WAITING FOR WORK ON 00E
?05 BG // JOB CMSUSER
?06??? DATE 12/27/23,CLOCK 05/54/39
?07*BG 1S03D? INVALID STATEMENT.


ENTER again:


08 BG
09 BG // PAUSE



ENTER again:



10 BG
11 BG EOJ CMSUSER
12??? DATE 12/27/23,CLOCK 05/55/29,DURATION 00/00/49
13 F1 1Q34I? LST WAITING FOR WORK ON 00E
14 F1 1Q34I?? BG WAITING FOR WORK





So my current issues are that there seems to be a one-deck lag between submitting a JCL deck from CMS and processing that deck in DOS/VS, and that for some reason my JCL seems to be invalid, which I can guess I may have gotten something wrong in my LISTIO JCL, but the NOTHING JCL looks like it should be right?


I do have the JCL decks set as fixed format 80 columns in CMS...



Here are the print files that get spooled to CMSUSER when LISTIO JCL is processed:


?--- OK????????????????? ID=0276 AUTONAME????????? LINE=000001 OF 000003 CASE=U
:READ? LISTIO?? JCL????? A1 CMS191 12/26/23 5:48
1S01D? INVALID STATEMENT.
EOJ NO NAME DATE 12/27/23,CLOCK 05/54/39



?--- OK????????????????? ID=0277 CMSUSER?????????? LINE=000001 OF 000006 CASE=U
// JOB CMSUSER DATE 12/27/23,CLOCK 05/54/39
// LISTIO
// LISTIO
1S03D? INVALID STATEMENT.
// PAUSE
EOJ CMSUSER DATE 12/27/23,CLOCK 05/55/29,DURATION 00/00/49

OK...ID10T error.? I got the file updated.

I found this thread from earlier in the year, so hope it is not too old to resurrect.

I am also trying to update my SYSTEM NETID file on S.

When I access the disk D (RW) and make the updates, then follow these commands, the file does not update:

DEF STOR 16M
IPL 190
SAVESYS CMS

However, after IPL, it is still here on the D drive (which is S R/W).

Help please!

I have the NJE connection between RSCS under VM CE 1.2 and MVS TK5 Update 2 running now.? I am using SDL Hercules 4.6.

Thanks to all those who helped, offered help, and to Mr. Coghlan for the code.

Hi Daniel,

I'd recommend that you use SDL Hercules 4.5 or 4.6; the TCPNJE driver is already in those releases and is stable.? I've been using NJE with SDL Hercules for since 2018.? The problem with Hercules 4.0 is that it is not maintained and is quite out of date.

VM/370 RSCS with Mr. Coghlan's modifications for NJE work perfectly in the SDL Hercules environment, so there is no need to regress back to Hercules 3.x unless you just want to.? I can likely help you with getting RSCS running if you have the modifications.

Regards,
Bob

Thanks.? I'll reach out to Mr. Coghlan.

On 12.18.2023 16:44, Daniel L. Srebnick via groups.io wrote:

I am running Hercules 4.0, which seems to have the TCP NJE code built in.? It looks like the Peter Coghlan code was developed for Hercules 3.x.? Am I correct?

If I am correct, is there a different process to get RSCS working with Hercules 4.x?

The NJE device code in Hyperion/Hercules 4.x is his code that he developed
for 3.x. His NJE line driver for VM/370 will work with the NJE device in
Hercules 4.x, but if you run into trouble and need his help, I suspect he
would first want to you to switch to Hercules Spinhawk and report the
problem based on that, since that's the code base he uses.

What you need from him is the software to install into VM/370 itself to use
the Hercules TCP NJE device.

-Matthew

I am running Hercules 4.0, which seems to have the TCP NJE code built in.? It looks like the Peter Coghlan code was developed for Hercules 3.x.? Am I correct?

If I am correct, is there a different process to get RSCS working with Hercules 4.x?

I have read .

I have also read the RSCS MEMO that is part of CE 1.2.

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.

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

开云体育

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

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.