Tom, It might not work for VM/CMS, but have you looked at ? Chris -- <cjar1950@...> ---------------------------------------------------------------------------------------------------------------------------------- On Fri, 22 Jan 2021 14:05:11 -0800 "Tom Chandler" <tchandler48@...> wrote: Trying to write a batch cobol program under cms.? I have read cms guide.? Wrote
what I thought was a simple cobol program using VSAM, and compiled it.
Well, many errors.
Question: does anyone have an example of a batch cobol program
using vsam files that I could look at.? It might make the manual
more understandable.
Cheers
Tom c
|
Trying to write a batch cobol program under cms.? I have read cms guide.? Wrote
what I thought was a simple cobol program using VSAM, and compiled it.
Well, many errors.
Question: does anyone have an example of a batch cobol program
using vsam files that I could look at.? It might make the manual
more understandable.
Cheers
Tom c
|
Re: add new dasd to vm/370 sixpack
Thank you Martin for that clear explanation!
Peter
toggle quoted message
Show quoted text
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Martin Taylor
via groups.io
Sent: Saturday, January 16, 2021 11:07 AM
To: [email protected]
Subject: Re: [h390-vm] add new dasd to vm/370 sixpack
Hello,
I have had the same issue when adding DASD to a VM370 system at the 1.3 level.
Prior to this a simple create of the DASD and adding it to the machine config file
with a suitable device address (that matches the DASD type) was all that was
required. I had added new DASD to a 1.2 system many time with no issue. A
VARY all devices in AUTOLOG1 brought the DASD online. However moving my
system to 1.3 caused all the DASD I had added to become inaccessible with
message DMKLNK108E NOT LINKED NOT MOUNTED being issued when logging
on to an affected user.
The cause of the above problem is that in VM/370 1.3 a fix is implemented that
meant that the SYSUSR parameter, in DMKSYS, had to be used to have the new
DASD accessible. This means that a CP regen is required. As with the 1.2 system
once the new DASD is online it can be used to allocate mini disks space (just do
not use the first cylinder), or any other use.
Below is an explanation of what that fix was and it¡¯s implications.
¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª Start of insert¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª
¡ª¡ª¡ª¡ª¡ª¡ª-
I traced the cause of the DMKLNK108E message down to an flag setting in the
RBLOK field RDEVFLAG. When set to RDEVMOUT its considered not to be
ATTACHED/MOUNTED hence the message.
Further digging showed that adding my DASD to the SYSUSR macro and
regenning CP allowed my userid to logon correctly.
Given the above I did some more searching and found fixes that dealt with these
fields/values. This revealed fix HRC039DK which is not on the 1.2 VM/370 system
but is on the 1.3. This fix is attempted to add clarity and consistency to device
status as explained in HRC039DK MEMO.
So I would say its a pretty safe bet that the behaviour I had seen is not so must
of a bug but a correction to wooly handling of device status in the past. It does
mean that when using VM/370 beta 1.3 the use of the SYSUSR parameter in
DMKSYS is mandated, which I think is the purpose of HRC039DK. Users of the 1.3
beta who just move their directory entries over, as has worked in the past, and
expect the system to run the same as previous versions.
¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ªend of insert ¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª
¡ª¡ª¡ª¡ª¡ª¡ª¡ª
Hope this is of use, at least it documents this behaviour for those moving to 1.3
and above from 1.2 systems.
Regards,
Martin. --
|
Re: add new dasd to vm/370 sixpack
Hello,
I have had the same issue when adding DASD to a VM370 system at the 1.3 level.
Prior to this a simple create of the DASD and adding it to the machine config file with a suitable device address (that matches the DASD type) was all that was required. I had added new DASD to a 1.2 system many time with no issue. A VARY all devices in AUTOLOG1 brought the DASD online. However moving my system to 1.3 caused all the DASD I had added to become inaccessible with message DMKLNK108E NOT LINKED NOT MOUNTED being issued when logging on to an affected user.
The cause of the above problem is that in VM/370 1.3 a fix is implemented that meant that the SYSUSR parameter, in DMKSYS, had to be used to have the new DASD accessible. This means that a CP regen is required. As with the 1.2 system once the new DASD is online it can be used to allocate mini disks space (just do not use the first cylinder), or any other use.
Below is an explanation of what that fix was and it¡¯s implications.
¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª Start of insert¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª-
I traced the cause of the DMKLNK108E message down to an flag setting in the RBLOK field RDEVFLAG. When set to RDEVMOUT its considered not to be ATTACHED/MOUNTED hence the message.
Further digging showed that adding my DASD to the SYSUSR macro and regenning CP allowed my userid to logon correctly.
Given the above I did some more searching and found fixes that dealt with these fields/values. This revealed fix HRC039DK which is not on the 1.2 VM/370 system but is on the 1.3. This fix is attempted to add clarity and consistency to device status as explained in HRC039DK MEMO.
So I would say its a pretty safe bet that the behaviour I had seen is not so must of a bug but a correction to wooly handling of device status in the past. It does mean that when using VM/370 beta 1.3 the use of the SYSUSR parameter in DMKSYS is mandated, which I think is the purpose of HRC039DK. Users of the 1.3 beta who just move their directory entries over, as has worked in the past, and expect the system to run the same as previous versions.
¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ªend of insert ¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª¡ª
Hope this is of use, at least it documents this behaviour for those moving to 1.3 and above from 1.2 systems.
Regards,
Martin.
|
Re: add new dasd to vm/370 sixpack
Hi Peter,
thanks for your help. I have it working now in hercules.rc but will move to AUTOLOG1 as that seems more authentic. Yes, without AUTOCR it is not a good idea to do this in OPERATOR. I did not even know that you could attach dasd dynamically to Hercules but that opens the perspective of adding users with their dasd without even IPLing the system.
best regards,
¸é±ð²Ô¨¦.
toggle quoted message
Show quoted text
On 16 Jan 2021, at 16:43, Peter Coghlan <groups@...> wrote:
Hi Rene,
I was thinking to do the VARY ONLINE nnn and the
ATTACH nnn TO SYSTEM AS VM50-X in the PROFILE EXEC of OPERATOR.
But I noticed that disk 191 of OPERATOR was not formatted, and
even when I did that, IPL CMS falls back to CP very quickly. I
gave OPERATOR some more storage, but that did not do the trick.
I am now looking to do that in hercules.rc but I wonder if OPERATOR
should be able to work with CMS.
I have seen it suggested somewhere to put stuff to be done at startup in the
PROFILE EXEC of OPERATOR but I can't recall where. This is not the correct
thing to do. You should place your ATTACH nnn to SYSTEM as xxxxxx command
in the PROFILE EXEC of AUTOLOG1. You won't need the VARY ONLINE command if
the dasd is available when VM ipls, only when it gets attached after VM ipls.
OPERATOR has difficulties with CMS because it is the primary system operator
and comes up in TERM MODE CP by default. You could change it to TERM MODE VM
and have it ipl CMS but I think you would still need to do the equivalent of
pressing enter on the OPERATOR console in order to get the ipl of CMS to
complete. The best idea is to stay away from OPERATOR for this purpose and
get AUTOLOG1 to do stuff that needs to be done at startup, like it is
supposed to do.
Regards,
Peter Coghlan.
best regards,
|
Re: add new dasd to vm/370 sixpack
Hi Rene,
I was thinking to do the VARY ONLINE nnn and the
ATTACH nnn TO SYSTEM AS VM50-X in the PROFILE EXEC of OPERATOR.
But I noticed that disk 191 of OPERATOR was not formatted, and
even when I did that, IPL CMS falls back to CP very quickly. I
gave OPERATOR some more storage, but that did not do the trick.
I am now looking to do that in hercules.rc but I wonder if OPERATOR
should be able to work with CMS.
I have seen it suggested somewhere to put stuff to be done at startup in the PROFILE EXEC of OPERATOR but I can't recall where. This is not the correct thing to do. You should place your ATTACH nnn to SYSTEM as xxxxxx command in the PROFILE EXEC of AUTOLOG1. You won't need the VARY ONLINE command if the dasd is available when VM ipls, only when it gets attached after VM ipls. OPERATOR has difficulties with CMS because it is the primary system operator and comes up in TERM MODE CP by default. You could change it to TERM MODE VM and have it ipl CMS but I think you would still need to do the equivalent of pressing enter on the OPERATOR console in order to get the ipl of CMS to complete. The best idea is to stay away from OPERATOR for this purpose and get AUTOLOG1 to do stuff that needs to be done at startup, like it is supposed to do. Regards, Peter Coghlan.
best regards,
¸é±ð²Ô¨¦.
On 16 Jan 2021, at 13:58, carlos feldman <carlfelster@...> wrote:
Hi Ren¨¦,
For attaching a DOS disk I use a similar procedure as Dave's
a) format a disk for instance dasdinit -a mydisk.cckd 3350-1 mydisk
b) list in hercules:
07A2 3350 Disks/mydisk.cckd ro sf=Disks/Shadows/mydisk_
c) attach it in operator console:
cp attach 7a2 to CMSUSER as 199
( you'll se a message in CMSUSER console; 199 ATTACHED
d),access it in CMSUSER
ACCESS 199 C.
In my case is a DOS partition, but you may well format as a CMSDISK.
This procedure is repeated each time I logon to CMS.
If you want it as a permanent disk, you have to modify and load, the current direct file to add your disk, for USER CMSUSER:
* userid cuu type adr num volser mode readpw writepw multpw
MDISK 191 3350 001 115 VM50-6 MR ALL WRITE MULT
MDISK 192 3350 116 115 VM50-6 MR ALL WRITE MULT
MDISK 193 3350 231 115 VM50-6 MR ALL WRITE MULT
MDISK 194 3350 346 115 VM50-6 MR ALL WRITE MULT
MDISK 195 3350 461 094 VM50-6 MR ALL WRITE MULT
For me, this was a test, so I preferred the first method
--
Carlos
Argentina
|
Re: add new dasd to vm/370 sixpack
Rene, ? If you add it to the Hercules config you shouldn¡¯t need to vary it on, only attach it to system. You can put this in AUTOLOG1¡¯s profile exec. That runs when the system comes up, Normally on VM/370 R6 you don¡¯t need to attach to system but a user mod was added to so that only volumes marked as SYSOWN in DMKSYS. There is a memo ¡°sysprog memo¡± that says how to rebuild the nucleus with the disk added if you wish to do this. ? Dave ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of rvjansen@...
Sent: 16 January 2021 15:30
To: [email protected]
Subject: Re: [h390-vm] add new dasd to vm/370 sixpack? Hi Carlos, I was thinking to do the VARY ONLINE nnn and the ATTACH nnn TO SYSTEM AS VM50-X in the PROFILE EXEC of OPERATOR. But I noticed that disk 191 of OPERATOR was not formatted, and even when I did that, IPL CMS falls back to CP very quickly. I gave OPERATOR some more storage, but that did not do the trick. I am now looking to do that in hercules.rc but I wonder if OPERATOR should be able to work with CMS. ¸é±ð²Ô¨¦.
? Hi Ren¨¦, For attaching a DOS disk I use a similar procedure as Dave's
a) format a disk for instance?dasdinit -a mydisk.cckd 3350-1 mydisk b) list in hercules: 07A2? ? 3350? ? Disks/mydisk.cckd ro sf=Disks/Shadows/mydisk_ c) attach it in operator console: ? ?cp attach 7a2 to CMSUSER as 199
?( you'll se a message in CMSUSER console; 199 ATTACHED d),access it in CMSUSER ? ? ?ACCESS 199 C. In my case is a DOS partition, but you may well format as a CMSDISK. This procedure is repeated each time I logon to CMS. If you want it as a permanent disk, you have to modify and load, the? current direct file to add your disk, for USER CMSUSER: * userid? ?cuu type adr num volser mode readpw? ?writepw? multpw
? MDISK? ? 191 3350 001 115 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
? MDISK? ? 192 3350 116 115 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
? MDISK? ? 193 3350 231 115 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
? MDISK? ? 194 3350 346 115 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
? MDISK? ? 195 3350 461 094 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT?? For me, this was a test, so I preferred the first method --
Carlos Argentina
?
|
Re: add new dasd to vm/370 sixpack
Hi Carlos,
thank you.
I was thinking to do the VARY ONLINE nnn and the ATTACH nnn TO SYSTEM AS VM50-X in the PROFILE EXEC of OPERATOR. But I noticed that disk 191 of OPERATOR was not formatted, and even when I did that, IPL CMS falls back to CP very quickly. I gave OPERATOR some more storage, but that did not do the trick. I am now looking to do that in hercules.rc but I wonder if OPERATOR should be able to work with CMS.
best regards,
toggle quoted message
Show quoted text
Hi Ren¨¦, ?
For attaching a DOS disk I use a similar procedure as Dave's
a) format a disk for instance?dasdinit -a mydisk.cckd 3350-1 mydisk b) list in hercules: 07A2? ? 3350? ? Disks/mydisk.cckd ro sf=Disks/Shadows/mydisk_ c) attach it in operator console: ? ?cp attach 7a2 to CMSUSER as 199
?( you'll se a message in CMSUSER console; 199 ATTACHED d),access it in CMSUSER ? ? ?ACCESS 199 C. ?
In my case is a DOS partition, but you may well format as a CMSDISK. ?
This procedure is repeated each time I logon to CMS. ?
If you want it as a permanent disk, you have to modify and load, the? current direct file to add your disk, for USER CMSUSER: * userid? ?cuu type adr num volser mode readpw? ?writepw? multpw
? MDISK? ? 191 3350 001 115 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
? MDISK? ? 192 3350 116 115 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
? MDISK? ? 193 3350 231 115 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
? MDISK? ? 194 3350 346 115 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
? MDISK? ? 195 3350 461 094 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
?
For me, this was a test, so I preferred the first method --
Carlos Argentina
|
Re: add new dasd to vm/370 sixpack
Hi Ren¨¦,
?
For attaching a DOS disk I use a similar procedure as Dave's
a) format a disk for instance?dasdinit -a mydisk.cckd 3350-1 mydisk
b) list in hercules:
07A2? ? 3350? ? Disks/mydisk.cckd ro sf=Disks/Shadows/mydisk_
c) attach it in operator console:
? ?cp attach 7a2 to CMSUSER as 199
?( you'll se a message in CMSUSER console; 199 ATTACHED
d),access it in CMSUSER
? ? ?ACCESS 199 C.
?
In my case is a DOS partition, but you may well format as a CMSDISK.
?
This procedure is repeated each time I logon to CMS.
?
If you want it as a permanent disk, you have to modify and load, the? current direct file to add your disk, for USER CMSUSER:
* userid? ?cuu type adr num volser mode readpw? ?writepw? multpw
? MDISK? ? 191 3350 001 115 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
? MDISK? ? 192 3350 116 115 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
? MDISK? ? 193 3350 231 115 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
? MDISK? ? 194 3350 346 115 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
? MDISK? ? 195 3350 461 094 VM50-6 MR? ?ALL? ? ? WRITE? ? MULT??
?
For me, this was a test, so I preferred the first method
--
Carlos
Argentina
|
Re: add new dasd to vm/370 sixpack
Hi Dave,
yep that works. Great!
thanks very much,
best regards,
toggle quoted message
Show quoted text
-----Original Message-----
From:?[email protected]?<[email protected]> On Behalf Of
rvjansen@...
Sent: 15 January 2021 21:45
To:?[email protected]
Subject: [h390-vm] add new dasd to vm/370 sixpack
I cannot find anything on the net.
What I want to do: add a dasd for a new user (bRexx tester) to a sixpack
instance (I want a new dasd because I will take that dasd for the user to new
systems with new levels of bREXX on it). I also can take a new instance online
and just reuse CMSUSER¡¯s disks, like I did for my own userid, but I thought
that this should be doable and should be documented. I will do the
documenting if someone can help me.
What I did:
(I chose 6A0 because that seemed to be defined as a 3350)
dasdinit -a vm3350-7.6a0.cckd 3350-1 VM50-7
Added that to sixpack.conf at A06, Hercules (4.00) starts without complaining.
Added a clone of CMSUSER to the directory, but with VM50-7 instead of
VM50-6. Ran direct sixpack, worked like a charm. User can logon.
with maint, VARY ONLINE 6A0
ATTACH 6A0 TO SYSTEM
it then complains VOLID MISSING OR INVALID
You need to specify the volume ID here"CP ATTACH 6A6 TO SYSTEM AS VM50-7"I cannot find IBCDASDI to put a label on it, but I thought dasdinit did do that
It doesI cannot find SYSTEM CONFIG so I assume this level did not have that yet
Yes it needs to be assembled into DMKSYS and the nucleus re-builtDave
|
Re: add new dasd to vm/370 sixpack
toggle quoted message
Show quoted text
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of
rvjansen@...
Sent: 15 January 2021 21:45
To: [email protected]
Subject: [h390-vm] add new dasd to vm/370 sixpack
I cannot find anything on the net.
What I want to do: add a dasd for a new user (bRexx tester) to a sixpack
instance (I want a new dasd because I will take that dasd for the user to new
systems with new levels of bREXX on it). I also can take a new instance online
and just reuse CMSUSER¡¯s disks, like I did for my own userid, but I thought
that this should be doable and should be documented. I will do the
documenting if someone can help me.
What I did:
(I chose 6A0 because that seemed to be defined as a 3350)
dasdinit -a vm3350-7.6a0.cckd 3350-1 VM50-7
Added that to sixpack.conf at A06, Hercules (4.00) starts without complaining.
Added a clone of CMSUSER to the directory, but with VM50-7 instead of
VM50-6. Ran direct sixpack, worked like a charm. User can logon.
with maint, VARY ONLINE 6A0
ATTACH 6A0 TO SYSTEM
it then complains VOLID MISSING OR INVALID
You need to specify the volume ID here "CP ATTACH 6A6 TO SYSTEM AS VM50-7" I cannot find IBCDASDI to put a label on it, but I thought dasdinit did do that
It does I cannot find SYSTEM CONFIG so I assume this level did not have that yet
Yes it needs to be assembled into DMKSYS and the nucleus re-built Dave
|
add new dasd to vm/370 sixpack
I cannot find anything on the net.
What I want to do: add a dasd for a new user (bRexx tester) to a sixpack instance (I want a new dasd because I will take that dasd for the user to new systems with new levels of bREXX on it). I also can take a new instance online and just reuse CMSUSER¡¯s disks, like I did for my own userid, but I thought that this should be doable and should be documented. I will do the documenting if someone can help me.
What I did:
(I chose 6A0 because that seemed to be defined as a 3350)
dasdinit -a vm3350-7.6a0.cckd 3350-1 VM50-7
Added that to sixpack.conf at A06, Hercules (4.00) starts without complaining.
Added a clone of CMSUSER to the directory, but with VM50-7 instead of VM50-6. Ran direct sixpack, worked like a charm. User can logon.
with maint, VARY ONLINE 6A0
ATTACH 6A0 TO SYSTEM
it then complains VOLID MISSING OR INVALID
I cannot find IBCDASDI to put a label on it, but I thought dasdinit did do that
I cannot find SYSTEM CONFIG so I assume this level did not have that yet
I do see a different number of tracks on the new DASD (16800 instead of 16650) but do not know if that is relevant.
User can logon but IPL CMS complains:
DMKLNK108E N5619850 191 NOT LINKED; VOLID VM50-7 NOT MOUNTED
DMKLNK108E N5619850 192 NOT LINKED; VOLID VM50-7 NOT MOUNTED
DMKLNK108E N5619850 193 NOT LINKED; VOLID VM50-7 NOT MOUNTED
DMKLNK108E N5619850 194 NOT LINKED; VOLID VM50-7 NOT MOUNTED
DMKLNK108E N5619850 195 NOT LINKED; VOLID VM50-7 NOT MOUNTED
LOGON AT 21:37:00 GMT FRIDAY 01/15/21
CMS VERSION 6.0 DOCKER 1.4.30
Y (19E) R/O
DMSACC113S 'A (191) ' NOT ATTACHED
Ready; T=0.01/0.01 21:37:14
best regards and many thanks in advance,
¸é±ð²Ô¨¦.
|
Thank you Tom, I appreciate it very much. We are a bit short-handed at the museum but we'll try to get to this soon.
-Dave
toggle quoted message
Show quoted text
On 1/14/21 4:54 PM, Tom Chandler wrote: Have any questions, just send them.? I will glad to help.
Cheers
Tom c
On Thu, Jan 14, 2021 at 3:39 PM Dave McGuire <mcguire@... <mailto:mcguire@...>> wrote:
? ?Ok, thanks Tom.? It's likely that we will give them a try over at
LSSM at some point soon.
? ? ? ? ? ? ?-Dave
On 1/14/21 4:34 PM, Tom Chandler wrote:
> I do not have access to vm/esa.? However, both are? basic gcc c
programs
> so I would think
> that they should without too much trouble.
>
> If so please let me know.
>
> Cheers
> Tom c
>
>
> On Thu, Jan 14, 2021 at 3:30 PM Dave McGuire
<mcguire@... <mailto:mcguire@...>
> <mailto:mcguire@... <mailto:mcguire@...>>> wrote:
>
>? ? ?On 1/14/21 9:39 AM, Tom Chandler wrote:
>? ? ? > There are two new applications available on Github for
VM370 cms:
>? ? ? >
>? ? ? > CMSBASIC - This is a port of bxbasic from linux, to run under
>? ? ?VM370.? I
>? ? ? > can found at:
>? ? ? > github.com/tchandler48/cmsbasic
<>
>? ? ?<>
>? ? ? >
>? ? ? > CMSPILOT - A port of the PILOT language from LInux to run
via VM370
>? ? ? > cms.? It is at
>? ? ? > github.com/tchandler48/cmspilot
<>
>? ? ?<>
>? ? ? >
>? ? ? > I have tested both, but sure there are some hidden issues.
>? ? ? > Questions/comments
>? ? ? > are welcome.
>
>? ? ? ? ?Nice!? Do you think either or both of these will run
under later
>? ? ?CMS
>? ? ?releases, such as that of VM/ESA?
>
>? ? ? ? ? ? ? ? ? -Dave
>
>? ? ?--
>? ? ?Dave McGuire, AK4HZ
>? ? ?New Kensington, PA
>
>
>
>
>
>
--
Dave McGuire, AK4HZ
New Kensington, PA
--
Dave McGuire, AK4HZ
New Kensington, PA
|
Have any questions, just send them.? I will glad to help.
Cheers Tom c
On Thu, Jan 14, 2021 at 3:39 PM Dave McGuire < mcguire@...> wrote:
? ?Ok, thanks Tom.? It's likely that we will give them a try over at
LSSM at some point soon.
? ? ? ? ? ? ?-Dave
On 1/14/21 4:34 PM, Tom Chandler wrote:
> I do not have access to vm/esa.? However, both are? basic gcc c programs
> so I would think
> that they should without too much trouble.
>
> If so please let me know.
>
> Cheers
> Tom c
>
>
> On Thu, Jan 14, 2021 at 3:30 PM Dave McGuire <mcguire@...
> <mailto:mcguire@...>> wrote:
>
>? ? ?On 1/14/21 9:39 AM, Tom Chandler wrote:
>? ? ? > There are two new applications available on Github for VM370 cms:
>? ? ? >
>? ? ? > CMSBASIC - This is a port of bxbasic from linux, to run under
>? ? ?VM370.? I
>? ? ? > can found at:
>? ? ? >
>? ? ?<>
>? ? ? >
>? ? ? > CMSPILOT - A port of the PILOT language from LInux to run via VM370
>? ? ? > cms.? It is at
>? ? ? >
>? ? ?<>
>? ? ? >
>? ? ? > I have tested both, but sure there are some hidden issues.
>? ? ? > Questions/comments
>? ? ? > are welcome.
>
>? ? ? ? ?Nice!? Do you think either or both of these will run under later
>? ? ?CMS
>? ? ?releases, such as that of VM/ESA?
>
>? ? ? ? ? ? ? ? ? -Dave
>
>? ? ?--
>? ? ?Dave McGuire, AK4HZ
>? ? ?New Kensington, PA
>
>
>
>
>
>
--
Dave McGuire, AK4HZ
New Kensington, PA
|
Ok, thanks Tom. It's likely that we will give them a try over at LSSM at some point soon.
-Dave
toggle quoted message
Show quoted text
On 1/14/21 4:34 PM, Tom Chandler wrote: I do not have access to vm/esa.? However, both are? basic gcc c programs so I would think
that they should without too much trouble.
If so please let me know.
Cheers
Tom c
On Thu, Jan 14, 2021 at 3:30 PM Dave McGuire <mcguire@... <mailto:mcguire@...>> wrote:
On 1/14/21 9:39 AM, Tom Chandler wrote:
> There are two new applications available on Github for VM370 cms:
>
> CMSBASIC - This is a port of bxbasic from linux, to run under
VM370.? I
> can found at:
> github.com/tchandler48/cmsbasic
<>
>
> CMSPILOT - A port of the PILOT language from LInux to run via VM370
> cms.? It is at
> github.com/tchandler48/cmspilot
<>
>
> I have tested both, but sure there are some hidden issues.
> Questions/comments
> are welcome.
? ?Nice!? Do you think either or both of these will run under later
CMS
releases, such as that of VM/ESA?
? ? ? ? ? ? -Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
--
Dave McGuire, AK4HZ
New Kensington, PA
|
I do not have access to vm/esa.? However, both are? basic gcc c programs so I would think that they should without too much trouble.
If so please let me know.
Cheers Tom c
On Thu, Jan 14, 2021 at 3:30 PM Dave McGuire < mcguire@...> wrote: On 1/14/21 9:39 AM, Tom Chandler wrote:
> There are two new applications available on Github for VM370 cms:
>
> CMSBASIC - This is a port of bxbasic from linux, to run under VM370.? I
> can found at:
>? ?????
>
> CMSPILOT - A port of the PILOT language from LInux to run via VM370
> cms.? It is at
>? ????
>
> I have tested both, but sure there are some hidden issues.?
> Questions/comments
> are welcome.
? ?Nice!? Do you think either or both of these will run under later CMS
releases, such as that of VM/ESA?
? ? ? ? ? ? -Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
|
On 1/14/21 9:39 AM, Tom Chandler wrote: There are two new applications available on Github for VM370 cms:
CMSBASIC - This is a port of bxbasic from linux, to run under VM370.? I can found at:
????? github.com/tchandler48/cmsbasic
CMSPILOT - A port of the PILOT language from LInux to run via VM370 cms.? It is at
???? github.com/tchandler48/cmspilot
I have tested both, but sure there are some hidden issues. Questions/comments
are welcome. Nice! Do you think either or both of these will run under later CMS releases, such as that of VM/ESA? -Dave -- Dave McGuire, AK4HZ New Kensington, PA
|
Awesome - will give them a spin!
Adrian
|
There are two new applications available on Github for VM370 cms:
CMSBASIC - This is a port of bxbasic from linux, to run under VM370.? I can found at:
????? github.com/tchandler48/cmsbasic
CMSPILOT - A port of the PILOT language from LInux to run via VM370 cms.? It is at
???? github.com/tchandler48/cmspilot
I have tested both, but sure there are some hidden issues.? Questions/comments
are welcome.
Cheers
Tom c.
|
Mark,
That functionality does not ?exist in VM/370s filesystem. Remember, it is NOT the shared filesystem, but rather the predecessor ?(800-byte block, IIRC) CMS filesystem.
Joe
Adrian,
I am not trying to pick on you ...
See:
??
and page down to the section on OPENTYP= where it says:
- OPENTYP=
- is the type of open to be performed on the file. Acceptable values are:
- READ
- indicates that the file exists and will only be read.
- WRITE
- indicates that the file may be written to or read from. All changed and added records are written. Other records remain unchanged. If the file does not exist, it is created.
- NEW
- indicates that the file does not exist and is then created. It may then be written to or read from. If the file already exists, it is an error and the file is not opened.
- REPLACE
- indicates that the file is replaced with only the subsequently written records. If the file does not exist, it is created.
- NONE
- indicates that the file is not actually opened. The file is implicitly opened when the first FSREAD, FSWRITE, or FSPOINT is issued to the file. Use of FSOPEN with OPENTYP=NONE is essentially equivalent to an FSSTATE, and differs from an FSSTATE in that it may be used to create an FSCB for the file. The CACHE parameter is ignored if OPENTYPE=NONE.
You can specify OPENTYP=WRITE or OPENTYP=NONE.? Then just issue FSREADs mixed with FSWRITEs.
Hope that helps,
Mark
|
carlos feldman
Dave McGuire