开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育

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

 

Aha... makes sense!

Will try that, thank you!

Cheers


Re: SVS Rel. 1.7K allocating sysres datasets

 

Use and make needed modifications ctl files from OSVS1 sysgen package.


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!

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

 

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

 

On Fri, Jul 14, 2023 at 08:42 AM, Harold Grovesteen wrote:

So, what is VTP?

I fiddled with it a little. It looks like it has a lot of the functionality that we would have with RFE or RPF, but without having to have TSO in place.


Re: VTP documentation

 

OS/VS predated my arrival to mainframe computing. I started just as
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
slowing me down. Do any exist?

In lieu of that:

* how do I create a new member in a PDS?

* how do I insert lines into a member that I am editing?





Re: VTP documentation

 

As I know, you can edit member with job for (don't remember which, but you can find it when you choose this item in menu).
Then simple submit this job from editor with SUB command.


Re: VTP documentation

 

Hi.

I'm on hte same boat.
It is a very interesting piece of software... incredible work.
But once I'm in, I feel lost... Have you managed to 'logoff'? I don't manage to do so... I don't find the way to return to the logon screen and switch user.

Cheers.


Re: SVS Rel. 1.7K allocating sysres datasets

 

To answer myself, Job passed when I stopped tso and vtam.


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:

t sounds like you have other problems.

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:

YROFFSET  -28           # <-- comment out if TX67805 has been installed
TZOFFSET  -0400         # <-- Eastern daylight time

This config throws TX67308 into the loop.

SYSEPOCH  1960
YROFFSET  -40
TZOFFSET  -0400

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):

ipl 150
sf ,00c
sf ,00e
s init.p1

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!)

HHC02245I 0:000C device initialized                                                                                                                                     
/ IEF543I 00C RDR FLUSHING JOBSTREAM AFTER JOB TX67308                                                                                                                  
/ IEF039I 00C RDR WAITING FOR WORK                                                                                                                                      
/ IEF403I TX67308  STARTED TIME=08.29.53 P01                                                                                                                            
...process process process, loop loop loop...
HHC01603I stop                                                                                                                                                          
HHC00834I Processor CP00: manual state selected                                                                                                                         
HHC01603I gpr 01=1000                                                                                                                                                   
HHC02269I General purpose registers                                                                                                                                     
HHC02269I GR00=0000007B GR01=00001000 GR02=00DFBA48 GR03=00DFECD0                                                                                                       
HHC02269I GR04=002EB22A GR05=00DFF050 GR06=00000000 GR07=90B00D72                                                                                                       
HHC02269I GR08=00DFEC20 GR09=00DFD380 GR10=00DFECD0 GR11=00B00BD8                                                                                                       
HHC02269I GR12=00DFE9A8 GR13=00DFBA48 GR14=A0B014C6 GR15=00000002                                                                                                       
HHC01603I start                                                                                                                                                         
HHC00834I Processor CP00: running state selected                                                                                                                        
/ STEP: TX67308  APPLY    SMP      ET=00.00.04 RC=0000 P01                                                                                                              
...loop loop loop...
HHC01603I stop                                                                                                                                                          
HHC00834I Processor CP00: manual state selected                                                                                                                         
HHC01603I gpr 01=1000                                                                                                                                                   
HHC02269I General purpose registers                                                                                                                                     
HHC02269I GR00=0000007B GR01=00001000 GR02=00DFCFA8 GR03=00DFEB70                                                                                                       
HHC02269I GR04=002F32C9 GR05=00DFF050 GR06=00000000 GR07=A0B0118A                                                                                                       
HHC02269I GR08=00DFE8C0 GR09=00DFD5E8 GR10=00DFEB70 GR11=00B00BD8                                                                                                       
HHC02269I GR12=00DFE9A8 GR13=00DFCFA8 GR14=A0B014C6 GR15=00000000                                                                                                       
HHC01603I start                                                                                                                                                         
HHC00834I Processor CP00: running state selected                                                                                                                        
/ IEF404I TX67308  ENDED   TIME=08.37.17 P01                                                                                                                            
/ IEF049I TX67308  ON DEVICE 00E                                                                                                                                        
/ IEF005I PARTITION WAITING FOR WORK  P01                                                                                                                               
/ IEF868I 00E WTR WAITING FOR WORK         

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 STEP: TX67308 APPLY SMP ET=00.00.04 RC=0000 P01 and flowerbox.

