Re: Real Storage Display

>I discussed this further with Jim Mulder. The z12, where I recently noticed >the 'unassigned' value, introduced 2 GB pages, one of whose consequences is >that LPAR boundaries are rounded up as needed to the nearest 2 GB boundary. If >an image profile specifies any other value, the 'excess' is

Address Spaces writing SMF 30 Subtype 6 Records (was: Address space)

> My notes list these as known Early Address Spaces that create subtype 6's: > > APPC ASCH AUTAM92A AUTAM92B AUTO92S BLSJPRMI CAS9 CSAA > HSAPIPLC HZR IFGEDI INIT JES2 LLA MIAMIMASC > MIMEDI RESOLVER RRS SOFTAUDT TFS TSS VLF >From an

Re: [EXTERNAL] LRECL=255 vs LRECL=259

On 2016-11-15 12:16, Dyck, Lionel B. (TRA) wrote: > I'm in the 255 camp and just tried a simple experiment. > > From TSO issue the Edit command: E T(ABC) CL > > This opens the old editor on dataset t.clist member abc and after adding a > few records and saving I checked the dcb which was

Re: [EXTERNAL] LRECL=255 vs LRECL=259

> On Nov 15, 2016, at 1:16 PM, Dyck, Lionel B. (TRA) wrote: > > I'm in the 255 camp and just tried a simple experiment. > > From TSO issue the Edit command: E T(ABC) CL > > This opens the old editor on dataset t.clist member abc and after adding a > few records and saving

Re: Old MF shops - was - RE: LRECL=255 vs LRECL=259

On 11/15/2016 2:23 PM, Lester, Bob wrote: HI Ed, One more, then I'll go back to lurking Was SPAC related to SPIZ? I seem to remember that SPIZ was Security Pacific (something), but then it gets cloudy... I know of no SPIZ. When I started there, it was Security Pacific

Re: Old MF shops - was - RE: LRECL=255 vs LRECL=259

SPAC was Security Pacific Automation Company, a wholly owned subsidiary of the parent corporation. When U.S. banking was (partially) deregulated in the 80s, SPAC was set up to contain all of IT, including people, hardware, and software. SPAC was then allowed to compete for outside business

Re: Real Storage Display

I discussed this further with Jim Mulder. The z12, where I recently noticed the 'unassigned' value, introduced 2 GB pages, one of whose consequences is that LPAR boundaries are rounded up as needed to the nearest 2 GB boundary. If an image profile specifies any other value, the 'excess' is

Re: Old MF shops - was - RE: LRECL=255 vs LRECL=259

HI Ed, One more, then I'll go back to lurking Was SPAC related to SPIZ? I seem to remember that SPIZ was Security Pacific (something), but then it gets cloudy... Thanks! BobL -Original Message- From: Lester, Bob Sent: Tuesday, November 15, 2016 3:12 PM To: 'IBM Mainframe

Re: Old MF shops - was - RE: LRECL=255 vs LRECL=259

Hi Ed, Dang fat fingers! That should be BofB, or more formally, FNBofB. Thanks! BobL -Original Message- From: Lester, Bob Sent: Tuesday, November 15, 2016 3:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Old MF shops - was - RE: LRECL=255 vs LRECL=259 [ EXTERNAL ] HI Ed, Does

Old MF shops - was - RE: LRECL=255 vs LRECL=259

HI Ed, Does BofA predate BoB? Sorry, I realize it's not Friday yet, but Thanks! BobL -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Jaffe Sent: Tuesday, November 15, 2016 2:46 PM To: IBM-MAIN@LISTSERV.UA.EDU

Re: LRECL=255 vs LRECL=259

On 11/15/2016 11:51 AM, Jesse 1 Robinson wrote: Ed, you and I shared some of that life at Security Pacific Bank. Too late to check on SPAC now, but my recollection from before I met you until today, I have always used/encountered LRECL 255. SPAC is one of the places I remember using

Re: Address space

I think maybe this discussion is for the Early Address Spaces, that among other things, create SMF 30 subtype 6 interval records instead of subtype 3s. My notes list these as known Early Address Spaces that create subtype 6's: APPC ASCH AUTAM92A AUTAM92B AUTO92S BLSJPRMI CAS9

New RFE for SRCHFOR function in ISPF

Cross posting to IBMMAIN and ISPF I always come across these Gems. I was running a SRCHFOR string command in 3.4 and it did not find my string. I then went to the PDS where I knew it was at, and SRCHFOR on the command line found the entry. So I learned that if you have added additional

