Keyboard Shortcuts
Likes
- H390-Vm
- Messages
Search
This group is for all folks running the original IBM VM/370 Release 6 operating system (or later (e.g. VMTCE (Community Edition)) on Hercules. Like the other early IBM operating systems this version has always been in the public domain and so can be freely distributed. The base version as supplied by IBM is lacking in many facilities. IBM solved this by providing additional extension products which were licensed and so are not available. There are however many user enhancements available which can be installed. In addition, in order to get users up and running quickly updated "releases" of VM/370 included the most popular updates are available for download, so novices can start to learn VM without having to delve into the system internals. It is intended that this wiki will provide information on the base release and these updates.
The available versions are here :-
?
?
MVS Batch Ouput from VM/CMS
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? |
REXX Program to read CP Directory
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. |
Re: NJE
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.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 |
Re: NJE
Hi Dan, VMCE 1.1.2 RSCS does not support the NJE interface?because?the developer considers the code incomplete, and? does not want to allow it to be included.? Bob Bolch On Wed, Dec 13, 2023 at 6:37?PM Daniel L. Srebnick via <dan=[email protected]> 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. |
NJE
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 |
Re: CMSBATCH Output
Thanks to Rene and Bob, I was able to get it all worked out. ?I now get back 2 files in my RDR, a console and a printer. ?Here's how I set it up: /JOB DAN 1234 TESTJOB cp spool console to dan cp spool printer to dan cp link dan 191 191 rr access 191 b/a filedef sysprint terminal ? <<< This is for the console output. cobol testprg1 print testprg1 listing ? ? ? ? ? <<< ?This is for the program listing. filedef sysout printer ? ? ? ? <<< This is for the COBOL DISPLAY statement output. global txtlib cob360r load testprg1 start release 191 cp detach 191 /* On my VM: q rdr ORIGINID FILE CLASS RECDS CPY HOLD CMSBATCH 0296 T CON 000038 01 NONE CMSBATCH 0297 A PRT 000181 01 NONE On the OPERATOR console: q prt 01:17:12 01:17:12 NO PRT FILES It was my console output that was ending up on the system printer queue in class T, because I had not spooled it back to me. Now to turn this into a submit EXEC. On Thu, 2023-11-30 at 15:46 -0800, Ren¨¦ Ferland wrote:
|
Re: CMSBATCH Output
On Thu, Nov 30, 2023 at 03:09 PM, Bob Polmanter wrote:
CP SPOOL CONSOLE TO userid START I wonder if it is necessary to explicitly START/STOP CLOSE. For sure I never did. :-) All my batch jobs starts with the statements:
|
Re: CMSBATCH Output
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 |
Re: CMSBATCH Output
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 /* |
Re: CMSBATCH Output
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 |
CMSBATCH Output
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? |
Re: VM370CE
On Tue, Nov 28, 2023 at 05:14 PM, Frank D. Engel, Jr. wrote:
Actually no, this is normal behavior. With EE,? the number of columns displayed depends on the filetype and the corresponding specification is searched in PROFILE EE. If you add the line FTDEFAULTS DIRECT F 80 M 72 to PROFILE EE, you should see things better in 80x24 mode. Or, indeed, you can work in 132x27 mode instead. Check the file "mecaff-tools-and-console-1.2.5.zip" in the Files section of h390-vm. The ZIP contains the file "MECAFF-tools-Manual-1.2.5.pdf" which explains on page 6 the behavior of EE you observed. Cheers, Rene FERLAND, Montreal |
Re: VM370CE
¿ªÔÆÌåÓýInteresting... I tried that, but it looks like it is off a bit in calculating
where to put things:
File: USER???? DIRECT?? A1? RECFM: F
LRECL:? 80(80) Lines:?? 568 Current:?? TOP
I tried changing the setting to 3279-5-E which is a 132x27 setting and that seems a bit better:
File: USER???? DIRECT??
A1????????????????????????????????????????????????????? RECFM: F
LRECL:? 80(80) Lines:?? 568 Current:??? 40
I can work with that - thank you!
On 11/28/23 15:58, Bob Bolch wrote:
|
Re: VM370CE
Good work, Rene. I will make a note of the setting in the next README. Bob On Tue, Nov 28, 2023, 1:38?PM Ren¨¦ Ferland <ferland.rene@...> wrote: On Mon, Nov 27, 2023 at 11:11 AM, Bob Bolch wrote: |
Re: VM370CE
On Mon, Nov 27, 2023 at 11:11 AM, Bob Bolch wrote:
However, the ''No fullscreen support present" is NOT what we should be seeing.Hello Bob, I was able to reproduce that behavior with ZOC. The problem disappeared when I change the terminal from 3278-2 to 3279-2-E. So could this be related to the colors used in the EE screen? That would be consistent with EDIT working when 3278-2 is specified. Cheers, Rene FERLAND, Montreal |
Re: VM370CE
Hi Frank, Thanks for the screen shots. Your setup looks correct. However, the ''No fullscreen support present" is NOT what we should be seeing. I will keep looking onto the issue. Bob Bolch On Mon, Nov 27, 2023, 10:17?AM Frank D. Engel, Jr. <fde101@...> wrote:
|