开云体育

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

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

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

...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

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

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

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

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

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

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

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

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

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

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

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