Re: Me Want Cookie!

2021-12-29 Thread Bob Bridges
I once wrote an article (so to speak) explaining cookies to my mom. My main theme was that I don't understand why people are so up in arms about them. I suppose it must be an extension of the general dislike of being tracked. But given that vendors are going to keep track of your information

Me Want Cookie!

2021-12-29 Thread Paul Gilmartin
Sometimes I browse the IBM-MAIN website with a handheld; more often with a laptop. I want different display preferences according to the different screen sizes. But when I switch from handheld to laptop or vice-versa, LISTSERV redraws the page on the new device to match the previous. I truly

Re: COBOL V4.2 to V6.3

2021-12-29 Thread Seymour J Metz
The binder is a different program from the linkage editor; z/OS includes both+, but only the binder can handle program objects. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on

COBOL V4.2 to V6.3

2021-12-29 Thread Tom Ross
>Then we take this file and execute through the PRELINK step. >The prelink program name is EDCPRLK. > >This is where the problem occurs. The prelinker is no longer supported with COBOL V5 and later. The COBOL migration guide explains what to do instead, normally just use the binder (what used to

Re: SMF119 - Subtype 20 and Subtype 21

2021-12-29 Thread Peter
Hello Massimo, Please do share to my personal email if you are fine with it. I will try On Wed, 29 Dec, 2021, 9:05 pm Massimo Biancucci, wrote: > Jake, > > I wrote a mix of REXX and Sort to do the task (CSV file as output) even > though I've got only subtype 21 at my shop for the sample. I

Re: SMF119 - Subtype 20 and Subtype 21

2021-12-29 Thread Massimo Biancucci
Jake, I wrote a mix of REXX and Sort to do the task (CSV file as output) even though I've got only subtype 21 at my shop for the sample. I think it's not so difficult to do the same for 20 subtype. It's a long writing for such a thread. If I can use the mail I see I'll be happy to share it with

Re: Using the JOBNAME system symbol in a batch job

2021-12-29 Thread Roger W Suhr
Hi, There are two system symbols that are available (but not listed in the SYMBOLS table and not documented in the same place as the symbol: - Contains the current JOB Name - Contains the current JOB ID (e.g. JOB19002) This has been in place since z/OS 2.3 (maybe earlier, but

Re: Using the JOBNAME system symbol in a batch job

2021-12-29 Thread Paul Gilmartin
On Wed, 29 Dec 2021 14:39:43 +, Seymour J Metz wrote: >"Within JCL, the substitution text for is the name of the job >assigned to the address >space in which the JCL is converted, not the name of the job being processed. >For instance, if >JES2 does the conversion, resolves to JES2." >

Re: Using the JOBNAME system symbol in a batch job

2021-12-29 Thread Seymour J Metz
"Within JCL, the substitution text for is the name of the job assigned to the address space in which the JCL is converted, not the name of the job being processed. For instance, if JES2 does the conversion, resolves to JES2." -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3

Sv: Using the JOBNAME system symbol in a batch job

2021-12-29 Thread Lars Höglund
Could this be the solution? The three types of symbols that can be used for JES2 in-stream substitution are JCL Symbols, JES Symbols and System Symbols: On a JES2 JOBCLASS definition, the field SYSSYM needs to be ALLOW rather than DISALLOW //Lasse -Ursprungligt meddelande- Från: IBM

Using the JOBNAME system symbol in a batch job

2021-12-29 Thread Gadi Ben-Avi
Hi, How do I use the JOBNAME system symbol in a batch job and have it resolve to the JOBNAME? Currently, every time I try, it resolved to JES2. We are running z/OS v2.4. Thanks Gadi -- For IBM-MAIN subscribe / signoff /

Re: SMF119 - Subtype 20 and Subtype 21

2021-12-29 Thread Carmen Vitullo
Peter, the 119 subtype 21, connection termination record I see using a vendor product, EASYSMF has these fields  - I hope the table format does not get wrapped ; Columns *Column* *Description* Time The time the record was written (connection close). System