Re: Splitting a sysplex in two

I like the idea, but would probably not be able to pursue it due to internal issues. Still :-) Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Tuesday, November 15, 2016 3:22 PM To:

AW: Re: Address space

>For RACF, several STCs like 'MASTER SCHEDULER JCL' and subsystem services are >started BEFORE RACF is started, but the SAF interface is already in place at >that stage of IPL. So, I'm not sure what you mean by "BEFORE RACF is started"? Are you talking about the RACF subsystem address space

Re: Splitting a sysplex in two

By far the easiest--if least elegant--method is to copy the entire sysplex and restore whatever you need to make the second one work. It's untidy because you'll have lots of stuff in each plex that's meaningless. For example, production volumes will not be accessible from DEV and vice versa.

Re: LRECL=255 vs LRECL=259

I'll chime in on this. I regularly use LRECL=259 for private PDS's when they need to be VB specifically to get 255 on any line, or to receive JES and other report listings where I don’t know the incoming LRECL a priori. LRECL=255 is probably OK for any of my actual usage, I just prefer 259.

Re: LRECL=255 vs LRECL=259

Ed, you and I shared some of that life at Security Pacific Bank. Too late to check on SPAC now, but my recollection from before I met you until today, I have always used/encountered LRECL 255. I know that limits record data to 251, but is there something special in having 4 extra bytes? It's

Re: LRECL=255 vs LRECL=259

I've never seen LRECL=259 in my life...well, until now! -- Regards, Gord Tomlin Action Software International (a division of Mazda Computer Corporation) Tel: (905) 470-7113, Fax: (905) 470-6507 -- For IBM-MAIN subscribe /

Re: LRECL=255 vs LRECL=259

On Tue, 15 Nov 2016 14:11:55 -0500, Tony Harminc wrote: > >But does it matter much? Concatenating or copying between VB 255 and >VB 259 should "just work" in almost all cases, whereas trying to mix & >match either of those with FB 80 is trouble. > In JCL, I use DISP=NEW,LRECL=222,BLKSIZE=SDB.

Re: LRECL=255 vs LRECL=259

On Tue, 15 Nov 2016 10:59:43 -0800, Ed Jaffe wrote: > >At PSI, we provide the option for customers to allocate our CLIST/EXEC >libraries either RECFM=FB w/LRECL=80 or RECFM=VB w/LRECL=259. One >customer claims the industry-standard for RECFM=VB CLIST/EXEC libraries >is LRECL=255 rather than

Re: [EXTERNAL] LRECL=255 vs LRECL=259

On 11/15/2016 11:16 AM, Dyck, Lionel B. (TRA) wrote: I'm in the 255 camp and just tried a simple experiment. From TSO issue the Edit command: E T(ABC) CL This opens the old editor on dataset t.clist member abc and after adding a few records and saving I checked the dcb which was VB,255,3120

Re: [EXTERNAL] LRECL=255 vs LRECL=259

I'm in the 255 camp and just tried a simple experiment. From TSO issue the Edit command: E T(ABC) CL This opens the old editor on dataset t.clist member abc and after adding a few records and saving I checked the dcb which was VB,255,3120 Not the ideal blksize but the lrecl is what I

Re: LRECL=255 vs LRECL=259

Put me in the 255 camp. I've never seen a 259 LRECL I not sure if I ever got close to using 251/255 anyway, even indenting by two for all Do/End, Select/When, If/Else statements and four or five levels of nesting! :-) Bob -Original Message- From: IBM Mainframe Discussion List

Re: LRECL=255 vs LRECL=259

On 15 November 2016 at 13:59, Ed Jaffe wrote: > Of course, my personal observations and experiences provide nothing more > than anecdotal evidence. Like a man with two watches being unsure of the > time, I am now unsure if LRECL=259 is widespread practice or if I was

Re: LRECL=255 vs LRECL=259

I have only seen fb80 and vb255. Never saw vb259. Dennis Roach, CISSP, PMP AIG IAM Access Administration – Infrastructure | Identity & Access Management 2929 Allen Parkway, America Building, 3rd Floor | Houston, TX 77019 Phone: 713-831-8799 dennis.ro...@aig.com | www.aig.com -Original

LRECL=255 vs LRECL=259

My whole life I have seen variable length CLIST/EXEC libraries allocated as RECFM=VB w/LRECL=259. Clearly, the intent was to allow up to 255-character source lines. At PSI, we provide the option for customers to allocate our CLIST/EXEC libraries either RECFM=FB w/LRECL=80 or RECFM=VB