Here is how my stage2 differed from distributed:

*** g09.jcl     2023-06-30 23:03:10.000000000 -0400
--- g09-stage2.jcl.save 2021-07-01 16:43:17.000000000 -0400

*** 1,4 ****
--- 1,5 ----
  //G09GEN1 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC ASMS,OBJ=OBJPDS1,MOD=IEAPGSPP,CLASS=A
  //SYSIN DD *
        PRINT ON,NODATA

*** 372,380 ****
  //SYSIN DD *
        PRINT ON,NODATA
  IEECVH1   CSECT
!       IEECRDCM DEV=D,                                            CCCCCCCCCCC
!                A=(14,                                                CATCHALL
!                )
   END
  /*
  //SG20 EXEC ASMS,OBJ=OBJPDS1,MOD=DCM010,CLASS=A
--- 373,379 ----
  //SYSIN DD *
        PRINT ON,NODATA
  IEECVH1   CSECT
!          IEECRDCM DEV=D
   END
  /*
  //SG20 EXEC ASMS,OBJ=OBJPDS1,MOD=DCM010,CLASS=A

*** 389,397 ****
        PRINT ON,NODATA
  IEECVH2   CSECT
        IEECRDCM DEV=D,                                            CCCCCCCCCCC
!                KEY=IEECVK3,                                      CCCCCCCCCCC
!                A=(14,                                               CATCHALL
!                )
   END
  /*
  //SG22 EXEC ASMS,OBJ=OBJPDS1,MOD=DCM011,CLASS=A
--- 388,394 ----
        PRINT ON,NODATA
  IEECVH2   CSECT
        IEECRDCM DEV=D,                                            CCCCCCCCCCC
!                KEY=IEECVK3
   END
  /*
  //SG22 EXEC ASMS,OBJ=OBJPDS1,MOD=DCM011,CLASS=A

*** 486,491 ****
--- 483,489 ----
           END
  /*
  //G09GEN2 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC ASMS,OBJ=OBJPDS3,MOD=IEAASU00,CLASS=A
  //SYSIN DD *
        PRINT ON,NODATA

*** 3587,3592 ****
--- 3585,3591 ----
      END
  /*
  //G09GEN3 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC ASMS,OBJ=OBJPDS2,MOD=IEFQMSGV,CLASS=A
  //SYSIN DD *
        PRINT ON,NODATA

*** 4069,4074 ****
--- 4068,4074 ----
           END
  /*
  //G09GEN4 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC PGM=IEBCOPY,COND=(8,LT)
  //SYSUT3 DD DSN=&SYSUT3,SPACE=(1700,(10,5)),UNIT=SYSDA
  //SYSUT4 DD DSN=&SYSUT4,SPACE=(460,(30,24)),UNIT=SYSDA

*** 4185,4190 ****
--- 4185,4191 ----
   S M=((IEELGON2,,R))
  /*
  //G09GEN5 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC PGM=IEBCOPY,COND=(8,LT)
  //SYSUT3 DD DSN=&SYSUT3,SPACE=(1700,(10,5)),UNIT=SYSDA
  //SYSUT4 DD DSN=&SYSUT4,SPACE=(460,(30,24)),UNIT=SYSDA

*** 4663,4668 ****
--- 4664,4670 ----
   SELECT MEMBER=(IGC0024I)
  /*
  //G09GEN6 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC  PGM=IEBCOPY,COND=(4,LT)
  //SYSPRINT DD SPACE=(121,(500,40),RLSE),
  //   DCB=(RECFM=FB,LRECL=121,BLKSIZE=121),SYSOUT=A

*** 4693,4698 ****
--- 4695,4701 ----
   COPY  OUTDD=SAMPLIB,INDD=ASAMPLIB
  /*
  //G09GEN7 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC PGM=IFCDIP00,COND=(8,LT)
  //STEPLIB DD DSN=SYS1.AOSCD,DISP=SHR
  //SERERDS DD   DSN=SYS1.LOGREC,DISP=(NEW,KEEP),

*** 4705,4710 ****
--- 4708,4714 ----
   CATLG CVOL=3350=FGEN67,VOL=3350=FGEN67,DSNAME=SYS1.LOGREC
  /*
  //G09GEN8 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC PGM=IEBCOPY,COND=(8,LT)
  //SYSUT3 DD DSN=&SYSUT3,SPACE=(1700,(10,5)),UNIT=SYSDA
  //SYSUT4 DD DSN=&SYSUT4,SPACE=(460,(30,24)),UNIT=SYSDA

*** 4718,4723 ****
--- 4722,4728 ----
   COPY OUTDD=OBJ1,INDD=((OBJ3,R))
  /*
  //G09GEN9 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC PGM=IEBCOPY,COND=(8,LT)
  //SYSUT3 DD DSN=&SYSUT3,SPACE=(1700,(10,5)),UNIT=SYSDA
  //SYSUT4 DD DSN=&SYSUT4,SPACE=(460,(30,24)),UNIT=SYSDA

*** 5496,5501 ****
--- 5501,5507 ----
    NAME  IGC40110(R)
  /*
  //G09GEN10 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC LINKS,
  // PARM='NCAL,LIST,XREF,REUS',
  //    UNIT='3350',SER=FGEN67,N=SYS1,NAME=LINKLIB,P1=' ',

*** 5599,5604 ****
--- 5605,5611 ----
  ./  ENDUP
  /*
  //G09GEN11 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC LINKS,COND=(4,LT),
  //     PARM='LIST,XREF,NCAL,SCTR,LET,SIZE=(192K,64K)',
  //     UNIT='3350',SER=FGEN67,N=SYS1,NAME=NUCLEUS,P1='(',

*** 5801,5806 ****
--- 5808,5814 ----
   INCLUDE RESLIB(IGC255)
  /*
  //G09GEN12 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC LINKS,
  // PARM='NCAL,LIST,XREF,LET',
  //    UNIT='3350',SER=FGEN67,N=SYS1,NAME=LINKLIB,P1=' ',

*** 8697,8702 ****
-- 8705,8711 ----
   NAME IGG019P2(R)
  /*
  //G09GEN13 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC PGM=IEHIOSUP
  //STEPLIB DD DSN=SYS1.LINKLIB,DISP=SHR,
  //   VOL=SER=FGEN67,UNIT=3350

*** 8706,8711 ****
--- 8715,8721 ----
  //     VOL=(,RETAIN,SER=FGEN67),UNIT=3350
  /*
  //G09GEN14 JOB 1,'SYSTEM GENERATION',CLASS=A,MSGCLASS=A,TYPRUN=HOLD
+ //JOBCAT   DD  DISP=SHR,DSN=SYS1.FDLB67.CATALOG
  //SG1 EXEC PGM=IEHLIST
  //SYSPRINT DD SPACE=(121,(1500,300),RLSE),
  //   DCB=(RECFM=FB,LRECL=121,BLKSIZE=121),SYSOUT=A

*** 8746,8751 ****
   LISTPDS VOL=3350=FGEN67,DSNAME=SYS1.MACLIB
   LISTPDS VOL=3350=FGEN67,DSNAME=SYS1.SAMPLIB
  /*
- 
- 
- 
--- 8756,8758 ----


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

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