Re: PDSCLEAN issue

No, Allan is right. LNKLST can include PDSE datasets but they seem to be managed differently to those added after IPL. They can't be deleted even after going through the Linklist unallocate palaver, and it seems they can't be emptied effectively. BTW, someone suggested DELETE PDSE(*) but that

Re: VSAM Performance - CPU reduction

Arun, In the IDCAMS listing, I see that the files are defined NONSPANNED. With the records being variable length, you could have as few as 2 records per ci, since the max is around 11000. if all the records are the minimum of 170, then you would have around 156 records per ci. Have you

Re: [EXTERNAL] CBT Tape Version 495 has been cut

Back in the olden days, we'd have to send Arnie a reel tape to get the updates. http://www.cbtclub.org/fall-social-photos-2017.html   In a message dated 1/17/2018 6:11:36 AM Central Standard Time, lionel.d...@va.gov writes:   Congratulations on another release. The site, and before that the

Re: VSAM usage for ancient disk models

Current (for us 2.1) z/OS HCD still shows 3375 as a valid DASD device type. IIRC 3375 was emulated CKD on FBA 3370 HDA's. I also think 3375s were used as the storage for the embedded 43X1's used as processor controllers on 3090s. Dana

Re: VSAM usage for ancient disk models

mitchd...@gmail.com (Dana Mitchell) writes: > Current (for us 2.1) z/OS HCD still shows 3375 as a valid DASD device > type. IIRC 3375 was emulated CKD on FBA 3370 HDA's. I also think > 3375s were used as the storage for the embedded 43X1's used as > processor controllers on 3090s. re:

Re: VSAM usage for ancient disk models

The 3090 processor controllers ran VM/370 on 3370 (FBA) disks. I was able to actually see one of these at a large NYC shop in the 1990's while touring it with a friend who was the VP of Operations there. The 3270 screen inside the 3090 box had the VM/370 screen logo. That made my day. I was

Re: running os/vs cobol in CICS 5.3 with DB2

Tim, I am looking for the QDM (quick and dirty method) to pull a shop into a more supported OS. There is no appetite for reworking code to accommodate the new COBOL. If we were actually able to run on something newer, there might be path for a small section of apps to go thru actual conversion.

VSE timeline [was: RE: VSAM usage for ancient disk models]

On this Wikipedia page, notes #44 and #45 lead to IBM z/VSE history pages that may tell you what you want to know. https://en.wikipedia.org/wiki/History_of_IBM_mainframe_operating_systems#DOS/VS 1980's VSE history: https://www-03.ibm.com/systems/z/os/zvse/about/history1980s.html 1990's

Re: VSAM usage for ancient disk models

Of course I remember the 3310, although I never used one. But your post reminds me of a question. Does anybody have a VSE timeline from the original DOS/VSE and ECPS:VSE that includes all of the packages, e.g., VSE/AF? There's a wike article on VSE and I'd like to flesh that out, or, better,

Re: Are Mainframes a Security Risk? | Enterprise Systems Media

Good hardware and good software don't ensure security, but they make it easier. Note that I wrote "easier", not "easy". There is no substitute for good management. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion

Re: VSAM usage for ancient disk models

MVS never supported the 3310 or 3370, but it supported the 3375 early on. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Edward Gould Sent:

Re: [EXTERNAL] CBT Tape Version 495 has been cut

On Wed, Jan 17, 2018 at 2:08 PM, R.S. wrote: > W dniu 2018-01-17 o 17:33, Edward Finnell pisze: > >> Back in the olden days, we'd have to send Arnie a reel tape to get the >> updates. >> >> >> http://www.cbtclub.org/fall-social-photos-2017.html >> In a message

Re: [EXTERNAL] CBT Tape Version 495 has been cut

-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Wednesday, January 17, 2018 3:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] CBT Tape Version 495 has been cut W dniu 2018-01-17 o 17:33, Edward Finnell pisze: >>

Re: Finding the names of hsm's BCDSs

Whilst you're waiting for IBM to deliver a proper API, you could trap the console output from a F DFHSM,Q CDS. DFHSM may well not be called DFHSM of course, so that will add a little extra work, perhaps using an ISGQUERY on ARCENQG On 17 January 2018 at 13:29, Manfred Lotz

