Hello,
I'm needing to change the FCB1 functionality under VM/ESA 2.4 and I've no clue how to get started.? The IBM publications refer to a 3211FCB1 ASSEMBLE but I' don't know where it is.? I'm wanting to change the FCB to start print on line 4 instead of line 1.
|
On Wed, Apr 6, 2022 at 09:26 AM, Bob Bolch wrote:
OK, I'm interested in what you mean by 'usable modules'.
Could you elaborate on the filetype produced and how they are used, please?
Sorry for the delay,? my wife and I are watching our grandson 4 days/week, and the off day gets used for catchup.
In the ASSIST package that is in this group's files section,
/g/h390-vm/files/ASSIST_VM370_etc
and the github entry,
is a tape (2022-03-21.ASSIST.191.aws ) that is loaded to the ASSIST 191 minidisk, which contains a script ASBUILD? EXEC, which contains the following lines which build a usable LOADLIB, for non-ASSIST programs to use when they call one of the routines, in the LOADLIB....SAY 'Building XMSOURCE LOADLIB. Allows routines to be used by'SAY 'non-ASSIST Assembler programs.'????????????????????????????????????? /* SYSLIB is input file of TEXT */????????????????????????????????????? /* records to be link edited.?? */'FILEDEF SYSLIB DISK XMSOURCE TXTLIB A (PERM'????????????????????????????????????? /* Link edit each member and put*/????????????????????????????????????? /* it in a LOADLIB.???????????? */'LKED XXXXDECI (XREF LIBE XMSOURCE PRINT''LKED XXXXDECO (XREF LIBE XMSOURCE PRINT''LKED XXXXGET? (XREF LIBE XMSOURCE PRINT''LKED XXXXOPEN (XREF LIBE XMSOURCE PRINT''LKED XXXXPNCH (XREF LIBE XMSOURCE PRINT''LKED XXXXPRNT (XREF LIBE XMSOURCE PRINT''LKED XXXXPUT? (XREF LIBE XMSOURCE PRINT''LKED XXXXREAD (XREF LIBE XMSOURCE PRINT''LKED XXXXSNAP (XREF LIBE XMSOURCE PRINT''FILEDEF SYSLIB CLEAR'??????????????? /* Remove SYSLIB definition.??? */
...
The original VM/SP script I wrote, (see tape, 2022-03-21.ASSIST.193.aws, ASSIST 193,? XMSOLKED EXEC), just does the the above. I copied the code verbatim into my ASBUILD EXEC, and as far as I can tell it 'works as advertised.'I'm trying to find a test program that I used, but so far, it is escaping my attention.?... Mark S.
|
Hi Mark,? OK, I'm interested in what you mean by 'usable modules'. Could you elaborate on the filetype produced and how they are used, please? /B
On Wed, Apr 6, 2022 at 10:16 AM Mark A. Stevens via <marXtevens= [email protected]> wrote: On Wed, Apr 6, 2022 at 04:07 AM, Bob Bolch wrote:
Since LKED?produces an object which?cannot be loaded or executed in VM/370 CMS,
why do we want to document it??
Bob
Because it CAN and DOES produce usable modules. :-) I used it for building ASSIST for VM/370. This is how I discovered there was no online help for it.
Of course, as Dave stated it can produce unusable modules, too.
?... Mark S.
|
On Wed, Apr 6, 2022 at 04:07 AM, Bob Bolch wrote:
Since LKED?produces an object which?cannot be loaded or executed in VM/370 CMS,
why do we want to document it??
Bob
Because it CAN and DOES produce usable modules. :-) I used it for building ASSIST for VM/370. This is how I discovered there was no online help for it. Of course, as Dave stated it can produce unusable modules, too. ?... Mark S.
|
Re: OS Link Macro - Was More Help Files
Hi Dave, The OS simulation LOAD SVC calls DMSSLN to load either a MODULE file or a TEXT file.? In VM/SP, CMS added a relocating loader and could then process a relocatable MODULE or a LOADLIB member. Only non-relocatable MODULE files can be built ior loaded in VM/370.
When I was trying to make a NUCXLOAD command for VM/370, I spent a couple weeks trying to understand the relocation section of a modern CMS MODULE file, to see if I could make a relocating loader. I did not get very far, and would like to get back to it at some point. TEXT files obviously get relocated when brought into memory by the LOAD or INCLUDE commands, so I ended up with a NUCXTEXT command to load a nucleus extension from a TEXT file in VM/370. I did not want to look at the relocatable loader code from a modern CMS, to avoid copyright infringement, but I did look at binary relocatable MODULE files from z/VM to understand the data area added to the end of a MODULE. That analysis is still incomplete.?? Bob
Bob, ? So how does OS LINK work in VM/370? Do you need to construct an auxiliary directory?? It says its supported in the manuals? Or modules that load at other than the default address… ? Dave ? ? ? Hi Dave, I see that the VM/370 LKED?and GEN3705 modules are made from DMSLKD, DMSGRN, and DMSNCP. DMSZAP can?patch?a LOADLIB file. The only 'loader' function in VM/370 is to read a 3705 control program module and write it to a page-format core image with the SAVENCP command.? A relocating loader for CMS was not added until VM/SP. ? Bob, ? I am not so sure that it can’t be loaded or executed! I would have thought if the LOADLIB was assigned to the correct DD then SVC ?6/LINK Macro would load code from it. In addition I was hoping to fix MVS version the ASM3705 assembler so it works under VM. That appears to be the only part of the NCP support that we are missing. There is a copy of the MVS version in one of the MVS groups. The CMS interface module exists in CMS…. … and lastly I hate ?having undocumented programs…. ? Dave ? ? Since LKED?produces an object which?cannot be loaded or executed in VM/370 CMS, why do we want to document it?? ? >From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via
>Sent: 06 April 2022 02:23
>To: [email protected]
>Subject: Re: [h390-vm] More Help Files
>
>
>>On Tue, Apr 5, 2022 at 09:44 AM, Dave Wade wrote:
>>I have uploaded a few more helpfiles for ...
>>Dave,
>>
>Do you want/need me to review those?
It can't do too much harm. They were generally created on VM/370 where there is no spell check etc.
>I did find out we don't have online help for LKED (DOSLKED?).
No, I only looked at stuff on the "Y" disk. The next step will be to check what is on the "S".?
The Linkage Editor is documented in
GC20-1801-10_VM370_Sysgen_Rel_6_Jan80.pdf
Which you will find on "BitSavers". In there it says, on page number 310 (page 341 in the PDF)
Only a subset of the possible linkage editor control statements are meaningful in CMS. .Since the CMS interface program cannot examine the input data for the LKED command, all of the control statements are allowed, even though several of them result in the creation of a load module file which cannot be used under CMS. For both command options and control statements, see the publication "OS/VS Linkage Editor and Loader"
which leads me to believe that the Linkage editor is a direct port of the OS/VS Linkage Editor. It won't take long to create a help file from the manual.
> ... Mark S.
|
Re: OS Link Macro - Was More Help Files
Bob, ? So how does OS LINK work in VM/370? Do you need to construct an auxiliary directory? ?It says its supported in the manuals? Or modules that load at other than the default address… ? Dave ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Bob Bolch
Sent: 06 April 2022 12:26
To: [email protected]
Subject: Re: [h390-vm] More Help Files? Hi Dave, I see that the VM/370 LKED?and GEN3705 modules are made from DMSLKD, DMSGRN, and DMSNCP. DMSZAP can?patch?a LOADLIB file. The only 'loader' function in VM/370 is to read a 3705 control program module and write it to a page-format core image with the SAVENCP command.? A relocating loader for CMS was not added until VM/SP. ? Bob, ? I am not so sure that it can’t be loaded or executed! I would have thought if the LOADLIB was assigned to the correct DD then SVC ?6/LINK Macro would load code from it. In addition I was hoping to fix MVS version the ASM3705 assembler so it works under VM. That appears to be the only part of the NCP support that we are missing. There is a copy of the MVS version in one of the MVS groups. The CMS interface module exists in CMS…. … and lastly I hate ?having undocumented programs…. ? Dave ? ? Since LKED?produces an object which?cannot be loaded or executed in VM/370 CMS, why do we want to document it?? ? >From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via
>Sent: 06 April 2022 02:23
>To: [email protected]
>Subject: Re: [h390-vm] More Help Files
>
>
>>On Tue, Apr 5, 2022 at 09:44 AM, Dave Wade wrote:
>>I have uploaded a few more helpfiles for ...
>>Dave,
>>
>Do you want/need me to review those?
It can't do too much harm. They were generally created on VM/370 where there is no spell check etc.
>I did find out we don't have online help for LKED (DOSLKED?).
No, I only looked at stuff on the "Y" disk. The next step will be to check what is on the "S".?
The Linkage Editor is documented in
GC20-1801-10_VM370_Sysgen_Rel_6_Jan80.pdf
Which you will find on "BitSavers". In there it says, on page number 310 (page 341 in the PDF)
Only a subset of the possible linkage editor control statements are meaningful in CMS. .Since the CMS interface program cannot examine the input data for the LKED command, all of the control statements are allowed, even though several of them result in the creation of a load module file which cannot be used under CMS. For both command options and control statements, see the publication "OS/VS Linkage Editor and Loader"
which leads me to believe that the Linkage editor is a direct port of the OS/VS Linkage Editor. It won't take long to create a help file from the manual.
> ... Mark S.
|
Hi Dave, I see that the VM/370 LKED?and GEN3705 modules are made from DMSLKD, DMSGRN, and DMSNCP. DMSZAP can?patch?a LOADLIB file. The only 'loader' function in VM/370 is to read a 3705 control program module and write it to a page-format core image with the SAVENCP command.?
A relocating loader for CMS was not added until VM/SP. Bob
Bob, ? I am not so sure that it can’t be loaded or executed! I would have thought if the LOADLIB was assigned to the correct DD then SVC ?6/LINK Macro would load code from it. In addition I was hoping to fix MVS version the ASM3705 assembler so it works under VM. That appears to be the only part of the NCP support that we are missing. There is a copy of the MVS version in one of the MVS groups. The CMS interface module exists in CMS…. … and lastly I hate ?having undocumented programs…. ? Dave ? ? Since LKED?produces an object which?cannot be loaded or executed in VM/370 CMS, why do we want to document it?? ? >From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via
>Sent: 06 April 2022 02:23
>To: [email protected]
>Subject: Re: [h390-vm] More Help Files
>
>
>>On Tue, Apr 5, 2022 at 09:44 AM, Dave Wade wrote:
>>I have uploaded a few more helpfiles for ...
>>Dave,
>>
>Do you want/need me to review those?
It can't do too much harm. They were generally created on VM/370 where there is no spell check etc.
>I did find out we don't have online help for LKED (DOSLKED?).
No, I only looked at stuff on the "Y" disk. The next step will be to check what is on the "S".?
The Linkage Editor is documented in
GC20-1801-10_VM370_Sysgen_Rel_6_Jan80.pdf
Which you will find on "BitSavers". In there it says, on page number 310 (page 341 in the PDF)
Only a subset of the possible linkage editor control statements are meaningful in CMS. .Since the CMS interface program cannot examine the input data for the LKED command, all of the control statements are allowed, even though several of them result in the creation of a load module file which cannot be used under CMS. For both command options and control statements, see the publication "OS/VS Linkage Editor and Loader"
which leads me to believe that the Linkage editor is a direct port of the OS/VS Linkage Editor. It won't take long to create a help file from the manual.
> ... Mark S.
|
Bob, Mark, ? I popped a help file for LKED onto GIRHUB. As Bob says it may not be useful, but I really hate not having such things. ? Dave ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Dave Wade via groups.io
Sent: 06 April 2022 11:36
To: [email protected]
Subject: Re: [h390-vm] More Help Files? Bob, ? I am not so sure that it can’t be loaded or executed! I would have thought if the LOADLIB was assigned to the correct DD then SVC ?6/LINK Macro would load code from it. In addition I was hoping to fix MVS version the ASM3705 assembler so it works under VM. That appears to be the only part of the NCP support that we are missing. There is a copy of the MVS version in one of the MVS groups. The CMS interface module exists in CMS…. … and lastly I hate ?having undocumented programs…. ? Dave ? ? Since LKED?produces an object which?cannot be loaded or executed in VM/370 CMS, why do we want to document it?? ? >From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via
>Sent: 06 April 2022 02:23
>To: [email protected]
>Subject: Re: [h390-vm] More Help Files
>
>
>>On Tue, Apr 5, 2022 at 09:44 AM, Dave Wade wrote:
>>I have uploaded a few more helpfiles for ...
>>Dave,
>>
>Do you want/need me to review those?
It can't do too much harm. They were generally created on VM/370 where there is no spell check etc.
>I did find out we don't have online help for LKED (DOSLKED?).
No, I only looked at stuff on the "Y" disk. The next step will be to check what is on the "S".?
The Linkage Editor is documented in
GC20-1801-10_VM370_Sysgen_Rel_6_Jan80.pdf
Which you will find on "BitSavers". In there it says, on page number 310 (page 341 in the PDF)
Only a subset of the possible linkage editor control statements are meaningful in CMS. .Since the CMS interface program cannot examine the input data for the LKED command, all of the control statements are allowed, even though several of them result in the creation of a load module file which cannot be used under CMS. For both command options and control statements, see the publication "OS/VS Linkage Editor and Loader"
which leads me to believe that the Linkage editor is a direct port of the OS/VS Linkage Editor. It won't take long to create a help file from the manual.
> ... Mark S.
|
Bob, ? I am not so sure that it can’t be loaded or executed! I would have thought if the LOADLIB was assigned to the correct DD then SVC ?6/LINK Macro would load code from it. In addition I was hoping to fix MVS version the ASM3705 assembler so it works under VM. That appears to be the only part of the NCP support that we are missing. There is a copy of the MVS version in one of the MVS groups. The CMS interface module exists in CMS…. … and lastly I hate ?having undocumented programs…. ? Dave ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of Bob Bolch
Sent: 06 April 2022 10:07
To: [email protected]
Subject: Re: [h390-vm] More Help Files? Since LKED?produces an object which?cannot be loaded or executed in VM/370 CMS, why do we want to document it?? ? >From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via
>Sent: 06 April 2022 02:23
>To: [email protected]
>Subject: Re: [h390-vm] More Help Files
>
>
>>On Tue, Apr 5, 2022 at 09:44 AM, Dave Wade wrote:
>>I have uploaded a few more helpfiles for ...
>>Dave,
>>
>Do you want/need me to review those?
It can't do too much harm. They were generally created on VM/370 where there is no spell check etc.
>I did find out we don't have online help for LKED (DOSLKED?).
No, I only looked at stuff on the "Y" disk. The next step will be to check what is on the "S".?
The Linkage Editor is documented in
GC20-1801-10_VM370_Sysgen_Rel_6_Jan80.pdf
Which you will find on "BitSavers". In there it says, on page number 310 (page 341 in the PDF)
Only a subset of the possible linkage editor control statements are meaningful in CMS. .Since the CMS interface program cannot examine the input data for the LKED command, all of the control statements are allowed, even though several of them result in the creation of a load module file which cannot be used under CMS. For both command options and control statements, see the publication "OS/VS Linkage Editor and Loader"
which leads me to believe that the Linkage editor is a direct port of the OS/VS Linkage Editor. It won't take long to create a help file from the manual.
> ... Mark S.
|
Since LKED?produces an object which?cannot be loaded or executed in VM/370 CMS, why do we want to document it?? Bob
>From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via
>Sent: 06 April 2022 02:23
>To: [email protected]
>Subject: Re: [h390-vm] More Help Files
>
>
>>On Tue, Apr 5, 2022 at 09:44 AM, Dave Wade wrote:
>>I have uploaded a few more helpfiles for ...
>>Dave,
>>
>Do you want/need me to review those?
It can't do too much harm. They were generally created on VM/370 where there is no spell check etc.
>I did find out we don't have online help for LKED (DOSLKED?).
No, I only looked at stuff on the "Y" disk. The next step will be to check what is on the "S".?
The Linkage Editor is documented in
GC20-1801-10_VM370_Sysgen_Rel_6_Jan80.pdf
Which you will find on "BitSavers". In there it says, on page number 310 (page 341 in the PDF)
Only a subset of the possible linkage editor control statements are meaningful in CMS. .Since the CMS interface program cannot examine the input data for the LKED command, all of the control statements are allowed, even though several of them result in the creation of a load module file which cannot be used under CMS. For both command options and control statements, see the publication "OS/VS Linkage Editor and Loader"
which leads me to believe that the Linkage editor is a direct port of the OS/VS Linkage Editor. It won't take long to create a help file from the manual.
> ... Mark S.
>_._,_._,_
Dave
|
From: [email protected] <[email protected]> On Behalf Of Mark A. Stevens via groups.io
Sent: 06 April 2022 02:23
To: [email protected]
Subject: Re: [h390-vm] More Help Files
On Tue, Apr 5, 2022 at 09:44 AM, Dave Wade wrote:
I have uploaded a few more helpfiles for ...
Dave,
Do you want/need me to review those? It can't do too much harm. They were generally created on VM/370 where there is no spell check etc. I did find out we don't have online help for LKED (DOSLKED?). No, I only looked at stuff on the "Y" disk. The next step will be to check what is on the "S". The Linkage Editor is documented in GC20-1801-10_VM370_Sysgen_Rel_6_Jan80.pdf Which you will find on "BitSavers". In there it says, on page number 310 (page 341 in the PDF) Only a subset of the possible linkage editor control statements are meaningful in CMS. .Since the CMS interface program cannot examine the input data for the LKED command, all of the control statements are allowed, even though several of them result in the creation of a load module file which cannot be used under CMS. For both command options and control statements, see the publication "OS/VS Linkage Editor and Loader" which leads me to believe that the Linkage editor is a direct port of the OS/VS Linkage Editor. It won't take long to create a help file from the manual. ... Mark S.
_._,_._,_ Dave
|
On Tue, Apr 5, 2022 at 09:44 AM, Dave Wade wrote:
I have uploaded a few more helpfiles for ...
Dave, Do you want/need me to review those? I did find out we don't have online help for LKED (DOSLKED?). ?... Mark S.
|
|
|
Folks, I have uploaded a few more helpfiles for ? SCRIPT RUNPARM SDIFF SED SFBROWSE SNOBOL4 TAPEMAP WAITC ? to the GITHUB repository. I think that completes the HELP for the Y-Disk unless some one knows differently. ? Dave
|
Re: Hercules with VM/370 on Linux in the background - erronous behaviour
Hi, Michael:
You might also be able to solve this by adding:
0</dev/null
to your nohup command. This should eliminate your 'stdin' errors.
- Richard, VE7CVS
toggle quoted message
Show quoted text
On 3/14/22 7:58 AM, Michael Grom 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
|
Re: tool to detect overlapping DCSS or named segments
Mark, I was out of town yesterday, so I am catching up.? I did put a copy of the old SNTPARS EXEC from Cornell U. onto the MAINT 5E5 tools disk. I used it in the old days, and it helped me rearrange the segments for the CMS Nucleus restructure in VM370CE.? On MAINT, Issue VMSETUP?CP, then run it with: SNTPARS DMKSNT?ASSEMBLE F
I added support for the NAME3800 entries. Bob?
|
Re: tool to detect overlapping DCSS or named segments
Thanks Rene, I live on GMT or GMT+1 so can’t always answer when you chaps ask questions Dave ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of René Ferland
Sent: 24 March 2022 01:55
To: [email protected]
Subject: Re: [h390-vm] tool to detect overlapping DCSS or named segments? On Wed, Mar 23, 2022 at 06:43 PM, Mark Waterbury wrote: Where can I find a copy of SNTPARS EXEC?
On minidisk 5E5 (B) of MAINT.
Rene FERLAND, Montreal
|
Re: tool to detect overlapping DCSS or named segments
On Wed, Mar 23, 2022 at 06:43 PM, Mark Waterbury wrote:
Where can I find a copy of SNTPARS EXEC?
On minidisk 5E5 (B) of MAINT. Rene FERLAND, Montreal
|
Re: tool to detect overlapping DCSS or named segments
Hi, Dave,
Thanks for that.? ?Where can I find a copy of SNTPARS EXEC?
Mark
|
Re: tool to detect overlapping DCSS or named segments
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 ?
toggle quoted message
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
|
Jim Snellen
Mark A. Stevens
Bob Flanders
René Ferland