开云体育

What say printout on virtual printer, which vol is not there where it needs
to be?

On Tue, Jul 11, 2023 at 1:50?PM Doug Wegscheid <dwegscheid@...>
wrote:

On Tue, Jul 11, 2023 at 07:12 AM, Alejandro olivan Alvarez wrote:

IEF244I VTP .TP .DD4 UNABLE TO ALLOCATE P01
IEF247I VTP ALLOCATION RECOVERY P01

I don't think the issue is the 3270s, what does the DD4 DD card in the
proc look like?

On Tue, Jul 11, 2023 at 07:12 AM, Alejandro olivan Alvarez wrote:

IEF244I VTP .TP .DD4 UNABLE TO ALLOCATE P01 IEF247I VTP ALLOCATION RECOVERY P01

I don't think the issue is the 3270s, what does the DD4 DD card in the proc look like?

Hi!

I'm messing with VS1 6.7 and I tried to install VTP 3.5 to give that a try (I know there's 3.7...but 3.5 seems to have a much more straightforward installation and overall footprint).
I got some problems due to DD statements beyond column 12, and I had to change a STEPCAT DD that complained about missing FGEN73 to FGEN67... but so far, I think I had all jobs, executing all steps, with condition 0 or at least without freaking output.

I added a pair of 3270 displays at 0C8 and 0C9 , as indicated on the README, and re-IPLed the system, which now starts much more automated, and, well.... looks good!

However, I'm unable to put VTP to run:
Either something is wrong with the installation and/or the underlying system, or I'm failing to guess the right answer to VTP startup job:

d a
IEE821I 12.50.29 ACTIVE DISPLAY 051
PNO JOBNAME STEPNAME SUBT STAT PNO JOBNAME STEPNAME SUBT STAT
WTRZ WTRZ WTR 00E
WTRF 00D 001 INITSWA P1 A,E
002 INITSWA P2 A,E 003 INITSWA P3 A,E
004 INITSWA P4 A,E
s vtp.p1
IEF244I VTP .TP .DD4 UNABLE TO ALLOCATE P01
IEF247I VTP ALLOCATION RECOVERY P01
IEF247I VTP 140,141,142,143,144,145,146,147,14A,14B OFFLINE P01
IEF247I VTP 14E,14F,150,152,153,154,155,156,157,158 OFFLINE P01
IEF247I VTP 159,15A,15B,15C,15D,15E,15F,1C0,1C1,1C2 OFFLINE P01
IEF247I VTP 1C3,1C4,1C5,1C6,1C7,1C8,1C9,1CA,1CB,1CC OFFLINE P01
IEF247I VTP 1CD,1CE,1CF,240,241,242,243,244,245,246 OFFLINE P01
IEF247I VTP 247,248,249,24A,24B,24C,24D,24E,24F,250 OFFLINE P01
IEF247I VTP 251,252,253,254,255,256,257,258,259,25A OFFLINE P01
IEF247I VTP 25B,25C,25D,25E,25F,2C0,2C1,2C2,2C3,2C4 OFFLINE P01
IEF247I VTP 2C5,2C6,2C7,2C8,2C9,2CA,2CB,2CC,2CD,2CE OFFLINE P01
IEF247I VTP 2CF,340,341,342,343,344,345,346,347,348 OFFLINE P01
IEF247I VTP 349,34A,34B,34C,34D,34E,34F,350,351,352 OFFLINE P01
IEF247I VTP 353,354,355,356,357,358,359,35A,35B,35C OFFLINE P01
IEF247I VTP 35D,35E,35F,3C0,3C1,3C2,3C3,3C4,3C5,3C6 OFFLINE P01
IEF247I VTP 3C7,3C8,3C9,3CA,3CB,3CC,3CD,3CE,3CF,450 OFFLINE P01
IEF247I VTP 451,452,453,454,455,456,457,4C0,4C1,4C2 OFFLINE P01
IEF247I VTP 4C3,4C4,4C5,4C6,4C7 OFFLINE P01
*00 IEF238A REPLY DEVICE NAME , OR 'CANCEL' P01

I have to answer always with a 'CANCEL' reply to end this job.
Otherwise, no matter which CUUs I reply to it (I have tried 0C0 and 0C9) it keeps asking over and over endlessly.

Maybe someone could help interpreting what's going on here: whether the install is messed or what does VTP needs to be told.

Thanks.
Regards.