Re: [EXTERNAL] CBT Tape Version 495 has been cut

W dniu 2018-01-17 o 17:33, Edward Finnell pisze: Back in the olden days, we'd have to send Arnie a reel tape to get the updates. http://www.cbtclub.org/fall-social-photos-2017.html In a message dated 1/17/2018 6:11:36 AM Central Standard Time, lionel.d...@va.gov writes: Congratulations

Re: [EXTERNAL] CBT Tape Version 495 has been cut

On Wed, 17 Jan 2018 14:11:02 -0600, John McKown wrote: >On Wed, Jan 17, 2018 at 2:08 PM, R.S. wrote: >> >> Excuse me, what CBT stands for? Is it a name (acronym) of bank? >> >​Connecticut Bank and Trust.​ > (More): http://www.cbttape.org/cbtfaq.htm -- gil

Re: Please Read: Server Certificates Expiring - Soon!

Please pardon the interruption for a brief comment. In case it is not completely obvious, the Digicert acquisition of the Geotrust CA also affects Verisign certificates. We have already encountered this issue (last week) with another business partner that used a certificate

Re: Finding the names of hsm's BCDSs

On Wed, 17 Jan 2018 09:04:18 +0100 Manfred Lotz wrote: :>I like to find out the DFSMShsm BCDS names programmatically. :>As I know the DD names, i.e. BAKCAT, and optionally BAKCAT2, BAKCAT3 :>and BAKCAT4 I thought of using AR mode in order to get the TIOT of HSM. :>However,

Re: DFSORT for HTTP logs - RECFM and BLKSiZE?

>I do believe that I should be able to point DFSORT at any file (Unix or not) >where performing the functions of DFSORT make sense, and not be required to >specify in JCL the physical attributes of LRECL, RECFM and most especially >BLKSIZE. These should all be derivable from the physical

Re: Are Mainframes a Security Risk? | Enterprise Systems Media

sorry to interfere, but there are compliance tools to help you find the gap between vendor requirements and reality. IBM, Vanguard, CA and of course us has tools. We just automated the process of compliance checks and send the results from many so called legacy systems to a single server, so the

Re: [EXTERNAL] Re: Please Read: Server Certificates Expiring - Soon!

Is there a way to subscribe to TechDocs? Some of them are really fun to read. A feed to https://www-03.ibm.com/support/techdocs/atsmastr.nsf/Web/TD-ByDate would be great! Can be made a part of the 'My Notifications' maybe..? – Vignesh Mainframe Infrastructure -Original Message- From:

Finding the names of hsm's BCDSs

Hi there, I like to find out the DFSMShsm BCDS names programmatically. As I know the DD names, i.e. BAKCAT, and optionally BAKCAT2, BAKCAT3 and BAKCAT4 I thought of using AR mode in order to get the TIOT of HSM. However, in order to get to the TIOT reliably I need SWAREQ which doesn't support

0C4 in IGGCSI00

If I pass an invalid filter key to IGGCSI00, I get an 0C4 in IGGCSI00. I don't see this on our normal z/OS V2R2 dev system; only on a zPDT running the ADCD Dec 2015 V2R2 build. Both systems have LMOD IGGCSI00 at the base level HDZ2220. On the other V2R2 system I get back RC4/Reas122 (Invalid

Re: 0C4 in IGGCSI00

On Wed, 17 Jan 2018 16:25:28 -0600, Kirk Wolf wrote: >If I pass an invalid filter key to IGGCSI00, I get an 0C4 in IGGCSI00. Invalid in what way? -- Walt -- For IBM-MAIN subscribe / signoff / archive

Re: VSE timeline [was: RE: VSAM usage for ancient disk models]

I remember the 3310. IBM called them "piccolo" drives because of the noise the actuators made. We received a bunch of these as replacements for faulty 3370s. That was back in 1981 when I was working at ICI Petrochemicals in the UK. The 3370s had a manufacturing fault that caused HDA failures. A

What about 3390-9 track???

I just read some chapter of DFSMS Macro Instructions for Datasets, the current one. And I found the manual claims a 3990-9 hac longer track size: it is 56669 - not 56664. Is it a typo or there is something I don't know??? (it is Appendix 1.5.4) -- Radoslaw Skorupka Lodz, Poland