Re: Splitting a sysplex in two

Two different Sysplexes. Per Allan's Redbook recommendation and reversing the merge, there are these "plexes" to probably split: CATALOGplex, DASDplex, ECSplex, GRSplex, JESplex, HFSplex, HMCplex, HSMplex, OAMplex, SAplex, RACFplex, RMFplex, RMMplex, SMSplex, TCPplex, VTAMplex, WLMplex

AW: Re: Address space

>SDSF no longer uses JES control blocks to gather data - all JES information >comes from JES SSI services and other GUPI services like IAZXJSAB. Thanks. It still is JES data. - Peter Hunkeler -- For IBM-MAIN subscribe /

Re: ADMF?

Correct. And for some reason DB2 folks also refer to one of the DB2 address spaces as the ADMF address space. I forget which one and it has NOTHING to do with Asynchronous Data Mover. :-) Cheers, Martin Sent from my iPad > On 15 Nov 2016, at 16:50, Mark Jacobs - Listserv

Re: Where are PDSE limitations documented?

W dniu 2016-11-15 o 17:48, Paul Gilmartin pisze: On Mon, 14 Nov 2016 13:12:06 -0500, Farley, Peter x23353 wrote: Trying to find where in the Fine Manuals the limitation of PDSE to one volume is documented. For some unknown reason I AssUMed that PDSE had solved the single-volume limitation

Re: ADMF?

ADMF was used to accelerate the movement of pages from expanded storage to real storage. With the demise of expanded storage, it's useless now. Here's the patent information. https://www.google.ch/patents/US5377337 Jesse 1 Robinson November 15, 2016 at 11:42

Re: ADMF?

Google came up with this link which deals with moving data to and from hiperspaces: http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieaa500/oedt.htm -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1

Re: Where are PDSE limitations documented?

On Mon, 14 Nov 2016 13:12:06 -0500, Farley, Peter x23353 wrote: >Trying to find where in the Fine Manuals the limitation of PDSE to one volume >is documented. For some unknown reason I AssUMed that PDSE had solved the >single-volume limitation for libraries and I am being told I am wrong

Re: (External):Re: Splitting a sysplex in two

-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Tuesday, November 15, 2016 7:48 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Splitting a sysplex in two You might also try "merging systems into a sysplex.

ADMF?

I received a question about 'ADMF', which I take to be Asynchronous Data Mover Facility. Someone actually found via Google a couple of IBM Main posts from Ed Finnell and from me (!) referring to turning it on by LPAR. We both mentioned DB2. We both liked ADMF. ;-) Problem is that I cannot now

Re: Splitting a sysplex in two

(This time with content.) In my experience, splitting and merging a sysplex are two very different activities. Merging is by far the more difficult because you likely have resolve name conflicts of all kinds, especially data set names. Are two like DSNs copies of the same data? If not, do you

Re: Address space

Rob Scott wrote: >The OWNER information can be extracted from the JSAB using IAZXJSAB or copied >from the STTROUID field from the extended status JES SSI call. >Note that these fields can be blank for address spaces that are started >SUB=MSTR. >Jobs that start *before* JES can ask for a

Re: Splitting a sysplex in two

Thanks Allan...reviewing it now. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Tuesday, November 15, 2016 10:48 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Splitting a sysplex in two You might also try

Re: Address space

Peter Hunkeler wrote: >>You could review your SYSLOG to see what things are started before your ESM >>started. >IMHO, the ESM (Enterprise Security Manager?) is started before any address >space is built. The ESM is initialized as part of NIP processing. When I (and John McKown) referred to

Re: Where are PDSE limitations documented?

W dniu 2016-11-15 o 16:22, Paul Gilmartin pisze: On 2016-11-15, at 04:17, R.S. wrote: What's the maximum number of cylinders that can be allocated to a PDSE? The number might be enormous nowadays. AFAIK there is no practical limit. So the limit is volume size minus VTOC That means 1TB

Re: Splitting a sysplex in two

You might also try "merging systems into a sysplex. It should be the same checklist, just operated in reverse. Redbook SG24-6818-00 HTH. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, November

Splitting a sysplex in two

I am in the process of planning for the splitting of a single sysplex into one PROD and one DEVL. Does anyone have a good checklist for this? The last time I did this was quite some time ago. I probably have most of the tasks identified, but can no longer find that old documentation I thought

Re: Where are PDSE limitations documented?