Could you post a lot more information about what you were doing and how, and what happened? I just restored and reinstalled TX67308 on my system. It took four seconds to restore, and four seconds to reinstall. It sounds like you have other problems.

--
Kevin

...but now all jobs do this. I think the IEFACTRT usermod is bum?

Patience is a virtue. It took 136 minutes for R1 to get to 0, and then the job completed successfully. Weird.

I have a freshly generated 6.7, using the instructions and materials from the Files section of this group. the g13-smpinit.jcl job ran fine, so SMP is at least minimally functional.

I am trying to apply some of the usermods from . The first one I am byting off is TX67308 (a replacement IEFACTRT).

The job does not complete. It hits the initiator, seems to do some work judging by the PSW jumping all over the place, then goes into a tight problem state CPU loop, with the instruction address bits of the PSW running in range of less than 20(hex) bytes, and a large R1 value that seems to be decrementing (it's around BB000000 right now, suppose I could wait for it to go to 0 and see what happens).

Has anyone else been able to apply this (or any) usermod?

Hi!

This is fantastic news! :-)
I think to recall but that I tried the nothing jcl trick like in dos/vs but
It didn't work... However I probably messed It Up somehow X-p and it works
if properly done :-)

Cheers

On Sat, Jul 8, 2023 at 04:10 PM, Kevin Leonard wrote:

Maybe the reader got marked offline to VS1 because it wasn't ready.

Yes Kevin, it is exactly that. And varying it online solves the problem, like you indicated.

So I assume a job already present in the virtual reader will ready the reader, and if the system is run native, initializing 00C to a socket device does the trick too.

Cheers,

Rene FERLAND, Montreal

Maybe the reader got marked offline to VS1 because it wasn't ready. Issue a DISPLAY UNITS command to check:

d u,,,00c,1
IEE450I 23.01.35 UNIT STATUS 188
UNIT TYPE STATUS VOLSER VOLSTATE
00C 2540 OFFLINE

If it shows as OFFLINE, vary it online:

v 00c,online
IEE302I 00C ONLINE

and then put a job in the reader and start it.

If that's it, maybe we need to play with the DEVSTAT NIP function so it doesn't put unit record devices offline at startup.

--

There used to be patches to retrofit HASP to VS1 back in the 80’s but by the time I heard about them I didn’t have a vs1 system. Hopefully they can be found.
Laddie Hanus

Hi, Doug,

Did you include the "VM" option in your VS1 SYSGEN ? That way, you can
IPL and run OS/VS1 "stand-alone" on a "bare" machine (hercules), or you can
IPL and run VS1 in a VM/370 virtual machine. When you add that VM option,
the VM/VS handshaking code is included in the nucleus.

If you do not include that option, then VS1 will not "know" that it is
running in a virtual machine.

I think that's how that code gets added to IEFOSC05 ... when the VM option
is included, and when NIP detects it is IPLed under VM.

Hope that helps,

Mark


On Sat, Jul 8, 2023 at 1:48?PM Doug Wegscheid <dwegscheid@...>
wrote:

posting your separator would be wonderful! I saw the information in the
Planning and Use Guide, didn't want to start from scratch (my assembler
skills are very very rusty). I was going to try to disassemble the stock
IEFOSC??, as well as the VM writer one, but I'd prefer to start with yours.
I'm not running VS1 under VM, but the VM writer is interesting because it
was putting information into the CP CLOSE command, but it sounds like your
writer shows how to find that information anyway.

As I recall, the VM writer is on a bootable system named VSXRES, and gets
started on 00F ('S VMWTR'?) Are the original materials stowed away
somewhere?

On Saturday, July 8, 2023 at 07:04:48 PM GMT+2, Kevin Leonard <
groups-list@...> wrote:

A separator routine would probably be the way to go, and the Planning and
Use Guide is the book that tells you how to do it. For something like
this, it seems like you might want to write a single control line at the
beginning of the data set with the information you would need (in VS1, the
information available is pretty much limited to job name and SYSOUT
class). I wrote a separator routine that can be used to create a single
HASP-like page that's useful in separating output being viewed online. I
don't think I included it in the interim VS1 system package I created. If
you'd like I could post it here as a sample of a separator routine.

