Mark Stevens,
Are the files on the TAPEMAP 191 disk on VM370CE any part of the ASSIST port to CMS that you were working on?
Thanks/Bob
|
Re: Minidisk allocation planning
Hi Bob,
yes, my wrong...guessing free device addresses in conjunction with dev types is a bad idea. I've checked dmkrio assemble on F (not dared to change it) and looked up a free address for a 3350 - now everything worked as supposed
and I restored my vsamio vmarc to that disk. Work in progress! :-)?
regards
Michael
|
Re: Hercules with VM/370 on Linux in the background - erronous behaviour
Thanks René, that worked like a charm it seems.?
regards
Michael
|
Re: Hercules with VM/370 on Linux in the background - erronous behaviour
Hi Michael,
to avoid this problem I run the remote sessions under tmux - you can also use screen. This makes sure that losing (or hanhing up) a connection does not interfere with you hercules sessions.? To illustrate, this is the process:
ssh to your remote machine tmux start hercules for a specific os - some need manual action and others not ctrl-b c to create a new session in the same tmux instance start other hercules instance ctrl b d to fall back into the ssh session logoff.
At any point the connection can be broken - a new ssh session can be started, and a ’tmux attach’ brings me back where I was.
After a tmux attach, ctrl-b n (next) enables one to choose the intended hercules console.
I consider this a sine-qua-non for operation of Hercules on remote machines.
best regards,
搁别苍é.
toggle quoted message
Show quoted text
On 14 Mar 2022, at 16:51, Bob Bolch < Bob@...> wrote:
Hi Michael, Maybe others can help. I just don't understand anything about your environment, because I don't have the background experience required.
I can say that the startup and shutdown?of VM depend on the OPERATOR user ID being logged on.? Bob
?? ? On Mon, Mar 14, 2022 at 11:34 AM Michael Grom < macbaer@...> wrote: Hi Bob, the thing is, I have to start hercules from a ssh session on a remote server which is not supposed to be open all time. Normally, when the ssh session terminates, the running shell at the remote server gets a SIGHUP (hang up) and terminates the processes which are sensitive to SIGHUP. This is prevented by "nohup" - hence the name. You basically detach a background process from the starting terminal. Works with the startup of TK4- but not with the startup of VM which seems to depend on "stdin" (the keyboard input of the terminal) to be available.?
regards
Michael
|
Re: Hercules with VM/370 on Linux in the background - erronous behaviour
Hi Michael, Maybe others can help. I just don't understand anything about your environment, because I don't have the background experience required.
I can say that the startup and shutdown?of VM depend on the OPERATOR user ID being logged on.? Bob
?? ?
On Mon, Mar 14, 2022 at 11:34 AM Michael Grom < macbaer@...> wrote: Hi Bob,
the thing is, I have to start hercules from a ssh session on a remote server which is not supposed to be open all time. Normally, when the ssh session terminates, the running shell at the remote server gets a SIGHUP (hang up) and terminates the processes which are sensitive to SIGHUP. This is prevented by "nohup" - hence the name. You basically detach a background process from the starting terminal. Works with the startup of TK4- but not with the startup of VM which seems to depend on "stdin" (the keyboard input of the terminal) to be available.?
regards
Michael
|
Re: Hercules with VM/370 on Linux in the background - erronous behaviour
Hi Bob,
the thing is, I have to start hercules from a ssh session on a remote server which is not supposed to be open all time. Normally, when the ssh session terminates, the running shell at the remote server gets a SIGHUP (hang up) and terminates the processes which are sensitive to SIGHUP. This is prevented by "nohup" - hence the name. You basically detach a background process from the starting terminal. Works with the startup of TK4- but not with the startup of VM which seems to depend on "stdin" (the keyboard input of the terminal) to be available.?
regards
Michael
|
Re: Minidisk allocation planning
Hi Michael, I could better understand?what you are doing if you tell me what commands you issued, what the responses are, and what the error messages say.?
I do know that 6D5 is defined to the system as a 2314 disk, not a 3350 in the DMKRIO? ASSEMBLE file.
I suggest you try again using VM50U0 to define your new minidisk. /Bob?
On Mon, Mar 14, 2022 at 10:54 AM Michael Grom < macbaer@...> wrote: Thanks Bob, I will probably do so - especially because I ran into another trouble:
?
DMKLNK117E USERID VSAMIO NOT LINKED; VOLID 191 CONFLICT
what happened??
created disk image using dasdinit of type 3350 with label VSAMIO and attached it @ cuu = 06D5 in the config file
created user vsamio in the directory with minidisk 191 for vol VSAMIO
added attach 6d5 to system as VSAMIO in the profile exec of autolog1
?kind regards
Michael
|
Re: Hercules with VM/370 on Linux in the background - erronous behaviour
Hi Michael, I do not understand what you are trying to do here. When the documented procedure?to bring up VM/370 is followed, the user ID "OPERATOR" is logged on. That ID is used to issue the various system commands to bring up the system, and to issue SHUTDOWN to take it down when you are done. The supplied configuration runs the OPERATOR user ID session through a simulated line mode (not fullscreen 3270) session.?
I have no idea what nohup is or does, but having the OPERATOR ID logged on is the means to issue the SHUTDOWN command. That's why we expect it to remain logged on.? Bob
On Mon, Mar 14, 2022 at 11:02 AM Michael Grom < macbaer@...> wrote: Dear Group,
while fiddling with the user directory, I noticed a strange behaviour with hercules that I haven't seen from hercules running TK4- on the same machine. I usally start hercules for mvs with
?
nohup ./mvs > mvs.out 2>&1 &?
?
and everything is fine. Cloned this as
nohup hercules -f vm370ce.conf > vm370.out 2>&1 & and get some errors regarding stdin
But even worse, entering "/SHUTDOWN" through the web console doesn't seem to shut down the system and hercules properly...edits to the user directory have been lost so I reckon data has not been flushed to the shadow disks properly.?
running hercules with VM/370 "headless" would be really desirable for me.
kind regards
Michael
|
Hercules with VM/370 on Linux in the background - erronous behaviour
Dear Group,
while fiddling with the user directory, I noticed a strange behaviour with hercules that I haven't seen from hercules running TK4- on the same machine. I usally start hercules for mvs with
?
nohup ./mvs > mvs.out 2>&1 &?
?
and everything is fine. Cloned this as
nohup hercules -f vm370ce.conf > vm370.out 2>&1 & and get some errors regarding stdin
But even worse, entering "/SHUTDOWN" through the web console doesn't seem to shut down the system and hercules properly...edits to the user directory have been lost so I reckon data has not been flushed to the shadow disks properly.?
running hercules with VM/370 "headless" would be really desirable for me.
kind regards
Michael
|
Re: Minidisk allocation planning
Thanks Bob, I will probably do so - especially because I ran into another trouble:
?
DMKLNK117E USERID VSAMIO NOT LINKED; VOLID 191 CONFLICT
what happened??
created disk image using dasdinit of type 3350 with label VSAMIO and attached it @ cuu = 06D5 in the config file
created user vsamio in the directory with minidisk 191 for vol VSAMIO
added attach 6d5 to system as VSAMIO in the profile exec of autolog1
?kind regards
Michael
|
Re: Minidisk allocation planning
VMCE supplies two preconfigured empty disk packs, labelled VM50U0 and VM50U1 that are to be used only for information put there by the end user. If you use those disk packs for installation specific minidisks, then when a new VM370CE release comes out, you can copy the user volumes to the new system release, and just add the new directory entries.
Bob
On Mon, Mar 14, 2022 at 6:21 AM Michael Grom < macbaer@...> wrote: Hi Dave,
thanks for the pointer. Using a dedicated new pack is definitely a good point here, not meddling with the distribution packs.?
kind regards
Michael
|
Re: Minidisk allocation planning
Hi Dave,
thanks for the pointer. Using a dedicated new pack is definitely a good point here, not meddling with the distribution packs.?
kind regards
Michael
|
Re: Minidisk allocation planning
Michael, Try “DISKMAP”. Its on MAINT’s B disk but there is a help file. I would say though if you want more minidisks add a pack for yourself. Makes upgrades simpler. Dave ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Michael Grom
Sent: 14 March 2022 09:14
To: [email protected]
Subject: [h390-vm] Minidisk allocation planning? Dear Group, is there a way to figure out if there is place for? a (new) minidisk allocation on a volume??
kind regards
Michael
|
Minidisk allocation planning
Dear Group,
is there a way to figure out if there is place for? a (new) minidisk allocation on a volume??
kind regards
Michael
|
Found in the "extended sixpack" direct. :-) Now transferring to my VM/370 installation..
kind regards
Michael
|
Dear René,
downloaded your 6pack, ipl'ed VM and searched the sixpack direct up and down for that virtual machine, to no avail.?
kind regards
Michael
|
On Sun, Mar 13, 2022 at 01:01 AM, Michael Grom wrote:
I was watching moshix' M94 video (Part 2 on how to use VSAM on VM/370 from COBOL + PL/I using VSAMIO)
Michael,
?
Be aware, again, that in Moshix video M94, VSAMIO usage is illustrated on a cloud extended Sixpack 1.2, which is different from VM/370 CE. In particular, the VSAMIO minidisk containing the MACLIBs, TXTLIB, and example programs used in the video is NOT available on VM/370 CE. Moreover, Jay Moseley has changed the way he distributes VSAMIO so the video instructions regarding its download and install (if there are any, I don't remember) are most probably obsolete now.
?
If you are ever interested by VSAMIO, one possible way to get it on VM/370 CE would be to transfer it from my old obsolete 6PExt. On that system, minidisk 191 of the NOLOG virtual machine VSAMIO contains all the stuff mentionned in the video.
?
Cheers,
?
Rene FERLAND, Montreal
|
Thanks :-) didn't know about that ... much easier than my
MOVEFILE approach with FILEDEFs
Am 13.03.2022 um 12:44 schrieb Dave
Wade:
toggle quoted message
Show quoted text
WHy? COPYFILE (REPL is fine. It creates a new
file and then renames the source at the end.
?
Dave
?
?
Hello Michael,
my guess is that the source file needs to be FIXED 80.
I wrote a small EXEC to convert such LRECL V files to LRECL
F.
Don't have access to my VM machine at the moment,
but it goes like this:
two filedefs, INPUT with LRECL V, output with LRECL FIXED 80,
MOVEFILE INPUT OUTPUT
then rename to result to original
You could look at my Stanford Pascal Compiler sites, maybe
you find the EXEC there:
HTH
kind regards
Bernd
?
?
Am 13.03.2022 um 10:01 schrieb Michael
Grom:
Dear Group,
I was watching moshix' M94 video (Part 2 on how to use VSAM
on VM/370 from COBOL + PL/I using VSAMIO) and thought I give
COBOL a try, first, without?
the VSAM example. So I prepped
a very small program and tried to compile. Before that, I
linked to COBOL 191 and accessed the mini disk as B.?
cobol mycob
SYSTEM/360 COBOL COMPILER? ? ? ? ? CB545 V2 LVL78
OPEN ERROR CODE '03' ON 'SYSIN '.
?
Ready; T=0.01/0.04 08:48:47
That was kind of unexpected to me. As René Ferland
explained, the Cobol compiler is significantly older than
the system itself and was lifted from a previous version of
MVS. Hence the use of VSAMIO which brings VSAM capability to
these old compilers. However, the problem seems to start
much earlier, at least with my?
VM/370 CE 1.1 installation.
query cplevel
SYSTEM 4381-A
VM/370 Community Edition Version? 1 Release? 1.1 03/10/22
08:54:40
?
Ready; T=0.01/0.01 08:56:28
update: I created the source file with "ee" without any
further specification, quite naively. A dir * cobol yields
Filename Filetype Fm? Format? ? Recs Blocks? ? Date? ?
?Time? ?Label
MYCOB? ? COBOL? ? A1? V? ? 32?
? ?10? ? ? 1? 03/12/22? ?16:29? CMS191
Could it be the old compiler chokes because of the file
attributes V and lrecl=32??
Is there a way to specify that beforehand or to change the
record attributes later??
kind regards
Michael
|
WHy? COPYFILE (REPL is fine. It creates a new file and then renames the source at the end. ? Dave ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Bernd Oppolzer via groups.io
Sent: 13 March 2022 09:20
To: [email protected]
Subject: Re: [h390-vm] COBOL compile error? Hello Michael, my guess is that the source file needs to be FIXED 80. I wrote a small EXEC to convert such LRECL V files to LRECL F.
Don't have access to my VM machine at the moment,
but it goes like this: two filedefs, INPUT with LRECL V, output with LRECL FIXED 80,
MOVEFILE INPUT OUTPUT
then rename to result to original You could look at my Stanford Pascal Compiler sites, maybe you find the EXEC there:
HTH
kind regards Bernd ? ? Am 13.03.2022 um 10:01 schrieb Michael Grom: Dear Group, I was watching moshix' M94 video (Part 2 on how to use VSAM on VM/370 from COBOL + PL/I using VSAMIO) and thought I give COBOL a try, first, without? the VSAM example. So I prepped a very small program and tried to compile. Before that, I linked to COBOL 191 and accessed the mini disk as B.? cobol mycob SYSTEM/360 COBOL COMPILER? ? ? ? ? CB545 V2 LVL78 OPEN ERROR CODE '03' ON 'SYSIN '. ? Ready; T=0.01/0.04 08:48:47
That was kind of unexpected to me. As René Ferland explained, the Cobol compiler is significantly older than the system itself and was lifted from a previous version of MVS. Hence the use of VSAMIO which brings VSAM capability to these old compilers. However, the problem seems to start much earlier, at least with my?
VM/370 CE 1.1 installation. query cplevel SYSTEM 4381-A VM/370 Community Edition Version? 1 Release? 1.1 03/10/22 08:54:40 ? Ready; T=0.01/0.01 08:56:28
update: I created the source file with "ee" without any further specification, quite naively. A dir * cobol yields Filename Filetype Fm? Format? ? Recs Blocks? ? Date? ? ?Time? ?Label MYCOB? ? COBOL? ? A1? V? ? 32? ? ?10? ? ? 1? 03/12/22? ?16:29? CMS191
Could it be the old compiler chokes because of the file attributes V and lrecl=32??
Is there a way to specify that beforehand or to change the record attributes later?? kind regards
Michael
|
Michael, Yes it needs FB80 so :- ? copy mycob cobol a = = = (repl recfm f lrecl 80 ? or before you save in EE do ? RECFM F LRECL 80 ? You can customize it with a PROFILE EE file to set COBOL to be FB80 ? FTDEFaults COBOL F 80 ? Take a look at “FSHELP EE” and the sections on profile and configuration. (If you use FSHELP you can move the cursor over the entry you want to view and hit PF1) ? Dave ? ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Michael Grom
Sent: 13 March 2022 09:01
To: [email protected]
Subject: [h390-vm] COBOL compile error? Dear Group, I was watching moshix' M94 video (Part 2 on how to use VSAM on VM/370 from COBOL + PL/I using VSAMIO) and thought I give COBOL a try, first, without? the VSAM example. So I prepped a very small program and tried to compile. Before that, I linked to COBOL 191 and accessed the mini disk as B.? cobol mycob SYSTEM/360 COBOL COMPILER? ? ? ? ? CB545 V2 LVL78 OPEN ERROR CODE '03' ON 'SYSIN '. ? Ready; T=0.01/0.04 08:48:47
That was kind of unexpected to me. As René Ferland explained, the Cobol compiler is significantly older than the system itself and was lifted from a previous version of MVS. Hence the use of VSAMIO which brings VSAM capability to these old compilers. However, the problem seems to start much earlier, at least with my?
VM/370 CE 1.1 installation. query cplevel SYSTEM 4381-A VM/370 Community Edition Version? 1 Release? 1.1 03/10/22 08:54:40 ? Ready; T=0.01/0.01 08:56:28
update: I created the source file with "ee" without any further specification, quite naively. A dir * cobol yields Filename Filetype Fm? Format? ? Recs Blocks? ? Date? ? ?Time? ?Label MYCOB? ? COBOL? ? A1? V? ? 32? ? ?10? ? ? 1? 03/12/22? ?16:29? CMS191
Could it be the old compiler chokes because of the file attributes V and lrecl=32??
Is there a way to specify that beforehand or to change the record attributes later?? kind regards
Michael
|
Michael Grom
René Ferland