Re: Computer History (Was: CLIP?)

I have found them to be extremely "picky". I had offered them some 3330 disks, (I had 40 of them and offered them all to them) and they told me that they only could use 1, and then complained because the one I sent had "stickers" on it. The "stickers" (there are 2 on each external drive case)

Re: empty KSDS behavior - why?

I think this is just one of the quirky things IBM has been getting away with for years. It's that way, because the VSAM designers built it that way. It's not a big enough issue to go out an fix it (e.g. Have the IDCAMS DEFINE command (possibly optional) open the KSDS just defined, for OUTOUT and

Re: empty KSDS behavior - why?

On Tue, 29 May 2018 20:42:53 -0400, Doug Shupe wrote: >LOADED vs UNLOADED. > >Read the VSAM DEMISTIFIED Redbooks. > >When you define a VSAM file it is in an UNLOADED state, REPRO will open for >output and work just fine. > >If you write a record and delete the record the VSAM file is now in a LOA

Re: empty KSDS behavior - why?

I realize its been this way since (probably) "day 1". I was just wondering why. In my particular use case the application opens the file for updating (I-O mode in COBOL) and both checks for the existence of records with certain keys and inserts new records. There is no "loading" of the file w

Re: JCL 'SYMBOLS=' vs. IDCAMS SYMBOLICRELATE

On Tue, 29 May 2018 19:30:30 -0500, Paul Gilmartin wrote: >On Thu, 5 Oct 2017 06:54:22 -0500, Tom Marchant wrote: >>... >>In addition, a normal alias must be defined in the same catalog that holds >>the related data set name. With SYMBOLICRELATE, that is not a requirement. >> >Is this welcom

Re: empty KSDS behavior - why?

LOADED vs UNLOADED. Read the VSAM DEMISTIFIED Redbooks. When you define a VSAM file it is in an UNLOADED state, REPRO will open for output and work just fine. If you write a record and delete the record the VSAM file is now in a LOADED state. You should be able to open I/O or REPRO with the RE

Re: JCL 'SYMBOLS=' vs. IDCAMS SYMBOLICRELATE

On Thu, 5 Oct 2017 06:54:22 -0500, Tom Marchant wrote: >... >In addition, a normal alias must be defined in the same catalog that holds >the related data set name. With SYMBOLICRELATE, that is not a requirement. > Is this welcome relaxation for SYMBOLICRELATE a recent innovation? I can't fin

Re: IEFA107I when pointing to dataset alias

Also, if the symbol ends with an underscore, the value can be longer than the symbol. On Tue, May 29, 2018 at 7:05 PM Michael Babcock wrote: > I’m at z/OS 2.2 > > On Tue, May 29, 2018 at 4:46 PM Paul Gilmartin < > 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > >> On Tue, 29 May 2018 23

Re: IEFA107I when pointing to dataset alias

I’m at z/OS 2.2 On Tue, May 29, 2018 at 4:46 PM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 29 May 2018 23:30:22 +0200, Lucas Rosalen wrote: > > >The ALIAS must be in the same catalog as the actual dataset. > > > Not for SYMBOLICRELATE, but only in very recen

Re: empty KSDS behavior - why?

SPEED. RECOVERY does not appear to make any difference. HI-U-RBA is still 0. From: IBM Mainframe Discussion List on behalf of Gerhard Adam Sent: Tuesday, May 29, 2018 4:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: empty KSDS behavior - why? Perhaps a silly q

Re: empty KSDS behavior - why?

Perhaps a silly question, but were these files allocated with RECOVERY or SPEED? IIRC, RECOVERY pre-formats the first control area with binary zeros. In other words, does changing this specification change the behavior? Adam Sent from my iPhone > On May 29, 2018, at 3:12 PM, Frank Swarbrick

Re: IEFA107I when pointing to dataset alias

On Tue, 29 May 2018 23:30:22 +0200, Lucas Rosalen wrote: >The ALIAS must be in the same catalog as the actual dataset. > Not for SYMBOLICRELATE, but only in very recent z/OS. -- gil -- For IBM-MAIN subscribe / signoff / archive

Re: IEFA107I when pointing to dataset alias

On Tue, 29 May 2018 16:09:54 -0500, Michael Babcock wrote: >Okay, I'm getting myself confused regarding SYMBOLICRELATE. > >I have a data set, SYS3.LINKLIB which resides in CATALOG.USERSYS. I want to >define an alias called XX35.SYS3.LINKLIB (XX35 hlq data sets reside in >CATALOG.USERTSO) tha

Re: IEFA107I when pointing to dataset alias

I think the alias and the resolved dataset have to be in the same catalog. Mark Jacobs Michael Babcock May 29, 2018 at 5:09 PM Okay, I'm getting myself confused regarding SYMBOLICRELATE. I have a data set, SYS3.LINKLIB which resides in CATALOG.USERSYS. I want to d

Re: IEFA107I when pointing to dataset alias

The ALIAS must be in the same catalog as the actual dataset. I think you could bypass this in a very "strange" way by: 1. definig an ALIAS XX35.SYS3 in your CATALOG.USERTSO poiting to CATALOG.USERSYS. 2. Then, definig your ALIAS with the SYMBOLICRELATE in CATALOG.USERSYS. Regards, Lucas On Tue,

Re: IEFA107I when pointing to dataset alias

Okay, I'm getting myself confused regarding SYMBOLICRELATE. I have a data set, SYS3.LINKLIB which resides in CATALOG.USERSYS. I want to define an alias called XX35.SYS3.LINKLIB (XX35 hlq data sets reside in CATALOG.USERTSO) that points to the SYS3.LINKLIB data set. I've issued: DEF ALIAS(N

Computer History (Was: CLIP?)

Remember http://www.computerhistory.org/ -- Computer History Museum. They love artifacts, documentation, literature, memories: http://www.computerhistory.org/artifactdonation/ Date:Sun, 20 May 2018 03:39:44 -0500 From:Brian Westerman Subject: Re: CLIP? He originally had well thousands o

Re: empty KSDS behavior - why?

Not quite sure what you are asking, but... IDCAMS SYSTEM SERVICES PRINT IDS(DVFJS.DUMMY1) IDCAMS SYSTEM SERVICES LISTING OF DATA SET -DVFJS.DUMMY1 IDC0005I NUMBER OF RECORDS PROCESSED WAS 0 IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0 IDCAMS SYSTEM SERVICES PRINT IDS(DVFJS.DUMM

Re: empty KSDS behavior - why?

On Tue, 29 May 2018 19:12:32 +, Frank Swarbrick wrote: >Test 1 - both DVFJS.DUMMY1 and DVFJS.DUMMY2 are "un-initialized" (HI-U-RBA is >0): > > REPRO IDS(DVFJS.DUMMY1) ODS(DVFJS.DUMMY2) >IDC3300I ERROR OPENING DVFJS.DUMMY1 >IDC3351I ** VSAM OPEN RETURN CODE IS 160 >IDC0005I NUMBER OF RECORDS

Re: empty KSDS behavior - why?

Did you try reading in each case? I believe that you will find that the results differ. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Frank Swarbrick Sent: Tuesday, May 29, 2018 3:12 PM To: I

Re: empty KSDS behavior - why?

Test 1 - both DVFJS.DUMMY1 and DVFJS.DUMMY2 are "un-initialized" (HI-U-RBA is 0): REPRO IDS(DVFJS.DUMMY1) ODS(DVFJS.DUMMY2) IDC3300I ERROR OPENING DVFJS.DUMMY1 IDC3351I ** VSAM OPEN RETURN CODE IS 160 IDC0005I NUMBER OF RECORDS PROCESSED WAS 0 IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12

Re: empty KSDS behavior - why?

I'd guess that add/delete of low values and of high values would leave behing different structures, but that the differences wouldn't affect performance significantly; certainly not as much as one ABEND due to failure to prime. As for REPRO, I'd like to know that too. -- Shmuel (Seymour J.) Me

Re: empty KSDS behavior - why?

On Tue, 29 May 2018 18:12:16 +, Seymour J Metz wrote: >Why would IBM have to add a key? What is necessary is to create an empty KSDS >that can be read; add and delete is one way to do it, and doesn't leave a key >behind. I'd prefer that they just initialized it to have the same contents as

Re: empty KSDS behavior - why?

Why would IBM have to add a key? What is necessary is to create an empty KSDS that can be read; add and delete is one way to do it, and doesn't leave a key behind. I'd prefer that they just initialized it to have the same contents as adding and deleting. -- Shmuel (Seymour J.) Metz http://mas

Re: empty KSDS behavior - why?

On Tue, May 29, 2018 at 12:25 PM Frank Swarbrick < frank.swarbr...@outlook.com> wrote: > I don't think the key would matter, because it can immediately be deleted, > leaving the file "empty" but with the HI RBA appropriately set in order to > avoid the issue. > > I'm glad to see I'm not the only o

Re: empty KSDS behavior - why?

I don't think the key would matter, because it can immediately be deleted, leaving the file "empty" but with the HI RBA appropriately set in order to avoid the issue. I'm glad to see I'm not the only one bothered by this. I'm still wondering how much support an RFE might get. Is there any sta

Re: Old School Maintenance Philosophy -- Never ACCEPT?

I (used to) do something similar with a few added steps: DFDSS dump the whole SMP/E environment ACCEPT CHECK ACCEPT RECEIVE APPLY CHECK (there are sometimes system holds that need addressing before APPLY and this gets the report out as well as doing the APPLY CHECK) APPLY It's probably worth noti

Re: File transfer Red Alert

We now have instructions on how to upload doc to IBM via various methods, including (for us) HTTPS. I'm not so clear on how to handle a team of individuals (OS, CICS, DB2, etc.) who each send doc supporting their own SRs. In the analogous (?) case of RECEIVE FROM NETWORK, we install one certific

Re: File transfer Red Alert

Reposting to the list server for Rick. rs1...@gmail.com wrote: Updated post with new FAQ site: The Support File Transfer Details page has been updated and the Support File Transfer ID link is live. Please see http://public.dhe.ibm.com/SupportFileTransferDetails.html for all the details neede