Re: tool to detect overlapping DCSS or named segments

#4105

Hi, Dave,

Thanks for that.? ?Where can I find a copy of SNTPARS EXEC?

Mark

Re: tool to detect overlapping DCSS or named segments

#4104

开云体育

Mark,

?

Well VM/SP has a “SNTMAP” (Usually pronounced SNOTMAP) but of course we don’t

There is an SNTPARS Rexx Exec but no idea how good it is.

?

Dave

?

Show quoted text

From: [email protected] <[email protected]> On Behalf Of Mark Waterbury
Sent: 23 March 2022 16:32
To: [email protected]
Subject: [h390-vm] tool to detect overlapping DCSS or named segments

?

Hi, All,

Does anyone recall any tool to identify any DCSS or named segments that potentially overlap each other if used at the same time??

Looking for something similar to DIRMAP EXEC of old, that works with the DMKSNT ASSEMBLE source or a compiled form of that (DMKSNT TEXT)?

Thanks in advance,

Mark S. Waterbury

tool to detect overlapping DCSS or named segments

#4103

Hi, All,

Does anyone recall any tool to identify any DCSS or named segments that potentially overlap each other if used at the same time??

Looking for something similar to DIRMAP EXEC of old, that works with the DMKSNT ASSEMBLE source or a compiled form of that (DMKSNT TEXT)?

Thanks in advance,

Mark S. Waterbury

Re: ASSIST port question

#4102

On Sat, Mar 19, 2022 at 04:27 AM, Bob Bolch wrote:

Are the files on the TAPEMAP 191 disk on VM370CE any part of the ASSIST port to CMS that you were working on?

Today, finally, I have fingers crossed, finished the implementation of ASSIST.? The files, documentation and upload to this group, of the ASSIST package, complete and usable. I welcome questions, comments, criticisms.

These are the files I found on TAPEMAP 191. I am not using them for my port.

It is incomplete, as I can't find a number of the original files from PSU/NIU. Files like documentation, macro libraries, and so on, needed for a complete install, and use.

XLIST: * * C?????????????????????????????????????? Lines 1-38/115? XLIST V1.2.5
? Filename Filetype Fm? Format??? Recs Blocks? Date?????? Time?? Label
? AS?????? EXEC???? C1? V??? 71????? 8????? 1? 2002-08-22 12:06? TAP191
? ASIVP??? JOB????? C1? F??? 80??? 144???? 15? 2002-08-21 11:40? TAP191
? ASSIST?? ASSEMBLE C1? F??? 80? 28857?? 2886? 2002-08-22 11:13? TAP191
? ASSIST?? LISTING? C1? F?? 121? 34167?? 5168? 2002-08-22 11:31? TAP191
? ASSIST?? MACLIB?? C1? F??? 80??? 107???? 11? 2002-08-22 11:30? TAP191
? ASSIST?? MAP????? C5? F?? 100??? 154???? 20? 2002-08-22 11:34? TAP191
? ASSIST?? MODULE?? C1? V 65535????? 4???? 90? 2002-08-22 11:34? TAP191
? ASSIST?? SYSPRINT C1? F?? 133??? 591???? 99? 2002-08-22 12:06? TAP191
? ASSIST?? SYSPUNCH C1? F??? 80??? 100???? 10? 2002-08-22 12:06? TAP191
? ASSIST?? TEXT???? C1? F??? 80?? 1480??? 148? 2002-08-22 11:31? TAP191

?... Mark S.

2 files uploaded #file-notice

[email protected] Notification

#4101

The following files and folders have been uploaded to the Files area of the [email protected] group.

By: Mark A. Stevens <marXtevens@...>

ASSIST port question

#4100

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

#4099

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

#4098

Thanks René, that worked like a charm it seems.?

regards
Michael

Re: Hercules with VM/370 on Linux in the background - erronous behaviour

#4097

开云体育

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,

搁别苍é.

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

#4096

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

?? ?

Show quoted text

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

#4095

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

#4094

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?

Show quoted text

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

#4093

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

Show quoted text

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

#4092

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

#4091

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

#4090

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

Show quoted text

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

#4089

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

#4088

开云体育

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

?

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

#4087

Dear Group,

is there a way to figure out if there is place for? a (new) minidisk allocation on a volume??

kind regards
Michael

Re: COBOL compile error

#4086

Found in the "extended sixpack" direct. :-) Now transferring to my VM/370 installation..

kind regards
Michael