Re: PDSCLEAN issue

On Tue, 16 Jan 2018 11:21:56 -0600, Paul Gilmartin wrote: >On Tue, 16 Jan 2018 16:08:49 +, Beesley, Paul wrote: > >>I have been using the PDSCLEAN program from the CBT tape file 693 for a while >> ... >>... >>The report says the PDSE has been cleared, and indeed

Re: PDSCLEAN issue

On Wed, 17 Jan 2018 16:20:28 -0600, Jeffrey Holst wrote: >> >As the manual DFSMS: Using Datasets notes: >A PDSE member is not actually deleted while in use. Any program connected to >the member when the delete occurs can continue to access the member until the >data set is closed. This is called a

Re: 0C4 in IGGCSI00

Don't see this problem on our system. z/os 2.2 RSU 1707 On Thu, Jan 18, 2018 at 9:25 AM, Kirk Wolf wrote: > If I pass an invalid filter key to IGGCSI00, I get an 0C4 in IGGCSI00. > > I don't see this on our normal z/OS V2R2 dev system; only on a zPDT running > the ADCD Dec

Re: 0C4 in IGGCSI00

Our dev LPAR at IBM also works OK. *** z/OS V2R2 - GA Code * Last Date z/OS CodeHOLDATA Changed Level Level DATE -- - --- -- 2017/12/26 V2R2 PUT1709/RSU1711 2017/12/21 I guess that's no consolation Kirk

Re: Finding the names of hsm's BCDSs

On Wed, 17 Jan 2018 15:04:11 +0200 ITschak Mugzach wrote: > Can you tell about the languages you wish to use and if this code > runs on a server side or client (TSO, Batch). > Assembler. The program runs in TSO. -- Manfred > ITschak > > On Wed, Jan 17, 2018 at 10:04

HCD CHIPD definition - SPAN

Thanks in advance for addressing my question ... I am defining a new partition on separate LCSS (most of our partition are on LCSS 1 and this new partition is on 1) and further defining a CHIPID of type OSC now the chipid's being defined should be in mode of "SPAN" as it's spanning across LCSS

Re: 0C4 in IGGCSI00

Same abens on our v2.2 (zPDT). ITschak בתאריך 18 בינו׳ 2018 4:04 לפנה״צ,‏ "Walt Farrell" כתב: > On Thu, 18 Jan 2018 11:38:28 +1100, Wayne Bickerdike > wrote: > > >Kirks example was *KIRK..FOO*. > > > >I don't even receive a message for that filter..

AW: Re: AW: Re: IEFA111I at IPL Time for z/OS V2.3

>I've arranged to have the System Messages documentation updated. Thanks, Scott, for having the doc updated. Saves me an RCF. -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to

Re: curious: Popularity & use of C on z/OS.

I was at IBM from 1978 and I certainly remember the spoof on the "COME FROM" statement. Some wag inside IBM wrote a fairly convincing treatise which was called "Structured Programming IBM's answer to the GOTO statement". At the time IBM were actively training us in Jackson Structured

Re: Are Mainframes a Security Risk? | Enterprise Systems Media

> On Jan 17, 2018, at 12:34 PM, Seymour J Metz wrote: > > Good hardware and good software don't ensure security, but they make it > easier. Note that I wrote "easier", not "easy". There is no substitute for > good management. > > Seymour: Some 20 years ago thew company I

Re: PDSCLEAN issue

My understanding is that the problem with deleting PDSE's after they have been in linklist, even after being removed from the currently active linklist set, was fixed in z/OS 1. See OW57609. Ant. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]

Re: PDSCLEAN issue

Oops, typo... z/OS 1.8 Sorry, Ant. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Anthony Thompson Sent: Thursday, 18 January 2018 10:46 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PDSCLEAN issue My understanding is that the

Re: [EXTERNAL] Are Mainframes a Security Risk? | Enterprise Systems Media

> On Jan 17, 2018, at 1:48 AM, Sankaranarayanan, Vignesh > wrote: > > "... he was able to find an exposure in z/OS rather fast, the ability of > almost any user to edit the APF (authorized program > facilities) and give yourself root access." >

