Re: info ibm-main

On Fri, 17 Sep 2021 17:53:45 -1000, Anne & Lynn Wheeler wrote: >info ibm-main > ITYM -- gil -- For IBM-MAIN subscribe / signoff

info ibm-main

info ibm-main -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: The Business Case for Pipes in the z/OS Base (was: Re: REXX - Interpret or Value - Which is better?)

On Fri, 17 Sep 2021 14:56:15 -0500, Hobart Spitz wrote: >... > 15. Is consistent with policies for combating global warming of > customers, vendors and the public. ... > OK. But 40% of the U.S. electorate would consider that an argument "against". Think of the environmental impact of

Re: The Business Case for Pipes in the z/OS Base (was: Re: REXX - Interpret or Value - Which is better?)

One additional "against" (until the problem is solved): The knowledge of how to structure recovery from abends in one (or more) pipe stages is not well known in application circles. Most batch recovery today involves stopping any successor jobs (usually via scheduler dependency on successful

Re: The Business Case for Pipes in the z/OS Base (was: Re: REXX - Interpret or Value - Which is better?)

On Fri, 17 Sep 2021 16:21:25 -0400, Steve Thompson wrote: >EXECIO is not supported the same between z/os and CMS. This is a pain. > Yes. What are your specifics. Mine include: o Lack of the VAR and, especially STRING, options, requiring extra code. Is that an accommodation to syntactic

Re: RMF SMF "broken" records

On 17/09/2021 6:34 pm, Martin Packer wrote: Thanks! That's a much crisper version of what I had roughly surmised. That's an interesting case in the blog post. I wonder if bash has been / could be fixed. (Not that I run it on z/OS or write loops in it on Pi.) I think it is more useful for the

Re: RMF SMF "broken" records

Welcome to the murky world... :-) Off topic but are there usable start and stop timestamps for things running in BPXAS address spaces? I've wondered about z/OS Unix substeps and thingies but not had cause to dig too deep. (I know where I am with conventional batch jobs and steps when it comes

Re: RMF SMF "broken" records

Thanks! That's a much crisper version of what I had roughly surmised. That's an interesting case in the blog post. I wonder if bash has been / could be fixed. (Not that I run it on z/OS or write loops in it on Pi.) Cheers, Martin Martin Packer WW z/OS Performance, Capacity and Architecture,

Re: RMF SMF "broken" records

On 17/09/2021 5:32 pm, Martin Packer wrote: Off topic but are there usable start and stop timestamps for things running in BPXAS address spaces? I've wondered about z/OS Unix substeps and thingies but not had cause to dig too deep. (I know where I am with conventional batch jobs and steps when

Re: ICSF Hash with a certain seed (Key)

Isn't the the REXX program missing a call EBCDIC_to_ASCII ; statement before this one? hmg_text = text_ASCII ; Bill On Thu, 16 Sep 2021 15:40:57 -0300, Isabel wrote: >Hello again and thanks Eric and the others for all the answers, but we >still have problems. :( > >Here is what we

Re: What does CLIST have that REXX doesn't? (was Interpret or Value - Which is better?)

OK, I'll bite - what is STTEAM? -Original Message- From: IBM Mainframe Discussion List On Behalf Of Seymour J Metz Sent: Thursday, September 16, 2021 9:29 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: What does CLIST have that REXX doesn't? (was Interpret or Value - Which is better?)

Re: REXX - Interpret or Value - Which is better?

Years ago I used INTERPRET often, and I too switched to VALUE. There's still one use case that I still use INTERPRET, and that's for 'passing' many variables (most of which are stem) between programs. This program reads an input dataset that contains all of the variable names that should be

Re: What does CLIST have that REXX doesn't? (was Interpret or Value - Which is better?)

STTEAM is a trypo for "stream I/O". Off the top of my head that's CHARIN, CHAROUT, LINEIN, LINEOUT and STREAM functions. A second typo: EXCIO should be EXECIO. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List

DB2 rerunning install clist when applying maintenance

When applying maintenance several sysmod hold data will say to rerun the install clist in order to get jcl updates, etc and to regenerate the jobs. Should we run through it specifying "install" or "migrate" in order to get all jobs regenerated? There really isnt an option in the clist for

Re: REXX - Interpret or Value - Which is better?

Interpret is great for parsing tokenised values like parmlibs, jcl etc.. (DSN=xxx for example. I use value when the right field contains special characters or is lengthy. ITscahk בתאריך יום ו׳, 17 בספט׳ 2021 ב-16:54 מאת Brian Chapman : > Years ago I used INTERPRET often, and I too switched to

Re: IPL's POR's frequency

I would say it is 168 years (24*7=168). And to avoid such comments I usually write 24/7/365. :-) -- Radoslaw Skorupka Lodz, Poland W dniu 15.09.2021 o 19:41, Lennie Dymoke-Bradshaw pisze: 24x7x365 is actually 7 years. . Lennie -Original Message- From: IBM Mainframe Discussion

Re: registration problem

I've seen the same issue myself, what works for me, is I logoff, and log back on, for some reason once back online I can see  the IBM-MAIN list, still access to the archives. Carmen On 9/17/2021 1:00 PM, J Ellis wrote: we are trying to get some 'younger' folks registered on this list, they

Re: registration problem

Still 'NO' access to the Archives Carmen On 9/17/2021 1:22 PM, Carmen Vitullo wrote: I've seen the same issue myself, what works for me, is I logoff, and log back on, for some reason once back online I can see  the IBM-MAIN list, still access to the archives. Carmen On 9/17/2021 1:00 PM,

Re: IPL's POR's frequency

24x7x52 is only correct if if you shut down for a day (two in leap year). 24x365 is correct except in leap yars. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of

Re: IPL's POR's frequency

I would use 24X365. Of course that does not take into account the Leap Year day. 24X7X52 is more correct. Matthew On Fri, 17 Sep 2021 16:52:24 +0200, Radoslaw Skorupka wrote: >I would say it is 168 years (24*7=168). >And to avoid such comments I usually write 24/7/365. :-) > > >--

Re: ICSF Hash with a certain seed (Key)

Hello Eric!! Thanks so much for all your help! Regards, It appears that now it works! On Fri, Sep 17, 2021 at 9:58 AM Bill Godfrey wrote: > Isn't the the REXX program missing a > call EBCDIC_to_ASCII ; > statement before this one? > hmg_text = text_ASCII ; > > Bill > > On Thu, 16

registration problem

we are trying to get some 'younger' folks registered on this list, they get the email to click the link to complete the registration, they can see the list of subjects, however when the select IBM-Main, it opens a page and tells them they are not authorized to view the archives with the email

The Business Case for Pipes in the z/OS Base (was: Re: REXX - Interpret or Value - Which is better?)

IMHO, the Business Cases on Pipes in the z/OS Base are as follows. (Pipes is already available as part of BatchPipes.) The case *for *Pipes in the z/OS base.: 1. Development costs would drop for customers, vendors, and IBM, since everyone could use Pipes in their software. 2. Hardware

Re: The Business Case for Pipes in the z/OS Base (was: Re: REXX - Interpret or Value - Which is better?)

EXECIO is not supported the same between z/os and CMS. This is a pain. GLOBALV probably needs porting to solve other problems. I was tempted to do that on the last project I was on where we had REXX working between the two platforms. Sent from my iPhone — small keyboarf, fat fungrs, stupd