Of course, if you're actually printing output from VS1 using a VM writer,
there's the hack I used to use that puts the VS1 job name in the VM
separator page in block letters. You zap the CP CLOSE command in IEFOSC05
so instead of saying "CLOSE ddd NAME jjj" it says "CLOSE ddd DIST jjj".
DMKSEP in VM/370 writes two values in block letters: the first is the
virtual machine user ID, and the second is the distribution code. If you
set the distribution code for a particular print spool file to the job
name, you get the job name in block letters.

--

posting your separator would be wonderful! I saw the information in the Planning and Use Guide, didn't want to start from scratch (my assembler skills are very very rusty). I was going to try to disassemble the stock IEFOSC??, as well as the VM writer one, but I'd prefer to start with yours.
I'm not running VS1 under VM, but the VM writer is interesting because it was putting information into the CP CLOSE command, but it sounds like your writer shows how to find that information anyway.

As I recall, the VM writer is on a bootable system named VSXRES, and gets started on 00F ('S VMWTR'?) Are the original materials stowed away somewhere?

On Sat, Jul 8, 2023 at 01:17 PM, Kevin Leonard wrote:

For example, you would modify the RDR proc to add IEFPDSI DD statements defining the proclibs:

//IEFPDSI DD DSN=SYS1.PROCLIB,DISP=SHR,DSN=BLKSIZE=19040 // DD DSN=SYS2.PROCLIB,DISP=SHR

and then start your reader using a:

S RDR,00C

command instead of a STARTF.

that's what I ended up doing, works great.

I'm working on a script to take SYSC.PROCLIB and produce SYSC.PROCVS1 (no SYSOUT=*, no VIO). I should have it all packaged up in a week or so.

Hello Alejandro, Kevin,

I found the problem, actually the same I encountered before on other systems: you need to have a (first) job in the virtual card reader BEFORE the IPL. After starting the initiator, I just started the reader. That job runs, and after that everything goes fine (including handshaking apparently).

Cheers,

Rene FERLAND, Montreal

Adding user proclibs in VS1 is kind of messy.