Re: curious: Popularity & use of C on z/OS.

One of the issues of ACM SIGPLAN Notices definitively resolved this issue by suggesting that the any need for the harmful semantics of GOTO statement could easily be eliminated by instead allowing a "COME FROM" statement.  I can't remember which year, but it was an April issue.  :)     JC Ewing

Re: Finding the names of hsm's BCDSs

Would obtaining the data set names from SDSF meet your requirement? //DFHSMJOB MSGLEVEL=1 //STARTING EXEC DFHSM,CMD=00 XX XX*

Re: AW: Re: IEFA111I at IPL Time for z/OS V2.3

That's correct - the IEFA111I message is intended to be information to help debug a job that didn't behave as expected. It's issued when a job has MSGLEVEL=(,1) in effect. I've arranged to have the System Messages documentation updated. -Scott Ballentine (sbal...@us.ibm.com) z/OS Allocation,

Re: VSE timeline [was: RE: VSAM usage for ancient disk models]

You said: "The 3370s had a manufacturing fault that caused HDA failures. A good friend was an IBM CE and he told me that it was caused by contaminated lubricant." In about 1975, I recall Roger Buchanan, an IBM CE originally from Australia, described an IBM Disk Error problem he had just

Re: curious: Popularity & use of C on z/OS.

The old goto chestnut drops again. *Considered harmful* is a part of a phrasal template used in the titles of at least 65 critical essays in computer science and related disciplines.[1]

Re: VSE timeline [was: RE: VSAM usage for ancient disk models]

In 1987 I worked on a variant of the 4331. The 8890. Sold by Nixdorf but manufactured by Hitachi in Israel. We ran DOS/VSE with FBA drives made by Fujitsu but rebadged as Nixdorf. It was replaced by an IBM 9370 with 9335 FBA drives. The 2.5 MIPS of this box soon maxed out and we went back to a

Re: VSE timeline [was: RE: VSAM usage for ancient disk models]

> On Jan 17, 2018, at 12:16 PM, Farley, Peter x23353 > wrote: > > On this Wikipedia page, notes #44 and #45 lead to IBM z/VSE history pages > that may tell you what you want to know. > >

Re: Finding the names of hsm's BCDSs

Writing SRBs to sniff private storage data in another address space is not for the faint-hearted. It can be done, however it is very easy to do it incorrectly or in an unsafe manner. AR-Mode access to the foreign address space (HSM) is a big no-no - you are breaking system integrity rules and

Re: curious: Popularity & use of C on z/OS.

On 17/01/2018 3:19 AM, Paul Gilmartin wrote: On Tue, 16 Jan 2018 18:51:55 +, Seymour J Metz wrote: That's a common beginners' mistake. Try putting the label inside a do block and see what happens. A proper goto would pop what needs to be popped and no more. See

Re: [EXTERNAL] CBT Tape Version 495 has been cut

I second that! -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Dyck, Lionel B. (TRA) Sent: Wednesday, January 17, 2018 7:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] CBT Tape Version 495 has been cut [External Email]

Re: Finding the names of hsm's BCDSs

Can you tell about the languages you wish to use and if this code runs on a server side or client (TSO, Batch). ITschak On Wed, Jan 17, 2018 at 10:04 AM, Manfred Lotz wrote: > Hi there, > I like to find out the DFSMShsm BCDS names programmatically. > > As I know the DD

Re: PDSCLEAN issue

On Tue, 16 Jan 2018 16:25:40 +, Allan Staller wrote: >The only restriction I am aware of is that the PDSE cannot be in the IPL time >LINKLIST. I think you mean LPA. LNKLST can include PDSE data sets. -- Tom Marchant --

Re: Finding the names of hsm's BCDSs

On Wed, 17 Jan 2018 12:01:22 + Rob Scott wrote: > In the meantime, you could try and come up with a safer local > solution based around using ISGQUERY for the SYSDSN major name > enqueues for the HSM address space. > > Depending on local naming standards you could

Re: [EXTERNAL] CBT Tape Version 495 has been cut

Congratulations on another release. The site, and before that the tape, have been a great benefit to the mainframe community and your work is greatly appreciated. -- Lionel B. Dyck < Mainframe Systems Programmer - TRA