On 2016-11-15, at 04:17, R.S. wrote: >> >> What's the maximum number of cylinders that can be allocated to a PDSE? >> The number might be enormous nowadays. > > AFAIK there is no practical limit. So the limit is volume size minus VTOC > That means 1TB nowadays. > BTW: PDSE V1 has "not so big"

Re: Address space

These days SDSF means "System Display and Search Facility" - I believe the change from "Spool" was made many years ago (15+?). SDSF no longer uses JES control blocks to gather data - all JES information comes from JES SSI services and other GUPI services like IAZXJSAB. -Original

Re: Address space

The OWNER information can be extracted from the JSAB using IAZXJSAB or copied from the STTROUID field from the extended status JES SSI call. Note that these fields can be blank for address spaces that are started SUB=MSTR. Jobs that start *before* JES can ask for a JOBID using the "Request

AW: Re: Address space

>You could review your SYSLOG to see what things are started before your ESM >started. IMHO, the ESM (Enterprise Security Manager?) is started before any address space is built. The ESM is initialized as part of NIP processing. At least for RACF, don't misinterpret the non-existence of the

Re: LASTCLPA error with z/OS 2.2

If testing the "feature bits" in CVTOSLVx does not work for some reason, then I refer you to field ECVTPSEQ. ECVTPSEQ DCF'0'Product sequence number. * This field will be changed when any new * version, release, or modification

Re: OS/VS COBOL - FD DCB vs JCL DCB

On Mon, 14 Nov 2016 15:42:18 +, Styles, Andy (SD EP zPlatform) wrote: >Whilst we can fix any failures as we go, questions are being asked whether we >can perform any scanning across programs and JCL and datasets to identify the >impact up front. E-Gen from

Re: Where are PDSE limitations documented?

W dniu 2016-11-15 o 04:45, Paul Gilmartin pisze: On Mon, 14 Nov 2016 13:12:06 -0500, Farley, Peter x23353 wrote: Trying to find where in the Fine Manuals the limitation of PDSE to one volume is documented. For some unknown reason I AssUMed that PDSE had solved the single-volume limitation

Re: Address space

Peter Hunkeler wrote: >Conclusion: SDSF gets the owner information from the JCT or some control block >"underneath" the JCT. And it does this equally for jobs currently executing. >Therefore, the owner is missing for the aforementioned jobs (STCs). True! Where or how does the SDSF gets the

Re: Address space

saurabh khandelwal wrote: >> In our shop, In sdsf I can see many jobs running with owner and some of them >> running without owner. This is WAD. I believe you are referring to STCs started very early in the IPL process, not 'batch jobs'. >> I am unable to find difference in this. Can anybody

Re: KnowledgeCenter access

It started working right after I sent the message. I guess I scared it into working. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Finnell Sent: Tuesday, November 15, 2016 11:42 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re:

Re: KnowledgeCenter access

A good way is to check it here => https://www-947.ibm.com/support/entry/myportal/Current_status I think Knowledge Center falls under "IBM Support Portal" category. ---

Re: Address space

On Mon, Nov 14, 2016 at 10:10 PM, saurabh khandelwal < sourabhkhandelwal...@gmail.com> wrote: > Hello group, > In our shop, In sdsf I can see many jobs running with owner and some of > them running without owner. > > I am unable to find difference in this. Can anybody help me to understand > this

Re: KnowledgeCenter access

As of right now it seems to be working for z/OS 2.1.0. What were you looking for? http://www.ibm.com/support/knowledgecenter/SSAUWB In a message dated 11/15/2016 3:33:07 A.M. Central Standard Time, gad...@malam.com writes: Does anyone else have problems accessing KnowledgeCenter? I

KnowledgeCenter access

Hi, Does anyone else have problems accessing KnowledgeCenter? I keep getting HTTP Service Temporarily Unavailable messages 9:30 GMT 15nov2016 Gadi לתשומת ליבך, בהתאם לנהלי חברת מלם מערכות בע"מ ו/או כל חברת בת ו/או חברה קשורה שלה (להלן : "החברה") וזכויות החתימה בהן, כל הצעה, התחייבות או מצג

Re: IBM SDK for Node.js - z/OS Preview Now Available

Thanks Tim, We get a z13s in April so I might leave it. I'm guessing that some of the instructions generated by the JIT compiler in V8 might be zEC12 and later so re-compiling won't help. On 15/11/2016 2:35 PM, Timothy Sipples wrote: David Crayford wrote: Drat! Looks like we need a new