|
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
|
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.
|
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
|
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
|
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.
|
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.
|
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.
|
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.
|
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 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,
I agree that the LKED?command can produce members in a LOADLIB. In VM/370, the use of such a library is as input to the GEN3705 CMS command. It is possible that some other special purpose program could be built? that could load from the LOADLIB, but CMS in VM/370 has no code that would support a GLOBAL LOADLIB command or any code to support use of LOAD files by LINK, LOAD, or ATTACH OS simulation interfaces within a CMS program.?
When I move the ASSIST code into the VM370CE release track, I will have a version I can try to understand how the ASSIST LOADLIB could possibly be used. I'm just swamped currently with other tasks.
/Bob?
|
Mark A. Stevens