Re: Questions about IARST64
Steve Comstock wrote: Can anyone enlighten me about the function / purpose of IARST64? Not that I've used it, but there certainly are several references to cells in the IARST64 doc and no general description of use in the normal documentation. I did find the following in zOS 1.10 Implementation Redbook, which has a bit more information on the subject IARST64 This service enables the caller to request private or common storage in sizes from 1 byte to 64 K. IARST64 is equivalent to GETMAIN and FREEMAIN, or STORAGE OBTAIN or RELEASE for 64-bit storage, or GET and FREE 1 to 64K bytes of private or common. It also seems to confirm the cellpool suspicion: IARST64 and IARCP64 service characteristics Both IARST64 and IARCP64 services have the following common characteristics: Pool extents are all 1 MB in size. GET and FREE requests are branch entered. They run with just registers and only program call when a new pool or new extent is needed. They use a register interface and have no parameter list. New pools and extents are implemented in a way that no actual lock or latch is taken when the function is running. At the last moment, when everything is settled and it is just required to insert the newly defined pool or extent into the existing schemes, a Compare-and-Swap is issued. If it fails, the loser has to clean up and reiterate its process, making another try to acquire the required pool or extent. It is considered that such a “losing” situation should rarely be happening. IARST64 pools cannot be deleted. EOT will clean up a private pool. Common pools are kept forever. Other characteristics that are shared in common by IARCP64 and IARST64 are: No contraction of pools is currently supported in z/OS V1R10. Boundaries are forced to quadword, cache line, or page, depending on cell size. Trailers are used when they fit, to detect overruns. Double free detected and rejected with abend. Date:Fri, 21 Sep 2012 10:06:31 -0600 From:Steve Comstock st...@trainersfriend.com Subject: Questions about IARST64 Well, I'm a bit confused by the docs on this service. In the Assembler Services Reference, the write up begins: Use IARST64 to request 64-bit Storage Services. so I at first assumed this has nothing to do with cell pools but is an alternative to IARV64 (no guard area, etc.) But just a few lines deeper I see: Note: There is diagnostic support for 64 bit cell pools, created by IARST64... so that sounds like cell pools. A few pages later I find this gem: For storage that is larger than what IARCP64 supports, consider using IARCP64 or IARV64 GETSTOR or GETCOMMON. Huh? If IARCP64 doesn't meet your needs use IARCP64? The IARST64 service is not referenced at all in the Assembler Services Guide doc. Can anyone enlighten me about the function / purpose of IARST64? Thanks. -- Kind regards, -Steve Comstock The Trainer's Friend, Inc. * -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: MQ monitoring
Ron I recently wrote a white paper on that. You can find the abstract and you can request it here http://www.epvtech.com/resources/newsletter.html If you have any problem please let me know. Best regards Fabio At 19:38 24/09/2012, you wrote: Antyone out here monitor MQ..and what are you looking for/at?? SMF rec's...fields to report on?? -- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed above. If you are not the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on the contents of the E-mail or attached files is strictly prohibited. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN + + Fabio Massimo Ottaviani + EPV Technologies Technical Director + Skype: fabio.massimo.ottaviani + Mobile: +393406168088 + + IT Cost under Control + www.epvtech.com + P Please consider the environment - do you really need to print this email? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Why File transfer through TSO IND$FILE is slower than TCP/IP FTP ?
Chris Mason wrote: 'Maximizing the SNA RU size reduces end-to-end acknowledgments at the 3270 application level.' This is just common sense. Thanks. Agreed. In order to illustrate the point I'm assuming you have to send 10K of data and the flow control parameters are such that each unit of data sent must be acknowledged - just to keep it simple. - If you send 10 units of 1K you are obliged to wait while 10 acknowledgements are returned. - If you send 1 unit of 10K you are obliged to wait while 1 acknowledgement is returned. QED! Thanks for this useful explanation. I am a great advocate of regular monitoring of buffer pool patterns of use. First of all I advise that dynamic buffering should be used. Then I advise to guard against too much or too little. This is what my VTAM and TCP/IP guys and gals doing. When VTAM is doing a GETMAIN for more buffers, all using VTAM need to wait for that GETMAIN to complete. Not a problem, but observable especially when all and everyone is logging on in the morning after the previous night IPL. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
RMF Spreadsheet Reporter
Dear Group, I am looking for Sysplex resources (CF Structure) utilization report and for doing this I am trying to configure RMF Spread sheet reporter. I tried following RMF user guide to configure but it didnt help me much as I am new with this product. Till now I have filled my Mainframe host detail, for which I want to get detail.Could someone please help shed some light on the above . Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Return Address from IKJPARS ?
So, as has been asked, what were the regs/PSW at the time of the PIC 6? It seems likely that the OP's code did not restore registers as the interface required it to do (particularly GR 2). If you return via reg 14 and reg 14 points to CVTBSM2, then the next thing that will be issued is the instruction at CVTBSM which (not surprisingly) is BSM 0,2. If GR 2 has not been restored, that may go off anywhere and could possibly get a PIC 6, although I'm not sure if that could happen on the BSM target itself or might be the result of some subsequent branch relying on the value in some register. Assuming that you know where to return, and not using reg 14 when reg 14 is documented as containing the return address, is dangerous at best. FWIW, returning to the normal reg 14 for a new RB is less efficient, not more efficient, than issuing SVC 3. Upon entry to a PRB's program, reg14 points to an SVC 3, so it is only one instruction less efficient), but it would be silly to issue SVC 3 if you are not in full control of the environment because otherwise, as Binyamin pointed out, you could be terminating your caller too. It is only when a RB is exiting that SVC 3 is appropriate. Returning by reg 14 is surely the right thing to do in general Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: RMF Spreadsheet Reporter
There is not much to configure here. It is pretty much canned. 1) Download the current version from http://www-03.ibm.com/systems/z/os/zos/features/rmf/ 2) Run an RMF Post processor report and create overview records. 3) Download records and feed to Spreadsheet Reporter. Additional information here: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ERBZUGB0/CCONTENTS?SHELF=erbzbkb0DN=SC33-7990-19DT=20110615130737 Chapter 7 topic 7.2 (watch the wrap) HTH, snip I am looking for Sysplex resources (CF Structure) utilization report and for doing this I am trying to configure RMF Spread sheet reporter. I tried following RMF user guide to configure but it didnt help me much as I am new with this product. Till now I have filled my Mainframe host detail, for which I want to get detail.Could someone please help shed some light on the above . /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Official current definition of MVS
In CAE1XxDH+r00Q87x75=xz7z7kfdkpdq2w53t6xz_b7kkrxbx...@mail.gmail.com, on 09/24/2012 at 09:39 PM, John Gilmore jwgli...@gmail.com said: and he has here committed a [vulgar sense] oxymoron. Actually a typo; that should have been It started as a feature of OS/360 MVT. -- Shmuel (Seymour J.) Metz, SysProg and JOAT Atid/2http://patriot.net/~shmuel We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM is a not deleting expired datasets
A couple of things to check (not mentioned so far): May be HSM is trying delete these datasets, or at least some of them, but is being unsuccessful for some reason. Check the HSM activity logs for possible errors. Also remember that HSM will only delete expired datasets if HSM is managing the particular volume(s). For non-SMS volumes (ADDVOLed with AUTOMIG turned on) and for SMS volumes the storage group containing the volumes must be defined with AM=Y. Richard Marchant -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan Sent: 24 September 2012 05:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFSMSHSM is a not deleting expired datasets From DFHSM Storage Adminstration. EXPIREDDATASETS: Specifying whether to scratch data sets with expired expiration dates Explanation: EXPIREDDATASETS(SCRATCH | NOSCRATCH) is an optional parameter specifying whether or not DFSMShsm should scratch data sets having explicit expiration dates when the date has passed (data set has expired). SMS-managed data sets not having explicit expiration dates are expired when they have met their management class expiration criteria. Note: Explicit expiration dates can be set by JCL, utility parameters, Data Class Expiration parameters, or Data Class Retention parameters. The explicit expiration date for a data set can be found in the data set's VTOC entry. SCRATCH specifies that DFSMShsm scratch data sets that have an expired expiration date when it performs space management and migration cleanup. NOSCRATCH specifies that DFSMShsm ignore the expiration date. DFSMShsm processes the data set as if the expiration date has not been reached. SMS relationship: Parameter applies in some instances to SMS-managed DASD volumes or data sets. SETSYS defaults: None. DFSMShsm defaults: If you do not specify this parameter on any SETSYS command, the DFSMShsm default is not to scratch the expired data sets. Typically, ML2 datasets and BACKUP datasets reside on tape. If the datasets are not expired, no tapes will be released except by recycle or manual deletion. Once all of the datasets on a particular tape are released (via RECYCLE, HDEL, or HBDEL), DFHSM will notify the EDM to expire the tape, and return it to the scratch pool. Caveat. It is possible to set up DFHSM tape pooling, in which case, the tape will be returned to the DFHSM pool, instead of the scratch pool and the EDM will not be invoked. snip I guess I am showing my lack of experience on this topic, but what does EXPIREDDATASETS setting have to do with whether or not the tapes are being released or not? Am I misunderstanding the book? From the HSM administrators guide: During automatic primary space management, the example scratches expired data sets that have valid explicit expiration dates in the data set's VTOC entry. The EXPIREDDATASETS parameter of the SETSYS command specifies the SCRATCH subparameter indicating for DFSMShsm to scratch any data set that has passed the expiration date. _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 /snip snip -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan snip Sounds like a good setup, the EDM reference will scratch the tape when DFHSM says it is done with it. However, since you are not expiring datasets, very few, if any tapes are being released. Of course, since you work for the legal system, they might not want things scratched Check with the powers that be before proceeding... IMO, change EXPIREDDATASETS to SCRATCH and bite the bullet. The first secondary space management that runs will do a lot of work. /snip snip I have HSM set as an External Data Manager in CA1 (EDM=HSM,PGM=ARCCTL in CTOEDM00). My SYS1.PARMLIB(ARCCMD00) specifies EXPIREDDATASETS(NOSCRATCH). For those with CA1 and EDM specified, how is yours set up? What reason would a shop have to specify NOSCRATCH? Can you tell I haven't supported HSM before? :-) (Always been in places with FDR, or had a separate team doing storage stuff for the past 20 years or so.) /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: 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: RMF Spreadsheet Reporter
If you do an internet search for RMF SPREADSHEET REPORTER you should find many links that can assist you Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jake anderson Sent: Tuesday, September 25, 2012 4:42 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: RMF Spreadsheet Reporter Dear Group, I am looking for Sysplex resources (CF Structure) utilization report and for doing this I am trying to configure RMF Spread sheet reporter. I tried following RMF user guide to configure but it didnt help me much as I am new with this product. Till now I have filled my Mainframe host detail, for which I want to get detail.Could someone please help shed some light on the above . Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM is a not deleting expired datasets
Thanks to all respondents. A big thanks to Richard for the suggestions. At this point, my management is concerned about changing anything because there must be a reason it's set this way. Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 steve_con...@ao.uscourts.gov From: Richard Marchant richard.march...@shoden.co.za To: IBM-MAIN@LISTSERV.UA.EDU Date: 09/25/2012 09:18 AM Subject:Re: DFSMSHSM is a not deleting expired datasets Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU A couple of things to check (not mentioned so far): May be HSM is trying delete these datasets, or at least some of them, but is being unsuccessful for some reason. Check the HSM activity logs for possible errors. Also remember that HSM will only delete expired datasets if HSM is managing the particular volume(s). For non-SMS volumes (ADDVOLed with AUTOMIG turned on) and for SMS volumes the storage group containing the volumes must be defined with AM=Y. Richard Marchant -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan Sent: 24 September 2012 05:02 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFSMSHSM is a not deleting expired datasets From DFHSM Storage Adminstration. EXPIREDDATASETS: Specifying whether to scratch data sets with expired expiration dates Explanation: EXPIREDDATASETS(SCRATCH | NOSCRATCH) is an optional parameter specifying whether or not DFSMShsm should scratch data sets having explicit expiration dates when the date has passed (data set has expired). SMS-managed data sets not having explicit expiration dates are expired when they have met their management class expiration criteria. Note: Explicit expiration dates can be set by JCL, utility parameters, Data Class Expiration parameters, or Data Class Retention parameters. The explicit expiration date for a data set can be found in the data set's VTOC entry. SCRATCH specifies that DFSMShsm scratch data sets that have an expired expiration date when it performs space management and migration cleanup. NOSCRATCH specifies that DFSMShsm ignore the expiration date. DFSMShsm processes the data set as if the expiration date has not been reached. SMS relationship: Parameter applies in some instances to SMS-managed DASD volumes or data sets. SETSYS defaults: None. DFSMShsm defaults: If you do not specify this parameter on any SETSYS command, the DFSMShsm default is not to scratch the expired data sets. Typically, ML2 datasets and BACKUP datasets reside on tape. If the datasets are not expired, no tapes will be released except by recycle or manual deletion. Once all of the datasets on a particular tape are released (via RECYCLE, HDEL, or HBDEL), DFHSM will notify the EDM to expire the tape, and return it to the scratch pool. Caveat. It is possible to set up DFHSM tape pooling, in which case, the tape will be returned to the DFHSM pool, instead of the scratch pool and the EDM will not be invoked. snip I guess I am showing my lack of experience on this topic, but what does EXPIREDDATASETS setting have to do with whether or not the tapes are being released or not? Am I misunderstanding the book? From the HSM administrators guide: During automatic primary space management, the example scratches expired data sets that have valid explicit expiration dates in the data set's VTOC entry. The EXPIREDDATASETS parameter of the SETSYS command specifies the SCRATCH subparameter indicating for DFSMShsm to scratch any data set that has passed the expiration date. _ Dave Jousma Assistant Vice President, Mainframe Services david.jou...@53.com 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 /snip snip -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Staller, Allan snip Sounds like a good setup, the EDM reference will scratch the tape when DFHSM says it is done with it. However, since you are not expiring datasets, very few, if any tapes are being released. Of course, since you work for the legal system, they might not want things scratched Check with the powers that be before proceeding... IMO, change EXPIREDDATASETS to SCRATCH and bite the bullet. The first secondary space management that runs will do a lot of work. /snip snip I have HSM set as an External Data Manager in CA1 (EDM=HSM,PGM=ARCCTL in CTOEDM00). My SYS1.PARMLIB(ARCCMD00) specifies EXPIREDDATASETS(NOSCRATCH). For those with CA1 and EDM specified, how is yours set up? What reason would a shop have to specify NOSCRATCH? Can you tell I haven't supported HSM before? :-) (Always been in places with FDR, or had a separate team doing storage stuff for the past 20 years or so.) /snip -- For
Re: RMF Spreadsheet Reporter
I forgot, If you include SHARE at the front SHARE RMF SPREADSHEET REPORTER it should be some of the Share Presentations to the top. They should be very helpful. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler If you do an internet search for RMF SPREADSHEET REPORTER you should find many links that can assist you Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jake anderson Sent: Tuesday, September 25, 2012 4:42 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: RMF Spreadsheet Reporter Dear Group, I am looking for Sysplex resources (CF Structure) utilization report and for doing this I am trying to configure RMF Spread sheet reporter. I tried following RMF user guide to configure but it didnt help me much as I am new with this product. Till now I have filled my Mainframe host detail, for which I want to get detail.Could someone please help shed some light on the above . Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM is a not deleting expired datasets
Steve Conway wrote: At this point, my management is concerned about changing anything because there must be a reason it's set this way. Probably yes. Perhaps the (previous) owners wanted to keep them due to some policy/rule. Is it possible for you to list them by 'last used' date and then backup/dump them before going to have HSM deal with them 21000 datasets? Of course, I'm aware that such step could change the expired status of those datasets, but I'm just wondering... Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM is a not deleting expired datasets
Interesting thought, Elardus, but I'm just going to leave it alone for now. It's not like I don't have anything to keep me busy. :-) Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 steve_con...@ao.uscourts.gov From: Elardus Engelbrecht elardus.engelbre...@sita.co.za To: IBM-MAIN@LISTSERV.UA.EDU Date: 09/25/2012 10:06 AM Subject:Re: DFSMSHSM is a not deleting expired datasets Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU Steve Conway wrote: At this point, my management is concerned about changing anything because there must be a reason it's set this way. Probably yes. Perhaps the (previous) owners wanted to keep them due to some policy/rule. Is it possible for you to list them by 'last used' date and then backup/dump them before going to have HSM deal with them 21000 datasets? Of course, I'm aware that such step could change the expired status of those datasets, but I'm just wondering... Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: 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: Official current definition of MVS
In rereading that portion of my post that Shmuel quoted it has occurred to me that it could be read as characterizing his 'typo' as vulgar. That was not at all my intent. In classical rhetoric oxymora were and are figures of speech that make use of an apparent but in the event not substantive contradiction. In current subliterate use 'oxymoron' has become a fancy synonym for 'contradiction'. Alexius Meinong's round square is thus converted, not very helpfully, into an instance of an oxymoron. --jg -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFSMSHSM is a not deleting expired datasets
Are you doing the release expirebv command on some schedule? font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMP/E RECEIVE FROMNETWORK vs. fchattr()
I've long wished that: o GIMZIP could build its product from non-catalogued data sets, perhaps unloaded RELFILEs on tape, passed temporary DSNs, or MCS/JCLIN in PDS members or UNIX files. I'd like to be able to transform an SMP/E installation tape to a GIMZIP archive without copying the parts to transitory catalogued data sets. o The producer's local data set names could be redacted from the GIMPAF file in order not to expose data set prefixes (which may be TSO user IDs) to customers. Both these desiderata could be addressed if GIMZIP supported using DDNAMEs to identify its source data and used the data set names from its control file in the generated GIMPAF. I understand your desires. BTW, GIMZIP does support input UNIX files. Kurt Quackenbush -- IBM, SMP/E Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Questions about IARST64
I should have thought that Peter Relson's post had clarified these issues more than adequately. IARCP64 makes above-the-bar storage available in chunks, one mibibyte at a time; and requesters must submanage this storage themselves. IARST64 submanages such chunks for you. Does the 'CP' in 'IARCP64' stand fror 'Cell Pool'? Does the 'ST' in 'IARST64' stand for 'STorage'? Maybe. What indeed is a cell pool? We all know what a buffer pool is; and perhaps its outstanding characteristic is that, since the units it manages are equal in size and thus interchangeable, it can be managed as a stack. This is clearly not the case with these 'cell pools'. They are heap-like rather than stack-like, and their name was thus ill-chosen. John Gilmore, Ashland, Ma 01721 - USA On 9/25/12, David Stokes sto...@interchip.de wrote: Steve Comstock wrote: Can anyone enlighten me about the function / purpose of IARST64? Not that I've used it, but there certainly are several references to cells in the IARST64 doc and no general description of use in the normal documentation. I did find the following in zOS 1.10 Implementation Redbook, which has a bit more information on the subject IARST64 This service enables the caller to request private or common storage in sizes from 1 byte to 64 K. IARST64 is equivalent to GETMAIN and FREEMAIN, or STORAGE OBTAIN or RELEASE for 64-bit storage, or GET and FREE 1 to 64K bytes of private or common. It also seems to confirm the cellpool suspicion: IARST64 and IARCP64 service characteristics Both IARST64 and IARCP64 services have the following common characteristics: Pool extents are all 1 MB in size. GET and FREE requests are branch entered. They run with just registers and only program call when a new pool or new extent is needed. They use a register interface and have no parameter list. New pools and extents are implemented in a way that no actual lock or latch is taken when the function is running. At the last moment, when everything is settled and it is just required to insert the newly defined pool or extent into the existing schemes, a Compare-and-Swap is issued. If it fails, the loser has to clean up and reiterate its process, making another try to acquire the required pool or extent. It is considered that such a “losing” situation should rarely be happening. IARST64 pools cannot be deleted. EOT will clean up a private pool. Common pools are kept forever. Other characteristics that are shared in common by IARCP64 and IARST64 are: No contraction of pools is currently supported in z/OS V1R10. Boundaries are forced to quadword, cache line, or page, depending on cell size. Trailers are used when they fit, to detect overruns. Double free detected and rejected with abend. Date:Fri, 21 Sep 2012 10:06:31 -0600 From:Steve Comstock st...@trainersfriend.com Subject: Questions about IARST64 Well, I'm a bit confused by the docs on this service. In the Assembler Services Reference, the write up begins: Use IARST64 to request 64-bit Storage Services. so I at first assumed this has nothing to do with cell pools but is an alternative to IARV64 (no guard area, etc.) But just a few lines deeper I see: Note: There is diagnostic support for 64 bit cell pools, created by IARST64... so that sounds like cell pools. A few pages later I find this gem: For storage that is larger than what IARCP64 supports, consider using IARCP64 or IARV64 GETSTOR or GETCOMMON. Huh? If IARCP64 doesn't meet your needs use IARCP64? The IARST64 service is not referenced at all in the Assembler Services Guide doc. Can anyone enlighten me about the function / purpose of IARST64? Thanks. -- Kind regards, -Steve Comstock The Trainer's Friend, Inc. * -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: 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: DFSMSHSM is a not deleting expired datasets
EXPIREBV will never touch an ML0/ML1/ML2 dataset. It deals only with backup copies of datasets. :: -Original Message- :: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :: Behalf Of Michael Wickman :: Sent: Tuesday, September 25, 2012 7:57 AM :: To: IBM-MAIN@LISTSERV.UA.EDU :: Subject: Re: DFSMSHSM is a not deleting expired datasets :: :: Are you doing the release expirebv command on some schedule? :: :: :: :: :: :: :: font size=1 :: div style='border:none;border-bottom:double windowtext :: 2.25pt;padding:0in 0in 1.0pt 0in' :: /div :: This email is intended to be reviewed by only the intended recipient :: and may contain information that is privileged and/or confidential. :: If you are not the intended recipient, you are hereby notified that :: any review, use, dissemination, disclosure or copying of this email :: and its attachments, if any, is strictly prohibited. If you have :: received this email in error, please immediately notify the sender by :: return email and delete this email from your system. :: /font :: :: -- :: For IBM-MAIN subscribe / signoff / archive access instructions, :: send email to lists...@listserv.ua.edu with the message: 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: ADR405E (041)-DYNA (02), DYNAMIC ALLOCATION OF VOLUME FB8ACC FAILED. ERROR CODE 0218. INFORMATION CODE 0000.
Good Day All, I haven't received any replies to my post. Perhaps I have the problem re-occuring again with lost posts. From: willie bunter williebun...@yahoo.com To: IBM-MAIN@LISTSERV.UA.EDU Sent: Monday, September 24, 2012 12:29:22 PM Subject: ADR405E (041)-DYNA (02), DYNAMIC ALLOCATION OF VOLUME FB8ACC FAILED. ERROR CODE 0218. INFORMATION CODE . Good Day All, I encountered a problem while attempting to perform a FLASHCOPY of a volume: ADR405E (041)-DYNA (02), DYNAMIC ALLOCATION OF VOLUME FB8ACC FAILED. ERROR CODE 0218. INFORMATION CODE . The dynamic allocation error occurred on the ouptut or target volume. A colleague gave me the following link posted on IBM's site : http://www-01.ibm.com/support/docview.wss?uid=isg3S1000603 The explanation is quite straight forward. I would like to try their suggestion : The WORKVOL or WORKUNIT parms on the EXEC statement for ADRDSSU can be used to point allocation to SPECIFIC volumes/units. However I am not sure as to how to go about coding this parm in the EXEC statement. Could anybody suggest how to do it? Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: 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: DFSMSHSM is a not deleting expired datasets
Hi, Michael. Not that I know of. Where would that commonly be specified? Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 steve_con...@ao.uscourts.gov From: Michael Wickman mwick...@waddell.com To: IBM-MAIN@LISTSERV.UA.EDU Date: 09/25/2012 11:06 AM Subject:Re: DFSMSHSM is a not deleting expired datasets Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU Are you doing the release expirebv command on some schedule? font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: 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: Questions about IARST64
IARCP64 makes above-the-bar storage available in chunks, one mibibyte at a time; and requesters must submanage this storage themselves. IARST64 submanages such chunks for you. IARV64 makes above-the-bar storage available in chunks, one mibibyte at a time; and requesters must submanage this storage themselves. IARCP64 makes above-the-bar storage available in chunks, one mibibyte at a time, and submanages this storage as pool of cells of the size requested on IAR64CP REQUEST=BUILD. Storage within any such one mibibyte chuck is used only by callers of IARCP64 using the same INPUT_CPID. IARST64 makes above-the-bar storage available in chunks, one mibibyte at a time, and submanages this storage as pool of cells of the requested size. Storage within such a one mibibyte chunk can be used by any caller of IARST64 whose requested size and storage attributes match the cell size and storage attributes being used for that one mibibyte chunk. Does the 'CP' in 'IARCP64' stand fror 'Cell Pool'? Yes: BROWSESYS1.MACLIB(IARCP64) Line Co Command === Scroll * Top of Data */ START OF SPECIFICATIONS *** * * *01* MACRO NAME: IARCP64 -02/13/09-0 * * *01* DESCRIPTIVE NAME: 64-bit Cell pool services Does the 'ST' in 'IARST64' stand for 'STorage'? Maybe. Yes: BROWSESYS1.MACLIB(IARST64) Line Col Command === Scroll = * Top of Data * */ START OF SPECIFICATIONS * * * * *01* MACRO NAME: IARST64 -05/28/10-0 * * * * * *01* DESCRIPTIVE NAME: 64-bit Storage services * * * What indeed is a cell pool? We all know what a buffer pool is; and perhaps its outstanding characteristic is that, since the units it manages are equal in size and thus interchangeable, it can be managed as a stack. This is clearly not the case with these 'cell pools'. They are heap-like rather than stack-like, and their name was thus ill-chosen. Call it what you like. IARCP64 and IARST64 are implemented based on the algorithms described here: http://www.google.com/patents/US20090100243 Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Questions about IARST64
John Gilmore wrote I should have thought that Peter Relson's post had clarified these issues more than adequately. Ah. As enjoyable as always to hear your opinion, Mr. Gilmore, although I couldn't myself find very much in Peter Relson's posting that seemed especially helpful (not that I was looking for help myself). Nor in yours, for that matter. But be that is it may, I can't see any rational reason for dismissing additional information when it is available. I was going to add a bit more here, and some suppositions, but Jim Mulder has said most of it, and confirmed my suspicions, which is nice. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Questions about IARST64
The patent that Jim Mulder cited: http://www.google.com/patents/US20090100243 contains very useful information. It begins with the text: begin extract A virtual storage technique is provided to manage a cell pool or a set of cell pools which can be used to satisfy variable-size storage requests. The algorithm uses no locks and relies on an atomic compare-and-swap instruction to serialize updates to the fields that can be simultaneously requested by multiple threads or processes. A free chain is used to manage cells which have already been obtained and freed, while there is an active extent that is used to hand out cells which have not previously been obtained. The algorithm is based on all cell pool extents being the same size, which allows the control information for the extent to be easily located on the extent boundary (e.g. at a 1 MB boundary). end extract The rationale for the use of the term 'pool' is now clear. It is that, while the cells allocated within a cell-pool extent may vary in size, cell-pool extents themselves are fixed--in fact 1 mibibyte--in size. This is legitimate developer-perspective terminology. It is less congenial from a user's perspective, but now that I understand its etiology I can live with it happily (which is just as well since I must do so whether happily or not). John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SMP/E RECEIVE FROMNETWORK vs. fchattr()
On Tue, 25 Sep 2012 11:19:38 -0400, Kurt Quackenbush ku...@us.ibm.com wrote: I've long wished that: o GIMZIP could build its product from non-catalogued data sets, perhaps unloaded RELFILEs on tape, passed temporary DSNs, or MCS/JCLIN in PDS members or UNIX files. I'd like to be able to transform an SMP/E installation tape to a GIMZIP archive without copying the parts to transitory catalogued data sets. o The producer's local data set names could be redacted from the GIMPAF file in order not to expose data set prefixes (which may be TSO user IDs) to customers. If the archid was used to store the archives in the package, and the name tag in the GIMPAF.XML was of the form SMPRELF/archid.pax.Z, Would that meet redaction requirements? If archid=FMID.Fnn, for example, then name would be SMPRELF/FMID.Fnn.pax.Z (even name=SMPRELF/RFDSNPFX.FMID.Fnn.pax.Z would be passable) Not to discourage DDNAME support, mind you... Both these desiderata could be addressed if GIMZIP supported using DDNAMEs to identify its source data and used the data set names from its control file in the generated GIMPAF. I understand your desires. BTW, GIMZIP does support input UNIX files. LLB, learned something new today. Absolute pathnames only, though...similar redaction requirements may apply. Regards, Art Gutowski Compuware -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Questions about IARST64
Nitpick on an error that is getting repeated: 2**20 Bytes = MiB is mebibytes (not mibibytes), as it is derived from mega binary. I hope the erroneous form is not a quote from a some manual. Reference: http://physics.nist.gov/cuu/Units/binary.html JC Ewing On 09/25/2012 01:26 PM, Jim Mulder wrote: IARCP64 makes above-the-bar storage available in chunks, one mibibyte at a time; and requesters must submanage this storage themselves. IARST64 submanages such chunks for you. IARV64 makes above-the-bar storage available in chunks, one mibibyte at a time; and requesters must submanage this storage themselves. IARCP64 makes above-the-bar storage available in chunks, one mibibyte at a time, and submanages this storage as pool of cells of the size requested on IAR64CP REQUEST=BUILD. Storage within any such one mibibyte chuck is used only by callers of IARCP64 using the same INPUT_CPID. IARST64 makes above-the-bar storage available in chunks, one mibibyte at a time, and submanages this storage as pool of cells of the requested size. Storage within such a one mibibyte chunk can be used by any caller of IARST64 whose requested size and storage attributes match the cell size and storage attributes being used for that one mibibyte chunk. Does the 'CP' in 'IARCP64' stand fror 'Cell Pool'? Yes: BROWSESYS1.MACLIB(IARCP64) Line Co Command === Scroll * Top of Data */ START OF SPECIFICATIONS *** * * *01* MACRO NAME: IARCP64 -02/13/09-0 * * *01* DESCRIPTIVE NAME: 64-bit Cell pool services Does the 'ST' in 'IARST64' stand for 'STorage'? Maybe. Yes: BROWSESYS1.MACLIB(IARST64) Line Col Command === Scroll = * Top of Data * */ START OF SPECIFICATIONS * * * * *01* MACRO NAME: IARST64 -05/28/10-0 * * * * * *01* DESCRIPTIVE NAME: 64-bit Storage services * * * What indeed is a cell pool? We all know what a buffer pool is; and perhaps its outstanding characteristic is that, since the units it manages are equal in size and thus interchangeable, it can be managed as a stack. This is clearly not the case with these 'cell pools'. They are heap-like rather than stack-like, and their name was thus ill-chosen. Call it what you like. IARCP64 and IARST64 are implemented based on the algorithms described here: http://www.google.com/patents/US20090100243 Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ... -- Joel C. Ewing,Bentonville, AR jcew...@acm.org -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GIM39001E in SMP/E RECEIVE FROMNTS
On Mon, 24 Sep 2012 09:18:09 -0400, Kurt Quackenbush ku...@us.ibm.com wrote: Presumably the MCS for each SYSMOD is in a unique data set? If so, then yes, the order in which the archives for those data sets appear in the GIMPAF.XML file determines the order in which they will be processed during the RECEIVE. Why does it matter whether each is in a unique dataset? If FMIDs are selected from an alphabetical list and dropped into a common MCS during build, wouldn't this problem still manifest? With IBM products its usually Hcc for base and Jcc for dependent, so GIMPAF order will be alpha order. Apparently not everyone follows that convention. Why does order matter? Is it because the FMID list in the GZONE entry is not updated until RECEIVE processing for that SYSMOD is complete, only after which it moves on to the next? Just curious and trying to contrast with ASSIGN statements in RECEIVE processing where order is unimportant. Thanks, Art Gutowski Compuware -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: GIM39001E in SMP/E RECEIVE FROMNTS
On Tue, 25 Sep 2012 17:24:32 -0500, Art Gutowski wrote: On Mon, 24 Sep 2012 09:18:09 -0400, Kurt Quackenbush wrote: Presumably the MCS for each SYSMOD is in a unique data set? If so, then yes, the order in which the archives for those data sets appear in the GIMPAF.XML file determines the order in which they will be processed during the RECEIVE. Why does it matter whether each is in a unique dataset? If FMIDs are selected from an alphabetical list and dropped into a common MCS during build, wouldn't this problem still manifest? I would assume so. With IBM products its usually Hcc for base and Jcc for dependent, so GIMPAF order will be alpha order. Apparently not everyone follows that convention. We don't. And I even overlooked a note to myself telling me to be careful of that. Are there second-level dependent FMIDs? Kcc? Why does order matter? Is it because the FMID list in the GZONE entry is not updated until RECEIVE processing for that SYSMOD is complete, only after which it moves on to the next? Just curious and trying to contrast with ASSIGN statements in RECEIVE processing where order is unimportant. Perhaps even more relevant is the ordering among PREs and SUPs of PTFs, where order of SYSMODs in SMPPTFIN under a single APPLY command doesn't matter. Thanks, gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
GIM44336S
OK. This was entirely a user error. I was pointing at the wrong archive in RECEIVE FROMNETWORK. But I got: GIM45500S ** VERIFICATION OF HASH VALUE OF FILE /*/*.gimzip/GIMPAF.XML FAILED. SMP/E WILL NOT RETRY FILE RETRIEVAL. GIM44336S ** AN UNUSUAL CONDITION OCCURRED. GIMJVCMF - java.security.InvalidParameterException GIM20501IRECEIVE PROCESSING IS COMPLETE. THE HIGHEST RETURN CODE WAS 12. Somehow the GIM44336S seems to be a punishment disproportionate to the offense? UNUSUAL CONDITION? security? What did I do? Will I be written up? MC was little help on this. I retried on a system with ICSF available, and got not the GIM44336S but yet the GIM45500S, which I had assumed was consequential to the GIM44336S, and this put me correctly on track for my problem. I don't consider either of these to merit RC=12. More like RC=8. But, yes, execution shouldn't continue. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
CBT File745 (File Formatter aka OS)
G'day - I've downloaded this utility from the CBT tape and I get a loop in the OSCOMM module, according to Strobe. I'm running z/os 1.11. Has anyone at this level assembled this program successfully, or more importantly, has anyone run into a loop and have a quick fix before I start debugging/tracing? Thanks from the bottom side of the planet, Tom Sydney, Oz -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Another Light goes out
http://www.computerworld.com/s/article/9231499/ Ohio_mainframe_exodus_wraps_up_in_84_500_hours?taxonomyId=68 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