There is a "default" proclib defined for VS1 use. If a reader is started by a STARTF command, or if the RDR proc doesn't contain an IEFPDSI DD statement, that "default" proclib is what is used to resolve procedure references in JCL. In VS1 releases 6.7 and earlier, that "default" proclib can't be modified by the user, and is always SYS1.PROCLIB. So the answer is, yes, you have to put your procs in SYS1.PROCLIB unless you want to add a user proclib, and the only way to specify a user proclib is to start a RDR proc that has an IEFPDSI DD statement defining your proclibs (you can't use the STARTF command and get a user proclib). For example, you would modify the RDR proc to add IEFPDSI DD statements defining the proclibs:

//IEFPDSI DD DSN=SYS1.PROCLIB,DISP=SHR,DSN=BLKSIZE=19040
// DD DSN=SYS2.PROCLIB,DISP=SHR

and then start your reader using a:

S RDR,00C

command instead of a STARTF.

--

A separator routine would probably be the way to go, and the Planning and Use Guide is the book that tells you how to do it. For something like this, it seems like you might want to write a single control line at the beginning of the data set with the information you would need (in VS1, the information available is pretty much limited to job name and SYSOUT class). I wrote a separator routine that can be used to create a single HASP-like page that's useful in separating output being viewed online. I don't think I included it in the interim VS1 system package I created. If you'd like I could post it here as a sample of a separator routine.

Of course, if you're actually printing output from VS1 using a VM writer, there's the hack I used to use that puts the VS1 job name in the VM separator page in block letters. You zap the CP CLOSE command in IEFOSC05 so instead of saying "CLOSE ddd NAME jjj" it says "CLOSE ddd DIST jjj". DMKSEP in VM/370 writes two values in block letters: the first is the virtual machine user ID, and the second is the distribution code. If you set the distribution code for a particular print spool file to the job name, you get the job name in block letters.

--

Hello Kevin,

No, the reader is not already started. See the execution log below:

THHC01027I Hercules version 4.6.0.10941-SDL-g65c97fd6, built on Jul 3 2023 17:38:06
HHC01031I Running on Socrate.local (Darwin-16.7.0.Darwin Kernel Version 16.7.0: Sun Jun 2 20:26:31 PDT 2019; roo 64-bit 64-bit x86_64 LP=4, Cores=4, CPUs=1)
HHC01018I 0:0004 COMM: client 127.0.0.1 devtype 1052: connected
VM/370 Online
logon vs1r67 vs1r67

LOGON AT 12:42:38 EST SATURDAY 07/08/23
ipl 148
IEA760A SPECIFY VIRTUAL STORAGE SIZE

IEA788I NON-PAGING MODE OF VS UNDER VM/370
IEE116A TOD CLOCK INVALID
IEA764I NIP01,CMD01,DFN01,JES01,SET01,SMF01
IEA765I DEVSTAT=ALL
IEA101A SPECIFY SYSTEM AND/OR SET PARAMETERS FOR RELEASE 06.7 OS/VS1
r 00,'date=95.188,gmt'
IEE055A SPECIFY LOCAL DATE AND/OR CLOCK
r 00,'clock=12.43.00'
IEE140I SYSTEM CONSOLES
CONSOLE/ALT COND AUTH ID AREA ROUTCD
30E/01F H CMDS 05 ALL
010/01F N ALL 01 Z,A ALL
01F/009 M ALL 02 ALL
009/010 N ALL 03 ALL
011/010 N ALL 04 Z,A 1-13,15-16
30E/01F A NONE 05 NONE
IEF032I PARMLIB VALUES TAKEN FOR JES
IEE101A READY
IEE029I JLPRM=(U)
IEF597I SYSTEM RESTART IN PROGRESS
IEF598I SYSTEM RESTART COMPLETED
IEF249I FOLLOWING P/R AND RSV VOLUMES ARE MOUNTED
FGEN67 ON 148 (P/R-PRV)
FDLB67 ON 149 (P/R-PRV)
PERM73 ON 14C (P/R-STR)
WORK73 ON 14D (P/R-PUB)
PAGE73 ON 151 (P/R-PRV)
IEE043I LOG DATA SET X QUEUED TO SYSOUT CLASS A
IEE052I MONITOR JOBNAMES,T ** FROM CMD01 AT IPL
IEE009I LOG NOW RECORDING ON DATA SET X
IEE052I MONITOR DSNAME ** FROM CMD01 AT IPL
IEE360I SMF NOW RECORDING ON SYS1.MANX ON 148. TIME=06.26.14
IEE048I INITIALIZATION COMPLETED
sf ,00e
IEF049I SYSLOGX ON DEVICE 00E
IEF868I 00E WTR WAITING FOR WORK
sf ,00d
IEF868I 00D WTR WAITING FOR WORK
s initswa.p1
IEF403I INITSWA STARTED TIME=06.26.35 P01
IEF005I PARTITION WAITING FOR WORK P01
RDR FILE 1158 HAS BEEN READ
#cp query files
FILES: 001 RDR, NO PRT, NO PUN
#cp query rdr
ORIGINID FILE CLASS RECDS CPY HOLD
VS1R67 1158 A RDR 000299 01 NONE
d a
IEE821I 06.27.31 ACTIVE DISPLAY 042
PNO JOBNAME STEPNAME SUBT STAT PNO JOBNAME STEPNAME SUBT STAT
WTRF 00D WTRF 00E
001 INITSWA P1 A,E
sf ,00c
IEF244I RDRF .00C .IEFRDER UNABLE TO ALLOCATE
p p1
IEF404I INITSWA ENDED TIME=06.27.59 P01
IEF049I INITSWA ON DEVICE 00E
IEF868I 00E WTR WAITING FOR WORK
IEF005I PARTITION WAITING FOR WORK P01
p 00d
IEF301I 00D WTR CLOSED
z eod
IEE018I LOG DATA SET EMPTY
IEE334I HALT EOD SUCCESSFUL
*IEE362A SMF ENTER DUMP FOR SYS1.MANX ON 148
IEE360I SMF NOW RECORDING ON SYS1.MANY ON 148. TIME=06.28.07
p 00e
IEF301I 00E WTR CLOSED
#cp
CP
query files
FILES: 001 RDR, 001 PRT, NO PUN
logoff
CONNECT= 00:02:44 VIRTCPU= 000:01.09 TOTCPU= 000:05.40
LOGOFF AT 12:45:23 EST SATURDAY 07/08/23

Cheers,

Rene FERLAND, Montreal

I'm not enthusiastic about tackling refitting HASP for VS1. The existing effort I looked at seemed to be missing macros and I wasn't excited about writing them. Maybe everything was there and I just wasn't seeing something.

--

The Planning and Use Guide is essentially the system programmer's guide for VS1. By MVS, system programmer documentation had been split across a number of manuals, but for VS1, a lot of it is in that one book.

--