Re: ADR137E - FILTERDD
Thank you for this feedback. Theo Buckton Mainframe Storage Engineer | Group Technology | Nedbank Floor, Block, Address, Country PO Box 1144, Johannesburg 2000, South Africa T +27 (0)00 000 F +27 (0)00 000 C +27 (83) 581 3017 @ the...@nedbank.co.za Website nedbank.co.za THINK BEFORE YOU PRINT - At Nedbank we are committed to minimising our environmental impact and encourage the preservation of natural capital -Original Message- From: IBM Mainframe Discussion List On Behalf Of Robert2 Gensler Sent: Friday, 17 April 2020 13:26 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ADR137E - FILTERDD CAUTION - EXTERNAL SENDER - Please be careful when opening links and attachments. Nedbank - IT Information Security Department (ISD) The contents of 'your.filtdd.here' would be something like: INCLUDE(mydata1, - mydata2, - ...) Here is an example in our pubs: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.adru000/r2355.htm Thanks, Robert Gensler DFSMSdss Development Beavercreek, OH rgen...@us.ibm.com IBM Mainframe Discussion List wrote on 04/17/2020 05:57:39 AM: > From: "Richards, Robert B." <01c91f408b9e-dmarc-requ...@listserv.ua.edu> > To: IBM-MAIN@LISTSERV.UA.EDU > Date: 04/17/2020 05:57 AM > Subject: [EXTERNAL] Re: ADR137E - FILTERDD Sent by: IBM Mainframe > Discussion List > > From a coworker's JCL: > > //STEP1 EXEC PGM=ADRDSSU,REGION=2048K //SYSPRINT DD SYSOUT=* > //OUTVOL1 DDVOL=SER=xx,UNIT=3390,DISP=SHR > //FILTERDS DDDSN=your.filtdd.here, > // DISP=(OLD,KEEP) > //SYSINDD* > COPY DATASET(FILTERDD(FILTERDS)) - > CANCELERROR - > CATALOG - > OUTDDNAME( - > OUTVOL1 - >) - >RENAMEUNCONDITIONAL(Y) - > TGTALLOC(SOURCE) - > ADMINISTRATOR - > WAIT(2,2) > /* > > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Buckton, T. (Theo) > Sent: Friday, April 17, 2020 5:51 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: ADR137E - FILTERDD > > Hi, > > I need assistance with abend code ADR137E and the FILTERDD keyword. > This abend code points to the fact that more than 255 entries are > specified in a INCLUDE statement. The DFSMSdss manual says that the > FILTERDD keyword must be specified - but I cannot find a sample JCL > that contains the FILTERDD statement. > > Anyone with such an sample JCL? Please help. > > Regards > > > > Nedbank disclaimer and confidentiality notice: > > This email may contain information that is confidential, privileged or > otherwise protected from disclosure. If you are not an intended > recipient of this email or all or some of the information contained > therein, do not duplicate or redistribute it by any means. Please > delete it and any attachments and notify the sender that you have > received it in error. Unless specifically indicated, this email is > neither an offer or a solicitation to buy or sell any securities, > investment products or other financial product or service, nor is it > an official confirmation of any transaction or an official statement > of Nedbank. Any views or opinions presented are solely those of the > author and do not necessarily represent those of Nedbank. Nedbank Ltd > Reg No 1951/09/06. > > The following link displays the names of the Nedbank Board of > Directors and Company Secretary. [https://urldefense.proofpoint.com/ > v2/url? > u=http-3A__www.nedbank.co.za_terms_DirectorsNedbank.htm=DwIFAg=jf_iaSHvJObTbx- > siA1ZOg=4IouVQcajkz0Xk8aBQYNyp4CJn0tmfX31FiYrnNQujA=C2XoFZLziFHqJocTAOtMEKDLk0cvb- > B5qChAPoDwf9o=PJyKwuzrP_h2Nnufvc6xlgXaFv1CWxmIfBaxVO7TUN8= ] > > If you do not want to click on a link, please type the relevant > address in your browser > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Nedbank disclaimer and confidentiality notice: This email may contain information that is confidential, privileged or
Re: JES2 parm change - how make sure it's right?
*Drifting the topic, any product that lets you make changes via command really could use an option to generate a new startup options file that reflected all of the cumulative changes.It would take some doing to do it in way that preserved comments. And avoided misleading comments.* --- If I'm not sure of a command,I put it into a file and issue it via ISFSLASH. One store of these commands can be a PDS. Just add them in some logical sequence. When you can't remember,"what was that command". Just refer to the command file. I find the JES2 commands incredibly cryptic and from time to time, we're asked to $T a jobclass. That's when my file comes in handy. I issue the commands via a REXX program which reads the PDS. Easy to comment out a command when parsing it to decide when to issue it or not. On Sat, Apr 18, 2020 at 6:35 AM Charles Mills wrote: > Drifting the topic, any product that lets you make changes via command > really could use an option to generate a new startup options file that > reflected all of the cumulative changes. > > It would take some doing to do it in way that preserved comments. And > avoided misleading comments. > > Original options file: > > FOO = NO ; Turn off the FOO option > > Assuming FOO was then turned on dynamically, you would not want an updated > file that now said > > FOO = YES ; Turn off the FOO option > > Perhaps the trick would be to comment out any changed statements and put > documenting comments on generated statements, so the result would be > > ; FOO = NO ; Turn off the FOO option > FOO = YES ; Generated by AUTO-OPTION > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Seymour J Metz > Sent: Friday, April 17, 2020 1:10 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: JES2 parm change - how make sure it's right? > > Is there an RFE or Share requirement to examine the running JES2 and > produce an updated initialization deck that > reflects the initial parameters and the dynamic updates? ISAGN. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Any shop use UNIX in a production job?
Hey R.S. , Boy I must have lived a sheltered "professional life", I have heard of some of these not many thorough. I worked at a past life we did LU 6.2 file xref and supported 26+ platforms and a lot of variations of Unix. But this was 15+ yrs ago, so times have changed and so have platforms. Scott On Fri, Apr 17, 2020 at 1:59 AM Timothy Sipples wrote: > Radoslaw Skorupka wrote: > >You mentioned several times about source code. IMHO it is irrelevant > >for UNIX certification. My understanding is "black box": anything which > >behaves as UNIX is UNIX. It can be written from scratch. > >Obviously, an access to source code seem to be much easier. > > First of all, maybe you missed my other post? > > There are many outcomes that are hypothetically possible that haven't > happened often. To my knowledge there's only one organization and product > that has ever achieved UNIX certification without some AT/Bell Labs code > lineage: IBM with z/OS UNIX. History suggests it was REALLY difficult. > There were many previous efforts that never really took off: > > 1. Somebody was asking about the UNIX subsystem that was available for > TSS/370. That was a collaboration with Bell Labs, as this paper from 1984 > discusses: > > https://www.bell-labs.com/usr/dmr/www/otherports/ibm.pdf > > TSS/370 UNIX became available in 1980, although (like TSS/370 and TSS/360) > I don't think it was ever an "official" IBM product. > > 2. INTERACTIVE Systems Corporation (ISC) developed a VM/370-based system > called VM/IX. > > 3. ISC's IX/370 was a VM/SP-based version of TSS/370's UNIX, updated with > UNIX System V compatibility. (Reference: IBM Announcement Letter 285-048.) > > 4. I think there was also an IX/360 from ISC, although I cannot find much > information about it. > > 5. AIX/370 was introduced in 1990. (References: IBM Announcement Letters > 288-130, 288-131, 289-075, and 289-412. Letter 289-412 also announced the > withdrawal of IX/370.) AIX/ESA followed in 1992. (Reference: IBM > Announcement Letter 291-544.) > > 6. Amdahl had UTS, and they started selling it commercially in 1980. UTS > notionally survived until fairly recently under UTS Global's stewardship. > > As far as I know *all* of these efforts were liberally based on AT's > UNIX source code. Maybe someone has interest in diving into code rescue > efforts to see how many of these UNIXes they can recover and reanimate. > There could be copyright impediments, though. > > In 2003 Peter Salus recounted some of the history of INTERACTIVE Systems > Corporation as he remembers it (on page 68): > > https://www.usenix.org/system/files/login/issues/login_december_2003.pdf > > I don't think he has the chronology quite right, though, but that's > understandable. I think at least IX/360 must have preceded PC/IX. (Why > call something "IX/360" in 1984? Or even 1980?) His recollection that some > other team started IX/360 agrees with the other information I found that > it started at Bell Labs with TSS/370 UNIX. And did VM/IX fold into IX/370? > It's very difficult to get this chronology sorted. > > - - - - - - - - - - > Timothy Sipples > I.T. Architect Executive > Digital Asset & Other Industry Solutions > IBM Z & LinuxONE > - - - - - - - - - - > E-Mail: sipp...@sg.ibm.com > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- *IDMWORKS * Scott Ford z/OS Dev. “By elevating a friend or Collegue you elevate yourself, by demeaning a friend or collegue you demean yourself” www.idmworks.com scott.f...@idmworks.com Blog: www.idmworks.com/blog *The information contained in this email message and any attachment may be privileged, confidential, proprietary or otherwise protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.* -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
JSON PARSE statement format ???
Hello again everyone,
I have been trying to use the new JSON PARSE statement and I am having a
little difficulty in understanding what is really needed.
I have a JSON document that looks something along the lines of:
{"httpHeaders":{"traceID":"my trace id data","spanID":"my spanid data"}}
I pass this to my CICS COBOL PROGRAM, where I have a working storage area
like this:
05 WS01-CONTEXT-HEADERS.
10 WS01-CH-TRACE-DATA PIC X(36).
10 WS01-CH-SPAN-DATA PIC X(36).
In the program I have a JSON PARSE statement like this:
JSON PARSE my input UTF8 data
INTO WS01-CH-CONTEXT-HEADERS
WITH DETAIL
NAME OF WS01-CONTEXT-HEADERS is 'httpHeaders'
WS01-CH-TRACE-DATA is 'traceID'
WS01-CH-SPAN-DATA is 'spanID'
END-JSON
Yes, I also have on exception
In any event, when I run this, it does what I want it to do, specifically,
that WS01-CH data fields have the data I want after the PARSE completes.
However, since I have WITH DETAIL specified, I can see a few things in the
CICS Region logs.
A few IGZ0321I messages. IGZ0321I During execution of the JSON PARSE
statement on line 16801 of program MYPROGR, no JSON name/value TRACEID,
which was thus not modified.
huh?
I think this means that the JSON object did not contain a name/value pair
for "TRACEID".
Which is what is expected because I specified "NAME OF" in the parse
statement.
So is this just to inform me things were done as I requested?
I realize this is just an FYI, and it will disappear when I get rid of
"WITH DETAIL".
I explicitly said I had other variables I wanted to use.
The program ran and did what I wanted.
What if anything, can I do to remove this Informational message?
Last question, because I am curious.
This is an http CONTEXT Header coming in over a z/OS Connect POST CICS
Container request.
Can I modify anything in the Context Header in my COBOL program, and have
it returned to z/OS Connect outside of the actual Response Message
Container that goes back?
Somehow it just seems wrong to think about that. The CONTEXT HEADERS are
likely read only.
But I don't know enough yet to understand this.
And I am having way too much fun.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: JES2 parm change - how make sure it's right?
On Sat, 18 Apr 2020, at 02:38, Lizette Koehler wrote: > Other option is to create a Secondary JES2, and test your parms there. I > have done this in the past and it is not difficult to do. I have a distant memory of using a secondary jes2 this way, and I think we concatenated the test parm deck onto a fixed one with a definite syntax error in it, so that even if the test deck was ok, the secondary would always find at least the error(s) in the last part of the deck. We might also have prefixed the test deck with lines defining a separate ckpt and spooldef from the real MAS's one. I can't quite remember. Ideally you still want to do this on a test system first, to get familiar with the process. -- Jeremy Nicoll - my opinions are my own. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
