Keyboard Shortcuts
Likes
- H390-OSVS
- Messages
Search
Re: SVS Rel. 1.7K allocating sysres datasets
Hi!
How did you stop TSO/VTAM? I'm not finding how to do that properly/cleanly. Whatever I do, VTAM never seems to finish to stop and NET, SNASOL,etc keep up. I bet there's an ellegant way to do that. I'm thinking on simply manually/cold start tk4- and try to just get jes2 up and running, but now I wonder how did you manage to just stop VTAM/TSO. Cheers |
SVS r1.7K generating starter system under tk4-
Hi!
I'm gathering all the pieces to generate the Starting system using the generating-system zipped JCLs under tk4-, and, while I got the whole picture clear enough to dare giving it a try, I miss a piece. Reading the description on the zip, I uderstand that both idecams.jcl and usercat.jcl files are VSAM master and user catalogs jobs, that we're advised NOT to be run while generating the staring system under tk4-, right?... if so, further question pop in my misnd: when and where should those jobs be run?... I guess they should be run under a running starter system, but I'm neither sure, nor I understand which volume is SRES17 present on a 3350 for the master catalog... at this point I'm staring to feel I'm missing something beyond what I have at hand. Could you please give me some clue? Thank you very much. Cheers. |
Re: SVS Rel. 1.7K allocating sysres datasets
Use and make needed modifications ctl files from OSVS1 sysgen package.
On Tue, Jul 18, 2023 at 11:52?AM Alejandro olivan Alvarez < alejandro.olivan.alvarez@...> wrote: Hi! |
Re: SVS Rel. 1.7K allocating sysres datasets
Hi!
I'm going to try to do so (prepare a starter system from Tk4-) , but I got stuck right from the beginning: I'm missing the control files for the DASDs creation. So, either I'm missing the point where I have to get additional stuff, or one is supposed to assemble the required control files (which sounds somehow challenging). Could you give some clue I could follow? Thank you very much. Cheers. |
Re: SVS Rel. 1.7K allocating sysres datasets
Glad you found the fix that works under MVS. It got me thinking, though: running the job under SVS rather than MVS, it works OK running without HASP, but gets ENQ failure for SYS1.PROCLIB with HASP because HOSRDR has SYS1.PROCLIB allocated. This could be a challenge. I'll have to think about it some more.
-- Kevin |
Re: VTP documentation
OS/VS predated my arrival to mainframe computing. I started just as
toggle quoted message
Show quoted text
the S/370 world emerged. So, what is VTP? Harold Grovesteen On Fri, 2023-07-07 at 08:14 -0700, Doug Wegscheid wrote:
I am trying to use VTP to update some PROCs, and the lack of docs is |
SVS Rel. 1.7K allocating sysres datasets
HI all.
I am trying to generate SVS Rel. 1.7K starter system using TK4-. I created the necessary DASDs, mounted them under MVS, loaded DLIB from tape to SDLB17 DASD, initialized SGEN17 DASD, and I am trying to allocate the necessary datasets on it. I am using the job "05-allocate-sysres.jcl", I have added the necessary authorization to the job card. When I started the job, I got the message: IEF861I FOLLOWING RESERVED DATA SET NAMES UNAVAILABLE TO G05RALC IEF863I DSN=SYS1.PARMLIB IEF863I DSN=SYS1.VTAMLIB *IEF099I JOB G05RALC WAITING FOR DATA SETS SGEN17 is mounted: 141 3350 O SGEN17 PRIV/RSDNT and from TSO I can allocate datasets on it. What am I doing wrong? Thank you for your answers. Bruno Novak |
Re: Unable to apply TX67308, infinite loop?
Glad you found it. Sometimes persistence is the only thing that can help you find things.
Thanks for posting the details. Maybe I can recreate the problem and see something that I could be checking to catch the problem and bypass it. This sounds like something that probably would get caught by a reasonability check, assuming I could see what to check. -- Kevin |
Re: Unable to apply TX67308, infinite loop?
On Mon, Jul 10, 2023 at 08:58 PM, Kevin Leonard wrote:
Found it. I had changed my hercules config on René Ferland's advice so that I didn't have to enter time at every boot (as a stopgap until I got TX67805 on). The original config works:
This config throws TX67308 into the loop.
I'll get TX67805 installed so I don't need the Hercules config hack. Smells like some date calculation getting used for both the WTO and the flowerbox; the looping code is getting invoked twice, it appears (I had to zap R1 twice to get it to exit). Thanks for confirming that TX67308 is indeed good on your system! |
Re: Unable to apply TX67308, infinite loop?
ok. I just made a copy of my system directory, and restored all the dasd from the tarball I took right after completing step g16 in the gen document. My STAGE1 is the distributed one. STAGE2 output looks a little different than the one distributed; I put that diff at the bottom of this posting (invocations of IEECRDCM differ slightly for DCM010 and DCM011, added JOBCAT DDs):
submit an IEFBR14 job. All is well. submitted tx67308.jcl. exceeded SWADS space. p p1 s init.p1,,space=(176,(4000),,contig) submitted tx67308.jcl. job runs for a few a seconds, then starts looping around 0xB015B2. I ended up stopping the CPU and stuffing a smaller value into R1 to speed things along (yes, I know that's not safe without understanding what it's doing, but I have nothing to lose at this point!)
Near as I can tell, the hang starts after the APPLY has taken place (the earlier steps did not do the WTO that TX67308 adds, nor give me a flowerbox). APPLY is the first step that I got the Here is how my stage2 differed from distributed:
|
Re: VTP 3.5 Starting device reply.
OK folks... It worked!
I added DLIBA1 at 150 to satisfy DD5 (not sure whther it is actually needed, maybe commneting DD5 as suggested would have been enough) I changed DD4 to point to WORK73, instead of WORK61. VTP is now working. It is very interesting... Thank you all for your help :-) Cheers. |
Re: VTP 3.5 Starting device reply.
Or comment out the bad DD cards....
On Tue, Jul 11, 2023 at 8:06 AM, Alejandro olivan Alvarez<alejandro.olivan.alvarez@...> wrote: Hi... I think you gave a clue... the tp03 jcl DDs DD4 and DD5 are refering to volumes that I don't have (WORK61 and DLIBA1)... so I guess this is the cause of failure. My system is using WORK73 and I thing DLIBA1 was the starter system volume... Interesting... I think I have something amiss here I have to try to attach DLIBA1 volume/DASD and/or WORK61 Cheers |
Re: VTP 3.5 Starting device reply.
Hi...
I think you gave a clue... the tp03 jcl DDs DD4 and DD5 are refering to volumes that I don't have (WORK61 and DLIBA1)... so I guess this is the cause of failure. My system is using WORK73 and I thing DLIBA1 was the starter system volume... Interesting... I think I have something amiss here I have to try to attach DLIBA1 volume/DASD and/or WORK61 Cheers |
Re: VTP 3.5 Starting device reply.
Maybe DLIBA1
toggle quoted message
Show quoted text
On Tue, Jul 11, 2023 at 2:00?PM Crni Mrki <crnimrki@...> wrote:
What say printout on virtual printer, which vol is not there where it |