Re: SYSPLEX distance

Thanks to everyone for their insights and pointers on this matter. It is obviously going to be very complicated to predict what might happen if we increase from our current 0.3km to something like (say) 20km. The IBM Redbook I mentioned suggests an IBM service to analyse some data (presumably

Re: Intel Chip flaw

On Thu, 4 Jan 2018 12:03:11 -0600, Mike Schwab wrote: >On Thu, Jan 4, 2018 at 11:41 AM, Raja Mohan wrote: >> Redhat did confirm in their advisory that it impacts Linux on Z. we may have >> to wait on IBM to confirm if it impacts z/OS, z/VM and z/VSE >> >IBM, if it finds it, will only issue a

Re: catalog doubt

Ya know, I almost replied but read the whole post and realized it was a tongue in cheek statement. ;-D an On: 06 January 2018 12:43, "Beverly Caldwell" wrote: OK OK OK Take a joke can you? Or is that not allowed on this board? I was

Re: Accessing 65536 devices

TDMF does include a logical data mover. When a database is closed it will swap over. During shutdown for an IPL it should get the remaining datasets. If your new dasd allows dynamic growing a volume, you can grow a non-EAV to the maximum EAV volume size, but no bigger. On Sat, Jan 6, 2018 at

Re: Accessing 65536 devices

Using FDRPAS or TDMF to go from smaller volumes to larger volumes will take you only so far. You can move one MOD3 to one MOD9 (or MOD whatever). After that you have to move datasets. I know there is another FDR product that will help move datasets, but even that has limitations. Naturally

Re: VSAM Performance - CPU reduction

On Sat, Jan 6, 2018 at 11:32 AM, Arun Venkatratnam wrote: > Resp: Reading through the entire file by sequential access took 90 CPU > seconds while skip-sequential took nearly 230 CPU seconds. > Doing the skip sequential (read by key) requires accessing the index

Re: catalog doubt

OK OK OK Take a joke can you? Or is that not allowed on this board? I was being somewhat facetious. I was referring to IBM's tendency to surround everything they do with some sort of mystical complexity. On Fri, Jan 5, 2018 at 8:47 PM, Ron hawkins wrote: > Kirk, > >

Re: VSAM Performance - CPU reduction

1. Have you looked at adding STRNO on the VSAM definition or using RLS to provide the records to be instorage? No, STRNO is not provided explicitly in the VSAM file definition.Strobe apparently shows the number of Strings is 48. RLS is also not used. 2. In your JCL for the job, have you coded

Re: VSAM Performance - CPU reduction

DATASET-OWNER-(NULL) CREATION2018.005 RELEASE2 EXPIRATION--.000 SMSDATA STORAGECLASS -SCTEST

Re: VSAM Performance - CPU reduction

Sometimes I find Strobe reports misleading when reviewing them They do a great job in showing how the process is working. But performance analysis takes a lot of experience to be able to use them well. QSAM is Queued Sequential Access Method - it is what is used to read your data and return

Re: AW: Re: Intel Chip flaw

With the Legacy Database Server z/Db2I.19? Code named 'zippity two da'. In a message dated 1/6/2018 3:16:19 AM Central Standard Time, p...@gmx.ch writes:   I imagine some clever marketing guy at IBM: "The *first* release of the all new IBM flagship operating system coming out in *2019* will

AW: Re: Intel Chip flaw

>LOL, I meant z/OS 1.9. I don't believe a z/OS 1.19 will ever see the light of >day. LOL, why not? Because IBM has logic behind numbering product versions and release? I remember: - OS/390 V1.3. Next release was OS/390 V2.4. - IBM z900, followed by IBM z990 followed by IBM z9. I imagine