Re: IBM BLSR subsystem

2022-05-18 Thread Jim Mulder
BLSR was initially developed by Washinton System Center as an assembler language sample program to go along with a book they were writing about using the Subsystem Interface. At the time, IBM was desperately looking for "ESA Exclusives" in order to sell 3090 machines vs the PCM

Re: Mark your calendars for July 10, 2022 - CustomPac intended removal date

2022-05-18 Thread Brian Westerman
I understand, but in this case the z13s is a supported processor for z/OS 2.5, but is almost completely incapable of running z/OSMF. It can run z/OSMF, but the response time is unacceptable. We finally got IBM to compare z/OSMF on a z13s without any zIIP and they came back to say that the one

Re: [EXTERNAL] Re: IBM BLSR subsystem

2022-05-18 Thread Dave Barry
IIRC, Batch LSR was developed at IBM by the BCP team; SMB was later developed by the DFdfp team. SMB is not BLSR under-the-covers, but it offers the same advantages. SMB is the more modern solution. It has worked wonders at my shop. Just mind your REGION size. If you haven't converted some

Re: Mark your calendars for July 10, 2022 - CustomPac intended removal date

2022-05-18 Thread Lennie Dymoke-Bradshaw
Purchase of an Intel XEON system to run a Linux system with zPDT could be used purely to run Z/OSMF. Would that be good enough? I think that might be cheaper than real Z upgrades, but I have not done any arithmetic on software costs. z/OS volume images could then be transferred using FTP when

Re: [EXTERNAL] Re: Mark your calendars for July 10, 2022 - CustomPac intended removal date

2022-05-18 Thread Pommier, Rex
Yes IBM allows for soft capping but that doesn't take care of the problem in 2 ways. First the soft cap only reduces a portion of the software license fees. Second, you still have the larger hardware costs of buying the bigger machine just to kneecap it. Rex -Original Message-

Re: Mark your calendars for July 10, 2022 - CustomPac intended removal date

2022-05-18 Thread Andrew Rowley
On 18/05/2022 3:53 pm, Timothy Sipples wrote: So over roughly 25 years it’s been about 3.5 to 98 PCIs as the minimum available CP configuration, or about a 28X increase. I did say "a small" system in the 1990s, not the smallest available. But your 28X illustrates the point. Over the same

Re: How to keep the response from HSENDCMD batch

2022-05-18 Thread Nobuhiko Furuya
Hello Mike, Thank you for your comment. But QUERY command doesn't support ODS parameter and HSENDCMD itself has no option. I have found the solution provided in HSM.SAMPLE.TOOL(QUERYSET) which uses extended console support. Best regards, Nobuhiko Furuya(古谷信彦) V-SOL Inc.

Re: How to keep the response from HSENDCMD batch

2022-05-18 Thread Mike Schwab
HSEND Q CDS ODS(my.output.file) On Wed, May 18, 2022 at 6:08 AM Nobuhiko Furuya wrote: > > Hello all, > > Could you give me your advice ? > > We are converting CA-Disk to DFSMShsm. > In this situation, we are to use HSENDCMD in TSO batch as follows. > > //STEP1EXEC PGM=IKJEFT01 > //SYSPRINT

Re: Mark your calendars for July 10, 2022 - CustomPac intended removal date

2022-05-18 Thread Mike Schwab
Doesn't IBM also allow software capping to a lower capacity than the slowest uniprocessor through the operating system? On Wed, May 18, 2022 at 5:54 AM Timothy Sipples wrote: > > Andrew Rowley wrote: > >It would benefit customers, software vendors and IBM if IBM could get > >these small systems

How to keep the response from HSENDCMD batch

2022-05-18 Thread Nobuhiko Furuya
Hello all, Could you give me your advice ? We are converting CA-Disk to DFSMShsm. In this situation, we are to use HSENDCMD in TSO batch as follows. //STEP1    EXEC PGM=IKJEFT01 //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN  DD *  HSENDCMD WAIT SETSYS SSMSTART(0005 0100)  HSENDCMD