Re: Purging Class Z Printouts
At a guess, they’re in MVS’s reader. Try Q RDR MVS ALL On Jan 3, 2024, at 12:50 PM, Frank D. Engel, Jr. <fde101@...> wrote:
?When I perform a "q prt" command as MAINT or from the operator console I can see a number of spooled print files/jobs that came from MVS running under VM; for examples:
OWNERID FILE CLASS RECDS CPY HOLD
MVS 0100 Z PRT 000053 01 NONE
MVS 0104 Z PRT 000037 01 NONE
MVS 0105 Z PRT 000033 01 NONE
I don't believe I need those so I am trying to purge them, but none of the syntax I am trying seems to work:
pur prt
NO FILES PURGED
Ready; T=0.01/0.01 12:46:38
pur prt 100
NO FILES PURGED
SPOOLID 0100 DOES NOT EXIST
Ready(00042); T=0.01/0.01 12:46:42
pur prt class z
NO FILES PURGED
Ready; T=0.01/0.01 12:46:47
pur prt class z 100
NO FILES PURGED
SPOOLID 0100 DOES NOT EXIST
Ready(00042); T=0.01/0.01 12:47:18
pur prt class all
NO FILES PURGED
CLASS MISSING OR INVALID
Ready(00028); T=0.01/0.01 12:47:28
pur all
NO FILES PURGED
Ready; T=0.01/0.01 12:47:32
pur prt class z all
NO FILES PURGED
I am hopefully missing something simple here - can anyone clue me in?
Thank you!
|
Purging Class Z Printouts
When I perform a "q prt" command as MAINT or from the operator console I can see a number of spooled print files/jobs that came from MVS running under VM; for examples:
OWNERID? FILE CLASS RECDS? CPY HOLD
MVS????? 0100 Z PRT 000053? 01 NONE
MVS????? 0104 Z PRT 000037? 01 NONE
MVS????? 0105 Z PRT 000033? 01 NONE
I don't believe I need those so I am trying to purge them, but none of the syntax I am trying seems to work:
pur prt
?NO? FILES PURGED
Ready; T=0.01/0.01 12:46:38
pur prt 100
?NO? FILES PURGED
SPOOLID 0100 DOES NOT EXIST
Ready(00042); T=0.01/0.01 12:46:42
pur prt class z
?NO? FILES PURGED
Ready; T=0.01/0.01 12:46:47
pur prt class z 100
?NO? FILES PURGED
SPOOLID 0100 DOES NOT EXIST
Ready(00042); T=0.01/0.01 12:47:18
pur prt class all
?NO? FILES PURGED
CLASS MISSING OR INVALID
Ready(00028); T=0.01/0.01 12:47:28
pur all
?NO? FILES PURGED
Ready; T=0.01/0.01 12:47:32
pur prt class z all
?NO? FILES PURGED
I am hopefully missing something simple here - can anyone clue me in?
Thank you!
|
Thanks! I just tested it, and it certainly works (as this maclib layout is recognized by the assembler) but it seems rather incomplete compared to what I had.
In all my enthousiasm I sent out a couple of personal mails and also, but different info, to the list, I have now corrected this by opening an issue at??to avoid duplication of effort. This contains a list of what is missing when compared to the verification procedure of the version I used on modern VM for years.
Also, my 'modern' seems to be the status quo on Z arch around 2015. It might even be that we can add more instruction macro's.?
best regards,
toggle quoted message
Show quoted text
The following files and folders have been uploaded to the Files area of the [email protected] group.
By: Dave Wade <dave.g4ugm@...> Description:
A VMARC format file with the MACLIB and MACROS from
https://www.jaymoseley.com/hercules/compiling/spopcodes.htm.
Use ind$file with RECFM F LRECL 80 to transfer the file to CMS.
To extract the MACLIB type
vmarc unpack opcodes vmarc a opcodes maclib a
to extract the individual MACRO files do
vmarc unpack opcodes vmarc a * macro a
to use the MACROS add OPCODES to your GLOBAL MACLIB.
|
The following files and folders have been uploaded to the Files area of the [email protected] group.
By: Dave Wade <dave.g4ugm@...>
Description:
A VMARC format file with the MACLIB and MACROS from
https://www.jaymoseley.com/hercules/compiling/spopcodes.htm.
Use ind$file with RECFM F LRECL 80 to transfer the file to CMS.
To extract the MACLIB type
vmarc unpack opcodes vmarc a opcodes maclib a
to extract the individual MACRO files do
vmarc unpack opcodes vmarc a * macro a
to use the MACROS add OPCODES to your GLOBAL MACLIB.
|
The following files and folders have been uploaded to the Files area of the [email protected] group.
By: Dave Wade <dave.g4ugm@...>
Description:
A tape in CMSTAPE format of a MACLIB and MACROS from
https://www.jaymoseley.com/hercules/compiling/spopcodes.htm.
to load the MACLIB type
TAPE LOAD
To use add "OPCODES" to your GLOBAL MACLIB file.
If you need the source MACROS issue a second TAPE LOAD.
|
Re: ERROR LOADING 'DMSROS TEXT'
On Tue, Jan 2, 2024 at 05:43 AM, Bob Polmanter wrote:
CP ATTACH 241 RENE R/O
Thanks! I didn't know that one. :-) Cheers, Rene FERLAND, Montreal
|
Re: ERROR LOADING 'DMSROS TEXT'
Hi Rene,
It looks like a bug issue to me.? It should not be doing this.
By the way, when bringing an OS disk online to VM, I'd recommend you make it read only.? You can do this two ways. One is to attach it as read only.? Or access it as read only.
CP ATTACH 241 RENE R/O
or
ACC 241 C/C
The attach is probably safer, so one does not forget to do the filemode/filemode on the ACCESS command each time it is used.
Regards,
Bob
|
ERROR LOADING 'DMSROS TEXT'
Hello all,
?
Following Doug message concerning the? transfer of files from MVS, I noticed something strange. I have this 3350 MVS disk on virtual address 241 and a temporary minidisk of 5 cylinders on 291. If I release the standard 191 minidisk to access 291 on A, and then try to access my MVS disk on file mode C, I get an error message regarding virtual storage:
?
Ready; T=0.01/0.01 00:19:47
rel a
Ready; T=0.01/0.01 00:19:49
acc 291 a
Ready; T=0.01/0.01 00:19:51
acc 241 c
DMSLIO109S VIRTUAL STORAGE CAPACITY EXCEEDED.
ERROR LOADING 'DMSROS TEXT'.
Ready(00104); T=0.01/0.01 00:19:56
q storage
STORAGE = 08192K
Ready; T=0.01/0.01 00:20:21
?
However, if I release my temporary minidisk 291 to access 191 on file mode A again, then no problem to access the MVS disk:
?
Ready; T=0.01/0.01 00:22:07
rel a
Ready; T=0.01/0.01 00:22:11
acc 191 a
Ready; T=0.01/0.01 00:22:15
acc 241 c
C (241) R/W - OS
Ready; T=0.01/0.01 00:22:30
?
How come the temporary minidisk has this effect on DMSROS?
?
I also noticed that I can work around this "problem" by accessing the MVS disk BEFORE doing so for the temporary minidisk. Yet, is this normal behaviour? Just wondering...
?
Cheers,
?
Rene FERLAND, Montreal
?
|
Re: Easiest way to move MVS PDS to CMS?
Bernd,
Yes, that will work.? You do not have to use MOVEFILE.? You can write your own program to read the records from the FILEDEF dataset.? If you do, you must use OS-style macros (e.g., GET/PUT or READ/WRITE) so as to use the OS simulation support built into CMS.? Compiled PASCAL will be using OS macros so you should be good to go.
This is not just limited to PDS datasets either.? You can read in sequential files too, with F, V or U records; just leave off the MEMBER option on the filedef.
Regards,
Bob
|
Re: Easiest way to move MVS PDS to CMS?
Doug,
I got you the first time.? I know your MVS is not under VM.? Just bring that dasd online to VM anyway regardless of where MVS is and follow the procedure.?? MVS of course should not be active while you are trying to access this dasd via VM.
Regards,
Bob
|
Re: Easiest way to move MVS PDS to CMS?
I did not know about this feature so far, that is:
CMS FILEDEF being able to access members of a MVS PDS which is on
a 3350 formatted by MVS,
be it a MVS guest of VM/370 or a copy of another MVS volume
(coming from another MVS system,
which is not part of the current VM/370 system).
My question now is:
is MOVEFILE really needed?
if my compiler (for example the New Stanford Pascal compiler -
)
is able to process FB 80 input files, shouldn't it be possible to
use the MVS member directly as input?
The compiler is itself a Pascal program and uses OS macros to
access the input files, after all (all files, BTW).
The Pascal compiler IS an OS compiler; there are almost no
differences between the OS and the VM version of the compiler.
That is (for example):?
FILEDEF? INPUT? DISK TESTPROG PASCAL J DSN MY SOURCE LIB (MEMBER
TESTPROG BLKSIZE 3120 LRECL 80 RECFM FB
EXEC PASCAL
What do you think?
I'm not able to test it at the moment, because in my
installation, VM/370 and MVS 3.8 live in different
Hercules instances. Well, I could, if I would add a volume of the
MVS Hercules machine to the VM machine
(with some Pascal sources on it).
Thank you,
kind regards
Bernd
Am 01.01.2024 um 00:59 schrieb Doug
Wegscheid:
toggle quoted message
Show quoted text
"The MVS is NOT running
under VM", but I can move a copy of the 3350 over to VM and
do it.
On Sunday, December 31, 2023 at 06:51:35 PM EST, Bob
Polmanter <wably@...> wrote:
Doug,
Probably the easiest way is to make the dasd volume
where your source dataset resides online to VM/370.?
Assign a real device address for the volume to be one
recognized already by CP for that device type.? The
MVS dasd addresses are usually already defined to VM
in most of the Sixpack and VM/CE distributions, so
you? can likely use the same device address that was
used in MVS itself for that particular volume.
After you bring up VM with the dasd in question,
attach that dasd to your userid.? To make the
explanation simpler, lets make some assumptions:
dasd volume = 14C? 3350? VOL=SER=MYPACK
Dataset you want:?? MY.SOURCE.LIB(COBOL5)?
attributes:? 3120/80/FB
So assuming you brought the dasd online to VM at
address 14C, then:
cp attach 14c to userid
ACC 14C J
FILEDEF? IN? DISK X X J DSN MY SOURCE LIB (MEMBER
COBOL5 BLKSIZE 3120 LRECL 80 RECFM FB
FILEDEF OUT COBOL5 COBOL A
MOVE IN OUT
Thats it.? The file should be on your A-disk.? Rinse
and repeat for any other members by respecifying the
FILEDEF IN again with a different member name, then
MOVE IN OUT, as many times as needed.? This can be put
into an EXEC also, of course.
Notes:? You need to know the dataset attributes and
put them on the filedef command.? CMS will not?
attributes from the VTOC on the volume.? There are no
'dots' (qualifier separators) in the DSNAME in the
filedef command.? Separate the qualifiers with a
blank.? Use a dummy filename and filetype on the IN
filedef; you must use the filemode letter of the drive
you accessed though.
Regards,
Bob
|
Re: Easiest way to move MVS PDS to CMS?
"The MVS is NOT running under VM", but I can move a copy of the 3350 over to VM and do it.
On Sunday, December 31, 2023 at 06:51:35 PM EST, Bob Polmanter <wably@...> wrote:
Doug,
Probably the easiest way is to make the dasd volume where your source dataset resides online to VM/370.? Assign a real device address for the volume to be one recognized already by CP for that device type.? The MVS dasd addresses are usually already defined to VM in most of the Sixpack and VM/CE distributions, so you? can likely use the same device address that was used in MVS itself for that particular volume.
After you bring up VM with the dasd in question, attach that dasd to your userid.? To make the explanation simpler, lets make some assumptions:
dasd volume = 14C? 3350? VOL=SER=MYPACK
Dataset you want:?? MY.SOURCE.LIB(COBOL5)? attributes:? 3120/80/FB
So assuming you brought the dasd online to VM at address 14C, then:
cp attach 14c to userid
ACC 14C J
FILEDEF? IN? DISK X X J DSN MY SOURCE LIB (MEMBER COBOL5 BLKSIZE 3120 LRECL 80 RECFM FB
FILEDEF OUT COBOL5 COBOL A
MOVE IN OUT
Thats it.? The file should be on your A-disk.? Rinse and repeat for any other members by respecifying the FILEDEF IN again with a different member name, then MOVE IN OUT, as many times as needed.? This can be put into an EXEC also, of course.
Notes:? You need to know the dataset attributes and put them on the filedef command.? CMS will not? attributes from the VTOC on the volume.? There are no 'dots' (qualifier separators) in the DSNAME in the filedef command.? Separate the qualifiers with a blank.? Use a dummy filename and filetype on the IN filedef; you must use the filemode letter of the drive you accessed though.
Regards,
Bob
|
Re: Easiest way to move MVS PDS to CMS?
Doug,
Probably the easiest way is to make the dasd volume where your source dataset resides online to VM/370.? Assign a real device address for the volume to be one recognized already by CP for that device type.? The MVS dasd addresses are usually already defined to VM in most of the Sixpack and VM/CE distributions, so you? can likely use the same device address that was used in MVS itself for that particular volume.
After you bring up VM with the dasd in question, attach that dasd to your userid.? To make the explanation simpler, lets make some assumptions:
dasd volume = 14C? 3350? VOL=SER=MYPACK
Dataset you want:?? MY.SOURCE.LIB(COBOL5)? attributes:? 3120/80/FB
So assuming you brought the dasd online to VM at address 14C, then:
cp attach 14c to userid
ACC 14C J
FILEDEF? IN? DISK X X J DSN MY SOURCE LIB (MEMBER COBOL5 BLKSIZE 3120 LRECL 80 RECFM FB
FILEDEF OUT COBOL5 COBOL A
MOVE IN OUT
Thats it.? The file should be on your A-disk.? Rinse and repeat for any other members by respecifying the FILEDEF IN again with a different member name, then MOVE IN OUT, as many times as needed.? This can be put into an EXEC also, of course.
Notes:? You need to know the dataset attributes and put them on the filedef command.? CMS will not? attributes from the VTOC on the volume.? There are no 'dots' (qualifier separators) in the DSNAME in the filedef command.? Separate the qualifiers with a blank.? Use a dummy filename and filetype on the IN filedef; you must use the filemode letter of the drive you accessed though.
Regards,
Bob
|
Re: Easiest way to move MVS PDS to CMS?
On Sun, Dec 31, 2023 at 02:54 PM, Doug Wegscheid wrote:
What is the easiest way to move the members of a source code only from MVS to CMS?
The MOVEFILE command. Check GC20-1818-0 "CMS Command and Macro Reference", page 139, for an example of what you want to do. Cheers, Rene FERLAND, Montreal
|
Easiest way to move MVS PDS to CMS?
I have an existing assembler program that I built on MVS 3.8J, and I want to get it working on CMS.
What is the easiest way to move the members of a source code only from MVS to CMS? (The MVS is NOT running under VM, so there will be some punching or IND$FILE along the way).
|
Re: DOS/VS under VM/370 Job Submission from CMS
Good info - I figured there had to be something like CP READY 00C
and was starting to dig through the help to try to find it, so
this cut short that search a bit.
The CP SP RDR CONT option looks promising as well.
Thank you!
toggle quoted message
Show quoted text
To fix the problem that only one job is executed when you quickly
submit more than one job: code
? ?CP SP RDR CONT
in the startup of the DOS guest.
If a job sits waiting in the VM rdr queue of DOS, issue a CP READY
00C in the DOS machine
(I hope my rusty memory has this all right)
--
Kris Buelens
|
Re: DOS/VS under VM/370 Job Submission from CMS
To fix the problem that only one job is executed when you quickly submit more than one job: code
? ?CP SP RDR CONT
in the startup of the DOS guest.
If a job sits waiting in the VM rdr queue of DOS, issue a CP READY 00C in the DOS machine
(I hope my rusty memory has this all right)
--
Kris Buelens
|
Re: DOS/VS under VM/370 Job Submission from CMS
Looks like this crossed over with my other reply.?
POWER/VS is running in F1.
I removed the PAUSE - I had only added it because the LISTIO was
failing and I wanted to see if something else would work (that was
an easy thing to try).? No longer needed now that the issue with
LISTIO was worked out.
I shut down DOS/VS again and when I logged in as dosvs, I did a q
rdr and indeed the last deck was left in the reader.
I purged that before doing another IPL.
Now it is working as expected, without the alternating behavior.
I suspect that when a deck was loaded onto the reader DOS/VS was
reading one deck then stopping until informed that another was
available, but the fact that a deck was on the reader then the
DOSIPL EXEC submitted another left it with two decks but it only
expected (and thus only read) one, leaving the other behind?
In any case, this seems to be working now.
Thank you!
On 12/26/23 07:53, René Ferland wrote:
toggle quoted message
Show quoted text
On Tue, Dec 26, 2023 at 03:29 AM, Frank D. Engel, Jr. wrote:
The // LISTIO statement in my LISTIO JCL also gets flagged as
invalid (though it is documented as valid in one of the IBM
books I found), but that one doesn't seem to be a VM issue...
Yes, LISTIO needs an argument, that's why it fails here.
?
I am not sure what is going on with this "alternating"
behavior. I never met it and it seems difficult to reproduce
without further information. One thing you don't say is whether
you use POWER or not. For sure your jobs don't have the JECL for
POWER. At this point, I would say: shutdown DOS/VS, clean the
card reader of DOSVS of any spool files, IPL DOS/VS again
including POWER, then delete any unecessary jobs of the Reader
queue of POWER. After all that, you can SUBMIT a job like this
from CMSUSER:
?
* $$ JOB JNM=LSTIO, CLASS=0,DISP=D
* $$ LST CLASS=A,DISP=D,JSEP=0
// JOB LISTIO?
// LISTIO SYS
/&
* $$ EOJ
I rarely use PAUSE in a job because it will force you to
interact with the console for the job to continue (or finish in
your case). The main usage I had of PAUSE is to interrupt a job
so I can mount a tape needed by the job.
Cheers,
?
Rene FERLAND, Montreal
?
|
Re: DOS/VS under VM/370 Job Submission from CMS
On Tue, Dec 26, 2023 at 04:52 AM, Frank D. Engel, Jr. wrote:
* nothing jcl actually processes (the one submitted by the DOSIPL EXEC???)
Yes, the one from DOSIPL EXEC, so no need to submit it again from CMSUSER. This job is there to ready the card reader task automatically at IPL. You have nicely customized DOSIPL EXEC to your needs, that's great. :-) Cheers, Rene FERLAND, Montreal P.S. -- At this point, I think any further questions about DOS/VS should be sent to H390-DOSVS.
|
Re: DOS/VS under VM/370 Job Submission from CMS
On Tue, Dec 26, 2023 at 03:29 AM, Frank D. Engel, Jr. wrote:
The // LISTIO statement in my LISTIO JCL also gets flagged as invalid (though it is documented as valid in one of the IBM books I found), but that one doesn't seem to be a VM issue...
Yes, LISTIO needs an argument, that's why it fails here.
?
I am not sure what is going on with this "alternating" behavior. I never met it and it seems difficult to reproduce without further information. One thing you don't say is whether you use POWER or not. For sure your jobs don't have the JECL for POWER. At this point, I would say: shutdown DOS/VS, clean the card reader of DOSVS of any spool files, IPL DOS/VS again including POWER, then delete any unecessary jobs of the Reader queue of POWER. After all that, you can SUBMIT a job like this from CMSUSER:
?
* $$ JOB JNM=LSTIO, CLASS=0,DISP=D
* $$ LST CLASS=A,DISP=D,JSEP=0
// JOB LISTIO?
// LISTIO SYS
/&
* $$ EOJ
I rarely use PAUSE in a job because it will force you to interact with the console for the job to continue (or finish in your case). The main usage I had of PAUSE is to interrupt a job so I can mount a tape needed by the job.
Cheers,
?
Rene FERLAND, Montreal
?
|
René Ferland