Re: Nigel's utility issue
I see that Nigel has answered you on the RACF newsgroup. I hope this has resolved your issue. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf > Of saurabh khandelwal > Sent: Wednesday, January 09, 2013 12:48 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Nigel's utility issue > > Hello, > > I am trying to setup Nigel's RACF tool but getting below issues. > To resolve this issue, I created racfdd and racfcert subdirectory under C:\Program > Files\racf path. But still issue is same. > I also created PROD and DEV directory and copied racf.ini file from C:\Program > Files\racf\examples\ini path and modified input_file=C:\Program > Files\racf\DEV\racfdev output_jcl_file=C:\Program Files\racf\DEV\JCL > output_text_file=C:\Program Files\racf\DEV\Text > > > C:\Program Files\racf>racf05 > * > > > WARNING = racf.ini specifies a drill down subdirectory of 'racfdd' > which is invalid, please check directory exists and is accessible > > * > > * > > > WARNING = racf.ini specifies a certificate subdirectory of 'racfcert' > which is invalid, please check directory exists and is accessible > > * > > Validating unload file racfdev... > Date of unload file = Wed Dec 26 14:44:29 2012 > > Error: Unable to open / create file racf05.jcl > > > But not sure, what else I am missing it. Can you please help me to resolve this issue. > > > -- > Thanks & Regards > Saurabh Khandelwal > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Nigel's utility issue
It may be: C:\Program Files\ Quite a few programs don't like the space in a directory name. Try it in another directory, i.e. C:\racf Sebastian On Wed, 9 Jan 2013 13:17:40 +0530, saurabh khandelwal wrote: >Hello, > > I am trying to setup Nigel�s RACF tool but getting below issues. >To resolve this issue, I created racfdd and racfcert subdirectory >under C:\Program >Files\racf path. But still issue is same. >I also created PROD and DEV directory and copied racf.ini file from >C:\Program Files\racf\examples\ini path and modified >input_file=C:\Program Files\racf\DEV\racfdev >output_jcl_file=C:\Program Files\racf\DEV\JCL >output_text_file=C:\Program Files\racf\DEV\Text > > >C:\Program Files\racf>racf05 >* > >WARNING = racf.ini specifies a drill down subdirectory of 'racfdd' > which is invalid, please check directory exists and is accessible > >* >* > >WARNING = racf.ini specifies a certificate subdirectory of 'racfcert' > which is invalid, please check directory exists and is accessible > >* >Validating unload file racfdev... >Date of unload file = Wed Dec 26 14:44:29 2012 > >Error: Unable to open / create file racf05.jcl > > >But not sure, what else I am missing it. Can you please help me to resolve >this issue. > > >-- >Thanks & Regards >Saurabh Khandelwal > >-- >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: Nigel's utility issue
Hello Lizette, Yes, few min back I got reply from him and solution worked for me . Thanks for help. Regards Saurabh On Wed, Jan 9, 2013 at 1:35 PM, Lizette Koehler wrote: > I see that Nigel has answered you on the RACF newsgroup. > > I hope this has resolved your issue. > > Lizette > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf > > Of saurabh khandelwal > > Sent: Wednesday, January 09, 2013 12:48 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Nigel's utility issue > > > > Hello, > > > > I am trying to setup Nigel's RACF tool but getting below issues. > > To resolve this issue, I created racfdd and racfcert subdirectory under > C:\Program > > Files\racf path. But still issue is same. > > I also created PROD and DEV directory and copied racf.ini file from > C:\Program > > Files\racf\examples\ini path and modified input_file=C:\Program > > Files\racf\DEV\racfdev output_jcl_file=C:\Program Files\racf\DEV\JCL > > output_text_file=C:\Program Files\racf\DEV\Text > > > > > > C:\Program Files\racf>racf05 > > * > > > > > > WARNING = racf.ini specifies a drill down subdirectory of 'racfdd' > > which is invalid, please check directory exists and is > accessible > > > > * > > > > * > > > > > > WARNING = racf.ini specifies a certificate subdirectory of 'racfcert' > > which is invalid, please check directory exists and is > accessible > > > > * > > > > Validating unload file racfdev... > > Date of unload file = Wed Dec 26 14:44:29 2012 > > > > Error: Unable to open / create file racf05.jcl > > > > > > But not sure, what else I am missing it. Can you please help me to > resolve > this issue. > > > > > > -- > > Thanks & Regards > > Saurabh Khandelwal > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Thanks & Regards Saurabh Khandelwal -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FREEVOL=EOV on R1.13
I dont have any more information than others about this R13 new function However... Allocation and ENQ processing are not changed. So you should expect all specified volumes to be ENQd and serialised until used. At EOV, the used volume will be DEQd. Another job that specifies the same volume list would have to wait until CLOSE time and the last volume is DEQd to get going. So whats the benefit? Also look at a related new function 'LABAN exit enhancement for multi-volume'. This is exploited by rmm in R13. You specify a single volume of a set, or an incomplete list of volsers at OPEN time the wrong sequence is detected and your tape management system can provide the correct list of volsers. I dont know, and no longer have a way to test this, but could this be a way to avoid the serialisation of all volumes at the start? For a complete answer best go to IBM and hope they ask the developer. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: LOOKAT: Bookie vs. PDF?
The minute I decide to stop delivering what the customer wants at a a price the customer can afford, I'd better get a government bail out. Vacation Notice: None Tom Puddicombe Mainframe Performance & Capacity Planning CSC 31 Brookdale Rd, Meriden, CT 06450 ITIS | (860) 428-3252 | tpudd...@csc.com | www.csc.com This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. From: Ron Hawkins To: IBM-MAIN@listserv.ua.edu Date: 01/08/2013 09:32 PM Subject:Re: LOOKAT: Bookie vs. PDF? Sent by:IBM Mainframe Discussion List No, but I wouldn't let the pilot design the passenger amenities either. > > What do customers know about web site design? would you let the > passengers fly the airplane? > -- 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
Backing up data with the help of dasd snapshots
Please bear with me, but this is an area where my knowledge is very limited. I'd need a quick and simple answer for a discussion here. Don't go too much into various possibilities. I just need to get the big picture for now. Snapshot functionality is offered by DASD subsystems, not by z/OS, right? What granularity can one get with snapshorts? - On the sub-volume level, i.e. on the individual MVS data set level ? - On a multi-volume level within one storage subsystem? - On a multi-volume level within multiple storage subsystems? -How can an application access the data in a snapshot, i.e. to create a point in time backup? -Is it reasonable to program, say in Java or PL/1, to backup data with the help of snapshot technology? - Does this require authorized functions? -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Backing up data with the help of dasd snapshots
Some simple answers as requested - Each hardware vendor supplies it's own software providing the 'snapshot' functionality. Changing hardware may necessitate changing jobs or parameters to accommodate the different hardware functionality provided. There are basically 2 levels - Full Volume & Dataset Level. In my experience, the full volume functionality is generally part of the deal when you buy the hardware. If it wasn't, you need to bargain harder. Dataset level may or may not have an extra cost - again depends on your deal. Full Volume level provides an identical copy of the volume - volser, datasets, everything. Because it's an identical volume, you can't bring it on line to the same LPAR, but you can bring it online to another LPAR if the original volume is not already online there. There are products which allow you to back the copy up while it is offline. These issues limit dataset accessibility and carry some risk if you need to understand if you use the volume on another system. There are also issues with multi-volume datasets. For the purposes of your discussion, I don't think you're interested in Full Volume. Now Dataset Level Flashcopy is more interesting because you can flash datatsets (even multi-volume ds's) to a new name. The new dataset is nearly instantaneously available while the actual physical copy happens in the background. This new dataset is available to other programs & utilities. There are also issues to consider when there are multiple subsystems involved. Luckily I don't have to deal with them except at DR as we can fit into a single subsystem. HTH's dd keller Please bear with me, but this is an area where my knowledge is very limited. I'd need a quick and simple answer for a discussion here. Don't go too much into various possibilities. I just need to get the big picture for now. Snapshot functionality is offered by DASD subsystems, not by z/OS, right? What granularity can one get with snapshorts? - On the sub-volume level, i.e. on the individual MVS data set level ? - On a multi-volume level within one storage subsystem? - On a multi-volume level within multiple storage subsystems? -How can an application access the data in a snapshot, i.e. to create a point in time backup? -Is it reasonable to program, say in Java or PL/1, to backup data with the help of snapshot technology? - Does this require authorized functions? -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This e-mail message and all attachments transmitted with it may contain legally privileged and/or confidential information intended solely for the use of the addressee(s). If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, forwarding or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately and delete this message and all copies and backups thereof. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Deleting a nonexisting volser from hsm
ARC0184I ERROR WHEN READING THE DFSMSHSM CONTROL DATA SET X RECORD FOR 300706 Volser 300706 is neither in any hsm ttoc listing (ergo the data set x record for 300706) nor in rmm, so no prev-vol recycling can come into play here unfortunately. Regarding "try a fixcds create which should then enable you to do a standard delvol." I issued a TSO HSEND FIXCDS X 300706 CREATE and hsm reported the record created: ARC0197I TYPE X, KEY 300706, FIXCDS CREATE SUCCESSFUL (I chose type X since X was what was reflected in the ARC0184I error message for volser 300706) Then followed with a DELVOL 300706 BACKUP(PURGE) but that apparently simply deleted the record just created with the fixcds create command. ARC0260I BACKUP VOLUME 300706 ENTRY DELETED leaving still, some vestige of 300706 residing somewhere in HSM A subsequent LIST TTOC SELECT(FAILEDRECYCLE) still is showing the same "ERROR WHEN READING THE DFSMSHSM CONTROL DATA SET X RECORD FOR 300706" Short of reconstructive surgery on the cds...is there any other commands I can try to tell HSM to just fuhget-about this non-existing volser 300706?? On Tue, Jan 8, 2013 at 10:32 AM, Michael Bieganski wrote: > Looking at hsm logs, I see that a recycle failed on volume 300706 along > with message ARC0184I ERROR WHEN READING THE DFSMSHSM CONTROL DATA SET X > RECORD FOR 300706. > Apparently, hsm is trying to recycle this 300706 volser twice daily and > failing each time. > I ran AUDIT MEDIACONTROLS VOLUMES(300706) and got back: ERR 110 300706- NO > V OR X RECORD so no backup or migration records exist. > Looking in RMM, I do not find any volume 300706. > HSM is trying to recycle this guy twice a day and just spinning is wheels. > I tried DELVOL 300706 BACKUP/MIGRATION/PRIMARY and all 3 responded with > ARC0260I xx VOLUME 300706 ENTRY NOT DEFINED > I also tried FIXCDS T 01-300706- DELETE and a FIXCDS T L2-300706- > DELETE > resulting in ARC0195I TYPE T, KEY xx-300706-, FIXCDS DELETE, > ERROR=RECORD NOT FOUND > Is there anyway I can delete this nonexisting volser from hsm so that it > will stop trying to recycle? > > thanks > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Language Environment SRB code
On Tue, Jan 8, 2013 at 11:04 PM, Miklos Szigetvari < miklos.szigetv...@isis-papyrus.com> wrote: > Hi > > We have made something like this, not over CEEPIPI, but over same > assembler code. > Thanks. If I understand you correctly, all of your code is Assembler. Please confirm. > > I didn't noticed this in the Vendor Interface, but a few weeks ago, there > was a Webcast about C/C++ LE etc. etc . I asked about zIIP (i.e. Enclave > SRB mode), the answer was :NO support . Will attempt to try the Vendor Interface now that you have seen it? > > > On 09.01.2013 06:36, Sam Siegel wrote: > >> The Language Environment Vendor Interfaces (SA22-7568-09) mentions the >> ability to use XL C/C++ in an SRB. This is the full XL C/C++, with some >> restrictions, not METAL-C. >> >> Chapter 4, Interfaces for Preinitialization,describes the general setup. >> The summary is that it is done by calling CEEPIPI from a TCB to >> establish >> an init_sub_dp environment. The environment token returned from the >> init_sub_dp call is then passed to the SRB. The SRB in turn calls CEEPIPI >> using the call_sub_addr_nochk (12) or call_sub_addr_nochk2(14) functions >> and the environment token returned by init_sub_dp. >> >> Additionally, the LE Service Routine vector must be used to provide >> suitable replacements. >> >> Question: Has anyone used this facility? If you have, I would like to >> exchange some emails with you to better understand the nuances involved in >> getting this to work. >> >> Thanks, >> Sam >> >> --**--** >> -- >> 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 > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Deleting a nonexisting volser from hsm
Michael, its the T record thats needed. FIXCDS T 01-300706- create Then try the delvol. Dave -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Automation for IGD17272I
Hi Mike, I'm at z/OS V.12, sorry. SMS 1.12.0 A.Cecilio On Fri, Jan 4, 2013 at 5:44 PM, af dc wrote: > Hello, > does anyone have some kind of automation to handle out-of-space SGs that > doesn't mind of sharing ?? > Everyday before going home I check all dasd SGs for any "abnormal" > occupancy and to prepare SGs to batch run without probls. But sometimes, > "after hours" I've to add some dasd volumes to a SG that has no space > available. > My question is to know from your experience in your shops if you have some > kind of process using NETVIEW, or any any other automation product that > capture IGD17272I and add dasd volumes to a SG automatically, for example, > or a product to monitor SGs space well I welcome any idea. > > I'm at z/os V.1.2 > Many thx,Antonio Cecilio. > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Deleting a nonexisting volser from hsm
See my post from yesterday.
Based on your response below, this 300706 seems to have been a backup volume.
There is apparently 1 dataset on a "prevvol" that thinks it is continued onto
300706.
1) HSEND LIST TTOC SELECT(FULL) will show all volumes eligible for recycle
(both ML2 and BACKUP).
Scan this listing for 300706 in the SUCC VOL column. (This information is
from the volume record for "prevvol").
2) HSEND LIST TTOC("prevvol") which will be the volser shown in the first
column.
HBDEL "last dsn on prevvol" ALL (this will delete the connection
to 300706)
If the above does not work, examine the recycle logs immediately prior to the
request for 300706.
If it shows that the volume immediately prior to 300706 was successfully
deleted, I would open a case with IBM. L2 can produce some pretty amazing
FIXCDS commands.
If the immediately prior volume was not successfully deleted, you have your
culprit. Perform step 2 above.
You might also try HSEND LIST DATASETNAME BCDS SELECT(VOLUME(300706)) to get
the datasets that way, independent of the TTOC's.
HBDEL these datasets.
Warning, this will run a while, depending on the size of your BCDS.
Might also be a "leftover" piece of storage. Try a bounce of the relevant DFHSM
address space (unlikely to be successful, but worth a try if all else fails).
HTH,
ARC0184I ERROR WHEN READING THE DFSMSHSM CONTROL DATA SET X RECORD FOR
300706
Volser 300706 is neither in any hsm ttoc listing (ergo the data set x record
for 300706) nor in rmm, so no prev-vol recycling can come into play here
unfortunately.
Regarding "try a fixcds create which should then enable you to do a standard
delvol."
I issued a TSO HSEND FIXCDS X 300706 CREATE and hsm reported the record created:
ARC0197I TYPE X, KEY 300706, FIXCDS CREATE SUCCESSFUL (I chose type X since X
was what was reflected in the ARC0184I error message for volser 300706)
Then followed with a DELVOL 300706 BACKUP(PURGE) but that apparently simply
deleted the record just created with the fixcds create command.
ARC0260I BACKUP VOLUME 300706 ENTRY DELETED leaving still, some vestige of
300706 residing somewhere in HSM A subsequent LIST TTOC SELECT(FAILEDRECYCLE)
still is showing the same "ERROR WHEN READING THE DFSMSHSM CONTROL DATA SET X
RECORD FOR 300706"
Short of reconstructive surgery on the cds...is there any other commands I can
try to tell HSM to just fuhget-about this non-existing volser 300706??
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Automation for IGD17272I
First all thx for sharing your ways of SG pooling mgmt, this subject is for us an activity that we work every day and with all that concern we still have SG space constrains. Here is what we have: - We have XRC SGs and Non-XRC SGs. When we need space on a non XRC SG we just use init dasd (we have XX already initialised) and add them to the non-XRC SG. For a XRC-SG we have a SG with empty dasd (that are XRCed) that we delete disc from that SG and add it to the XRC-SG. - We also have an overflow SG that is concatened on the most critical SGs - We have an SG historic record, done hourly with SG free space %: Date/Hour Alloc Free Qty AVG AllocAVG Free%Free 130109/1201 4472043900 1161788782 (499) 8962011.82 2328234.03 20.62 130109/1301 4627551004 1006281678 (499) 9273649.31 2016596.55 17.86 130109/1401 4401653661 1232179021 (499) 8820949.22 2469296.64 21.87 130109/1501 4372088379 1261744303 (499) 8761700.16 2528545.70 22.40 130109/1601 4426457653 1207375029 (499) 8870656.62 2419589.24 21.43 - We have SG Thrs but I never look at it as a concern (maybe I'm wrong): - We capture IGD17272I by Netview only to our team get noticed and act in case needed. With all those controls we still have times where a new application gets on production and we didn't know, or Database team run online reorgs we didn't know, or some batch application generating more backups that usual or even wrong dataset allocation, well, as Graham says "we dont live in an ideal world". Maybe the use of QUINEW or DISNEW volumes on some critical SGs could be a way, yes. About new products like Omegamon for Storage, do you have any experience ?? Many thx to you all, Antonio Cecilio. On Wed, Jan 9, 2013 at 4:22 PM, af dc wrote: > Hi Mike, > I'm at z/OS V.12, sorry. > > SMS 1.12.0 > > A.Cecilio > > > On Fri, Jan 4, 2013 at 5:44 PM, af dc wrote: > >> Hello, >> does anyone have some kind of automation to handle out-of-space SGs that >> doesn't mind of sharing ?? >> Everyday before going home I check all dasd SGs for any "abnormal" >> occupancy and to prepare SGs to batch run without probls. But sometimes, >> "after hours" I've to add some dasd volumes to a SG that has no space >> available. >> My question is to know from your experience in your shops if you have >> some kind of process using NETVIEW, or any any other automation product >> that capture IGD17272I and add dasd volumes to a SG automatically, for >> example, or a product to monitor SGs space well I welcome any idea. >> >> I'm at z/os V.1.2 >> Many thx,Antonio Cecilio. >> >> > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
dcollect question
Hello Esteemed Listers -
I have a question related to a dcollect that we are using here.
The current process does a dcollect as follows:
DCOLLECT OFILE(DD1) ELIMIT(50) STOG(BACKUP,-
DB2DATA, -
DB2TEMP, -
DB2LOG2, -
DB2WORK)
NODATAINFO
Generating a file for input to iceman.
Typical record in the file:
+1+2+3+4+5+6+7--
µ V PRD1 · ¤ DB21AJX ß[ç jM Ô Ã V ùÉ / 3390
--+8+9+0+1+2+3+4
Í DB2DATA 2107 ß[ç jM Ô Ã V ùÉ
+5
/
Then iceman sorts the file with the following parm:
SORT FIELDS=(87,6,CH,A)
OUTFIL FNAMES=RPT1,NODETAIL,CONVERT,OUTREC=(1,80),
HEADER1=(' ',/,
'THE STATUS OF THE POOLS ARE AS FOLLOWS'),
SECTIONS=(87,6,
TRAILER3=(1:'STORGRP ',87,8,20:' # OF VOLS',
COUNT,40:'% AVAIL',AVG=(40,1,BI)))
Which produces:
THE STATUS OF THE POOLS ARE AS FOLLOWS
STORGRP BACKUP # OF VOLS 12 % AVAIL 47
STORGRP DB2DATA# OF VOLS 36 % AVAIL 4
STORGRP DB2LOG2# OF VOLS 4 % AVAIL 52
STORGRP DB2TEMP# OF VOLS 6 % AVAIL 27
STORGRP DB2WORK # OF VOLS 3 % AVAIL 83
My question is, how to also provide a value for the total space per storgrp,
does anyone have the expertice to do so?
Thank you kindly for you assistance,
Jeff A
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Deleting a nonexisting volser from hsm
On Wednesday, January 9, 2013 10:14:13 AM UTC-6, David Devine wrote: > Michael, its the T record thats needed. FIXCDS T 01-300706- create Then > try the delvol. Dave > -- For > IBM-MAIN subscribe / signoff / archive access instructions, send email to > lists...@listserv.ua.edu with the message: INFO IBM-MAIN Tried the aforementioned FIXCDS X 300706 CREATE...and then DELVOL 300706 BACKUP(PURGE) ...no joy; Now just tried FIXCDS T 01-300706- CREATE followed by a DELVOL 300706 BACKUP(PURGE) ..but still getting same error ARC0184I ERROR WHEN READING THE DFSMSHSM CONTROL DATA SET X RECORD FOR 300706 (in fact now I get two of these ARC0184I's for 300706 when I run LIST TTOC SELECT(FAILEDRECYCLE) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ESDS extent ...
When HSM (or equivalent product) recalls a data set, it has to allocate the space on the primary DASD. That allocation will need data class attributes. In my opinion, the HSM manuals are not clear how or where HSM gets the data class attributes. I believe you, but it would be nice if the HSM manuals clearly stated that the data class attributes of a recalled data set were solely obtained from the migrated copy of data set and not from the current SMS data class. >From the z/OS V1R12.0 DFSMShsm Storage Administration manual: = Chapter 54. RECALL command: Recalling a specific migrated data set The RECALL command recalls a migrated data set. If you want, you can specify the volume and type of unit where DFSMShsm is to recall the data set. If you specify the volume and type of unit when recalling an SMS-managed data set, the volume and unit type will be passed to the automatic class selection (ACS) Routines. ACS ultimately determines to which volume the data set is recalled. The FORCENONSMS parameter allows the ability to force recall of an SMS-managed data set to a non-SMS-managed volume. It is not possible to convert a data set that is not extended format to a data set that is extended format during a recall. However, you can convert an extended format data set to a data set that is not extended format during a recall, if you specify the FORCENONSMS optional parameter. = Don Williams -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Tuesday, January 08, 2013 3:32 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... W dniu 2013-01-08 21:26, Don Williams pisze: > HSM Recall does not re-invoke the DataClas ACS routine (several years > ago, I had to proof that to my teammates). Therefore a recalled data > set will have the same data class name. Since a data class could > affect many hundreds or thousands of data sets (we still have some > applications that cannot handle extended data sets), I've never > changed a data class from non-extented to extended then tried to > recall the data set. It would be interesting to know if that would work. It is not matter whether DC is called or not (it's not AFAIK). It's matter that even changed DC does not affect existing dataset parameters. It will not affect. Caution: parameters like DVC can be changed dynamically, but actually DVC is some "potential bahavior" not "actual shape" of the physical object. Of course REPRO or EXPORT/IMPORT will change the EA parameter. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.555.904 zotych. -- 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 IB
Re: ESDS extent ...
Isn't the assigning of a dataclass upon recall dependent on the coding of the dataclass acs routine rather than HSM? -Original Message- From: Don Williams [mailto:donb...@gmail.com] Sent: Wednesday, January 09, 2013 2:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... When HSM (or equivalent product) recalls a data set, it has to allocate the space on the primary DASD. That allocation will need data class attributes. In my opinion, the HSM manuals are not clear how or where HSM gets the data class attributes. I believe you, but it would be nice if the HSM manuals clearly stated that the data class attributes of a recalled data set were solely obtained from the migrated copy of data set and not from the current SMS data class. >From the z/OS V1R12.0 DFSMShsm Storage Administration manual: = Chapter 54. RECALL command: Recalling a specific migrated data set The RECALL command recalls a migrated data set. If you want, you can specify the volume and type of unit where DFSMShsm is to recall the data set. If you specify the volume and type of unit when recalling an SMS-managed data set, the volume and unit type will be passed to the automatic class selection (ACS) Routines. ACS ultimately determines to which volume the data set is recalled. The FORCENONSMS parameter allows the ability to force recall of an SMS-managed data set to a non-SMS-managed volume. It is not possible to convert a data set that is not extended format to a data set that is extended format during a recall. However, you can convert an extended format data set to a data set that is not extended format during a recall, if you specify the FORCENONSMS optional parameter. = Don Williams -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Tuesday, January 08, 2013 3:32 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... W dniu 2013-01-08 21:26, Don Williams pisze: > HSM Recall does not re-invoke the DataClas ACS routine (several years > ago, I had to proof that to my teammates). Therefore a recalled data > set will have the same data class name. Since a data class could > affect many hundreds or thousands of data sets (we still have some > applications that cannot handle extended data sets), I've never > changed a data class from non-extented to extended then tried to > recall the data set. It would be interesting to know if that would work. It is not matter whether DC is called or not (it's not AFAIK). It's matter that even changed DC does not affect existing dataset parameters. It will not affect. Caution: parameters like DVC can be changed dynamically, but actually DVC is some "potential bahavior" not "actual shape" of the physical object. Of course REPRO or EXPORT/IMPORT will change the EA parameter. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.555.904 zotych. -- For
Re: IBM Systems Magazine Article on zEC12 + Java
Maybe 16^2 where the ^2 was too small to read? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Zelden Sent: Tuesday, January 08, 2013 4:58 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: IBM Systems Magazine Article on zEC12 + Java http://www.ibmsystemsmag.com/mainframe/trends/whatsnew/java_compiler/?page=3 "Historically, System z has had a 4K (4096-byte) page frame. The IBM System z10 mainframe introduced 1-megabyte large pages (LPs). A 1MB LP contains the equivalent of 16 4K pages." 16?? Must be new math or I'm suffering from a misconception. -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- 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: Language Environment SRB code
>> >> On 09.01.2013 06:36, Sam Siegel wrote: >> >>> The Language Environment Vendor Interfaces (SA22-7568-09) mentions the >>> ability to use XL C/C++ in an SRB. This is the full XL C/C++, with some >>> restrictions, not METAL-C. Beware that the "some restrictions" can be quite significant in practice. Many of the C/C++ library routines you might expect to use just don't work in that environment. CC -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
LLA Management of Linklst datasets
Hello All, I have a small doubt on LLA management of datasets. I know LLA managed all Linklst datasets by default and my query is if I have added a new dataset in a new lnklst set and activated this set so will it be come under lla management Or do i need to refresh/modify LLA. I am sure for deletion of lnklst datasets I have to refresh/modify LLA also but not sure for addition I tried to find in manual to see if addition also require LLA refresh/modify but didn't see however manual says about deletion. Any inputs. -- Thanks & Regards: Sunil Mirchandani 9243116830 "Yesterday I dared to struggle. Today I dare to win" -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
LLA Management of Linklst datasets
Hello All, I have a small doubt on LLA management of datasets. I know LLA managed all Linklst datasets by default and my query is if I have added a new dataset in a new lnklst set and activated this set so will it be come under lla management Or do i need to refresh/modify LLA. I am sure for deletion of lnklst datasets I have to refresh/modify LLA also but not sure for addition I tried to find in manual to see if addition also require LLA refresh/modify but didn't see however manual says about deletion. Any inputs. -- Thanks & Regards: Sunil Mirchandani 9243116830 "Yesterday I dared to struggle. Today I dare to win" -- Thanks & Regards: Sunil Mirchandani 9243116830 "Yesterday I dared to struggle. Today I dare to win" -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ESDS extent ...
Dataclass ACS is ONLY invoked on initial dataset allocations (&ACSENVIR='ALLOC') - possibly with some very exceptional exceptions (I'm not bang up to date on possible recent developments in SMS-land). But this link confirms categorically that HSM recalls and numerous other 'ACS environments' do not invoke Dataclass ACS. http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.idai600%2Facssel.htm On 9 January 2013 19:12, O'Brien, David W. (NIH/CIT) [C] < obrie...@mail.nih.gov> wrote: > Isn't the assigning of a dataclass upon recall dependent on the coding of > the dataclass acs routine rather than HSM? > > -Original Message- > From: Don Williams [mailto:donb...@gmail.com] > Sent: Wednesday, January 09, 2013 2:09 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ESDS extent ... > > When HSM (or equivalent product) recalls a data set, it has to allocate > the space on the primary DASD. That allocation will need data class > attributes. > In my opinion, the HSM manuals are not clear how or where HSM gets the > data class attributes. I believe you, but it would be nice if the HSM > manuals clearly stated that the data class attributes of a recalled data > set were solely obtained from the migrated copy of data set and not from > the current SMS data class. > > From the z/OS V1R12.0 DFSMShsm Storage Administration manual: > > > = > Chapter 54. RECALL command: Recalling a specific migrated data set > > The RECALL command recalls a migrated data set. If you want, you can > specify the volume and type of unit where DFSMShsm is to recall the data > set. > > If you specify the volume and type of unit when recalling an SMS-managed > data set, the volume and unit type will be passed to the automatic class > selection (ACS) Routines. ACS ultimately determines to which volume the > data set is recalled. > > The FORCENONSMS parameter allows the ability to force recall of an > SMS-managed data set to a non-SMS-managed volume. It is not possible to > convert a data set that is not extended format to a data set that is > extended format during a recall. However, you can convert an extended > format data set to a data set that is not extended format during a recall, > if you specify the FORCENONSMS optional parameter. > > > = > > Don Williams > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of R.S. > Sent: Tuesday, January 08, 2013 3:32 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ESDS extent ... > > W dniu 2013-01-08 21:26, Don Williams pisze: > > HSM Recall does not re-invoke the DataClas ACS routine (several years > > ago, I had to proof that to my teammates). Therefore a recalled data > > set will have the same data class name. Since a data class could > > affect many hundreds or thousands of data sets (we still have some > > applications that cannot handle extended data sets), I've never > > changed a data class from non-extented to extended then tried to > > recall the data set. It would be interesting to know if that would work. > > It is not matter whether DC is called or not (it's not AFAIK). It's matter > that even changed DC does not affect existing dataset parameters. > It will not affect. > Caution: parameters like DVC can be changed dynamically, but actually DVC > is some "potential bahavior" not "actual shape" of the physical object. > > Of course REPRO or EXPORT/IMPORT will change the EA parameter. > > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > > > -- > Tre tej wiadomo ci mo e zawiera informacje prawnie chronione Banku > przeznaczone wy cznie do u ytku s u bowego adresata. Odbiorc mo e by > jedynie jej adresat z wy czeniem dost pu osób trzecich. Je eli nie jeste > adresatem niniejszej wiadomo ci lub pracownikiem upowa nionym do jej > przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, > rozprowadzanie lub inne dzia anie o podobnym charakterze jest prawnie > zabronione i mo e by karalne. Je eli otrzyma e t wiadomo omy kowo, > prosimy niezw ocznie zawiadomi nadawc wysy aj c odpowied oraz trwale > usun t wiadomo w czaj c w to wszelkie jej kopie wydrukowane lub > zapisane na dysku. > > This e-mail may contain legally privileged information of the Bank and is > intended solely for business use of the addressee. This e-mail may only be > received by the addressee and may not be disclosed to any third parties. If > you are not the intended addressee of this e-mail or the employee > authorised to forward it to the addressee, be advised that any > dissemination, copying, distribution or any other similar activity is > legally prohibited and may be punishable. If you received this e-mail by > mistake please advise the s
Re: Language Environment SRB code
On Wed, Jan 9, 2013 at 11:23 AM, Chris Craddock wrote: > >> > >> On 09.01.2013 06:36, Sam Siegel wrote: > >> > >>> The Language Environment Vendor Interfaces (SA22-7568-09) mentions the > >>> ability to use XL C/C++ in an SRB. This is the full XL C/C++, with > some > >>> restrictions, not METAL-C. > > Beware that the "some restrictions" can be quite significant in practice. > Many of the C/C++ library routines you might expect to use just don't work > in that environment. > What about just pure C/C++ code without calling LE library routines or C-Runtime library routines and assuming that malloc/free and new/delete eventually invokes the STORAGE OBTAIN/DELETE provided by the substitute service routines? What about C++ STL? Thanks. > > CC > -- > 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: ESDS extent ...
Don, Please refer to 11.6.5 ACS routines invoked for restoring, recalling, recovering, and converting data sets in DFSMSdfp Storage Administration. Table 11 clearly shows that Dataclass in not invoked by HSM Recall or Recover. -Original Message- From: Don Williams [mailto:donb...@gmail.com] Sent: Wednesday, January 09, 2013 2:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... When HSM (or equivalent product) recalls a data set, it has to allocate the space on the primary DASD. That allocation will need data class attributes. In my opinion, the HSM manuals are not clear how or where HSM gets the data class attributes. I believe you, but it would be nice if the HSM manuals clearly stated that the data class attributes of a recalled data set were solely obtained from the migrated copy of data set and not from the current SMS data class. >From the z/OS V1R12.0 DFSMShsm Storage Administration manual: = Chapter 54. RECALL command: Recalling a specific migrated data set The RECALL command recalls a migrated data set. If you want, you can specify the volume and type of unit where DFSMShsm is to recall the data set. If you specify the volume and type of unit when recalling an SMS-managed data set, the volume and unit type will be passed to the automatic class selection (ACS) Routines. ACS ultimately determines to which volume the data set is recalled. The FORCENONSMS parameter allows the ability to force recall of an SMS-managed data set to a non-SMS-managed volume. It is not possible to convert a data set that is not extended format to a data set that is extended format during a recall. However, you can convert an extended format data set to a data set that is not extended format during a recall, if you specify the FORCENONSMS optional parameter. = Don Williams -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Tuesday, January 08, 2013 3:32 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... W dniu 2013-01-08 21:26, Don Williams pisze: > HSM Recall does not re-invoke the DataClas ACS routine (several years > ago, I had to proof that to my teammates). Therefore a recalled data > set will have the same data class name. Since a data class could > affect many hundreds or thousands of data sets (we still have some > applications that cannot handle extended data sets), I've never > changed a data class from non-extented to extended then tried to > recall the data set. It would be interesting to know if that would work. It is not matter whether DC is called or not (it's not AFAIK). It's matter that even changed DC does not affect existing dataset parameters. It will not affect. Caution: parameters like DVC can be changed dynamically, but actually DVC is some "potential bahavior" not "actual shape" of the physical object. Of course REPRO or EXPORT/IMPORT will change the EA parameter. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Ba
Re: Language Environment SRB code
>>> Sam Siegel posted: On Wed, Jan 9, 2013 at 11:23 AM, Chris Craddock wrote: > >> > >> On 09.01.2013 06:36, Sam Siegel wrote: > >> > >>> The Language Environment Vendor Interfaces (SA22-7568-09) mentions the > >>> ability to use XL C/C++ in an SRB. This is the full XL C/C++, with > some > >>> restrictions, not METAL-C. > > Beware that the "some restrictions" can be quite significant in practice. > Many of the C/C++ library routines you might expect to use just don't work > in that environment. > What about just pure C/C++ code without calling LE library routines or C-Runtime library routines and assuming that malloc/free and new/delete eventually invokes the STORAGE OBTAIN/DELETE provided by the substitute service routines? If your routines cause any of the proscribed functions to be invoked, your SRB will be terminated. Things such as an SVC will cause this. So unless you know that the compiler generated, and library contained routines, that will be used for the code you wrote, will not do something that is prohibited in SRB "mode", give it a whirl. However, I can tell you that this can be a frustrating proposition where you find something that was working yesterday, crashes tomorrow because of some unknown or unseen difference that causes a slightly different code path to be taken and some kind of I/O (OPEN any one?) gets done. Regards, Steve Thompson -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: LLA Management of Linklst datasets
On Thu, 10 Jan 2013 01:08:18 +0530, sunil mirchandani wrote: > Hello All, > >I have a small doubt on LLA management of datasets. > >I know LLA managed all Linklst datasets by default and my query is if I >have added a new dataset in a new lnklst set and activated this set so will >it be come under lla management Or do i need to refresh/modify LLA. I am >sure for deletion of lnklst datasets I have to refresh/modify LLA also but >not sure for addition If you add a new dsn to the LNKLST dynamically, tt will be added to / managed by LLA automatically. > >I tried to find in manual to see if addition also require LLA >refresh/modify but didn't see however manual says about deletion. > I don't know if / where it is documented. If not in a manual, SHARE presentations (which to me is basically the same as being "not documented"). Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ESDS extent ...
Sorry, correct link: http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.idas200%2Fs2010.htm On 9 January 2013 20:03, O'Brien, David W. (NIH/CIT) [C] < obrie...@mail.nih.gov> wrote: > Don, > > Please refer to 11.6.5 ACS routines invoked for restoring, recalling, > recovering, and > converting data sets in DFSMSdfp Storage Administration. > > Table 11 clearly shows that Dataclass in not invoked by HSM Recall or > Recover. > > -Original Message- > From: Don Williams [mailto:donb...@gmail.com] > Sent: Wednesday, January 09, 2013 2:09 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ESDS extent ... > > When HSM (or equivalent product) recalls a data set, it has to allocate > the space on the primary DASD. That allocation will need data class > attributes. > In my opinion, the HSM manuals are not clear how or where HSM gets the > data class attributes. I believe you, but it would be nice if the HSM > manuals clearly stated that the data class attributes of a recalled data > set were solely obtained from the migrated copy of data set and not from > the current SMS data class. > > From the z/OS V1R12.0 DFSMShsm Storage Administration manual: > > > = > Chapter 54. RECALL command: Recalling a specific migrated data set > > The RECALL command recalls a migrated data set. If you want, you can > specify the volume and type of unit where DFSMShsm is to recall the data > set. > > If you specify the volume and type of unit when recalling an SMS-managed > data set, the volume and unit type will be passed to the automatic class > selection (ACS) Routines. ACS ultimately determines to which volume the > data set is recalled. > > The FORCENONSMS parameter allows the ability to force recall of an > SMS-managed data set to a non-SMS-managed volume. It is not possible to > convert a data set that is not extended format to a data set that is > extended format during a recall. However, you can convert an extended > format data set to a data set that is not extended format during a recall, > if you specify the FORCENONSMS optional parameter. > > > = > > Don Williams > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of R.S. > Sent: Tuesday, January 08, 2013 3:32 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: ESDS extent ... > > W dniu 2013-01-08 21:26, Don Williams pisze: > > HSM Recall does not re-invoke the DataClas ACS routine (several years > > ago, I had to proof that to my teammates). Therefore a recalled data > > set will have the same data class name. Since a data class could > > affect many hundreds or thousands of data sets (we still have some > > applications that cannot handle extended data sets), I've never > > changed a data class from non-extented to extended then tried to > > recall the data set. It would be interesting to know if that would work. > > It is not matter whether DC is called or not (it's not AFAIK). It's matter > that even changed DC does not affect existing dataset parameters. > It will not affect. > Caution: parameters like DVC can be changed dynamically, but actually DVC > is some "potential bahavior" not "actual shape" of the physical object. > > Of course REPRO or EXPORT/IMPORT will change the EA parameter. > > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > > > -- > Tre tej wiadomo ci mo e zawiera informacje prawnie chronione Banku > przeznaczone wy cznie do u ytku s u bowego adresata. Odbiorc mo e by > jedynie jej adresat z wy czeniem dost pu osób trzecich. Je eli nie jeste > adresatem niniejszej wiadomo ci lub pracownikiem upowa nionym do jej > przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, > rozprowadzanie lub inne dzia anie o podobnym charakterze jest prawnie > zabronione i mo e by karalne. Je eli otrzyma e t wiadomo omy kowo, > prosimy niezw ocznie zawiadomi nadawc wysy aj c odpowied oraz trwale > usun t wiadomo w czaj c w to wszelkie jej kopie wydrukowane lub > zapisane na dysku. > > This e-mail may contain legally privileged information of the Bank and is > intended solely for business use of the addressee. This e-mail may only be > received by the addressee and may not be disclosed to any third parties. If > you are not the intended addressee of this e-mail or the employee > authorised to forward it to the addressee, be advised that any > dissemination, copying, distribution or any other similar activity is > legally prohibited and may be punishable. If you received this e-mail by > mistake please advise the sender immediately by using the reply facility in > your e-mail software and delete permanently this e-mail including any > copies of it either printed or saved to hard drive. > > B
Re: Language Environment SRB code
Hi On 09.01.2013 17:06, Sam Siegel wrote: On Tue, Jan 8, 2013 at 11:04 PM, Miklos Szigetvari < miklos.szigetv...@isis-papyrus.com> wrote: Hi We have made something like this, not over CEEPIPI, but over same assembler code. Thanks. If I understand you correctly, all of your code is Assembler. Please confirm. No, it is C++ code , not over CEEPIPI, but over same assembler routine to ENTER or EXIT Enclave SRB mode I didn't noticed this in the Vendor Interface, but a few weeks ago, there was a Webcast about C/C++ LE etc. etc . I asked about zIIP (i.e. Enclave SRB mode), the answer was :NO support . Will attempt to try the Vendor Interface now that you have seen it? We have a very sophisticated C/C++ application, to generate AFP or PDF datastream. Our goal was to enable _some parts_, to run on zIIP. It was impossible, to rewrite redesign it, but we could run for example the ZLIB compress/decompress CPU intensive functions, in Enclave SRB mode. On 09.01.2013 06:36, Sam Siegel wrote: The Language Environment Vendor Interfaces (SA22-7568-09) mentions the ability to use XL C/C++ in an SRB. This is the full XL C/C++, with some restrictions, not METAL-C. Chapter 4, Interfaces for Preinitialization,describes the general setup. The summary is that it is done by calling CEEPIPI from a TCB to establish an init_sub_dp environment. The environment token returned from the init_sub_dp call is then passed to the SRB. The SRB in turn calls CEEPIPI using the call_sub_addr_nochk (12) or call_sub_addr_nochk2(14) functions and the environment token returned by init_sub_dp. Additionally, the LE Service Routine vector must be used to provide suitable replacements. Question: Has anyone used this facility? If you have, I would like to exchange some emails with you to better understand the nuances involved in getting this to work. Thanks, Sam --**--** -- 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 -- 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: LLA Management of Linklst datasets
My rule of thumb, drilled into me long before z/OS, was "any change to the link list merits a refresh of LLA." Don't know if it's still valid but it never caused a problem. To me, it looks like very cheap insurance. :>: -Original Message- :>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On :>: Behalf Of sunil mirchandani :>: Sent: Wednesday, January 09, 2013 11:38 AM :>: To: IBM-MAIN@LISTSERV.UA.EDU :>: Subject: LLA Management of Linklst datasets :>: :>: Hello All, :>: :>: I have a small doubt on LLA management of datasets. :>: :>: I know LLA managed all Linklst datasets by default and my query is if I :>: have added a new dataset in a new lnklst set and activated this set so :>: will :>: it be come under lla management Or do i need to refresh/modify LLA. I am :>: sure for deletion of lnklst datasets I have to refresh/modify LLA also :>: but :>: not sure for addition :>: :>: I tried to find in manual to see if addition also require LLA :>: refresh/modify but didn't see however manual says about deletion. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Language Environment SRB code
On Wed, Jan 9, 2013 at 12:07 PM, Steve Thompson wrote: > >>> Sam Siegel posted: > On Wed, Jan 9, 2013 at 11:23 AM, Chris Craddock > wrote: > > > >> > > >> On 09.01.2013 06:36, Sam Siegel wrote: > > >> > > >>> The Language Environment Vendor Interfaces (SA22-7568-09) mentions > the > > >>> ability to use XL C/C++ in an SRB. This is the full XL C/C++, with > > some > > >>> restrictions, not METAL-C. > > > > Beware that the "some restrictions" can be quite significant in > practice. > > Many of the C/C++ library routines you might expect to use just don't > work > > in that environment. > > > > What about just pure C/C++ code without calling LE library routines or > C-Runtime library routines and assuming that malloc/free and new/delete > eventually invokes the STORAGE OBTAIN/DELETE provided by the substitute > service routines? > > > If your routines cause any of the proscribed functions to be invoked, your > SRB will be terminated. Things such as an SVC will cause this. > > So unless you know that the compiler generated, and library contained > routines, that will be used for the code you wrote, will not do something > that is prohibited in SRB "mode", give it a whirl. However, I can tell > you that this can be a frustrating proposition where you find something > that was working yesterday, crashes tomorrow because of some unknown or > unseen difference that causes a slightly different code path to be taken > and some kind of I/O (OPEN any one?) gets done. > My intention is to do all I/O on a TCB and provide buffer of data to the SRB to perform some CPU intensive tasks. The processed buffer is then used by the TCB to write output data. There would be no cases where I/O occurs in the C/C++ SRB code. Is there anyway to tell by looking at the binder map, compiler listing, etc. to see if SRB prohibited code (svc, etc.) is generated? Thanks, Sam > > Regards, > Steve Thompson > > -- > 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: Language Environment SRB code
On Wed, Jan 9, 2013 at 12:31 PM, Miklos Szigetvari < miklos.szigetv...@isis-papyrus.com> wrote: > Hi > > > On 09.01.2013 17:06, Sam Siegel wrote: > >> On Tue, Jan 8, 2013 at 11:04 PM, Miklos Szigetvari < >> miklos.szigetvari@isis-**papyrus.com > >> wrote: >> >> Hi >>> >>> We have made something like this, not over CEEPIPI, but over same >>> assembler code. >>> >>> Thanks. If I understand you correctly, all of your code is Assembler. >> Please confirm. >> > No, it is C++ code , not over CEEPIPI, but over same assembler routine to > ENTER or EXIT Enclave SRB mode Thanks ... got it now. > > >> I didn't noticed this in the Vendor Interface, but a few weeks ago, there >>> was a Webcast about C/C++ LE etc. etc . I asked about zIIP (i.e. Enclave >>> SRB mode), the answer was :NO support . >>> >> >> Will attempt to try the Vendor Interface now that you have seen it? >> >> We have a very sophisticated C/C++ application, to generate AFP or PDF > datastream. > Our goal was to enable _some parts_, to run on zIIP. > It was impossible, to rewrite redesign it, but we could run for example > the ZLIB compress/decompress CPU intensive functions, in Enclave SRB mode. > Well at least you got ZLIB running. > >>> On 09.01.2013 06:36, Sam Siegel wrote: >>> >>> The Language Environment Vendor Interfaces (SA22-7568-09) mentions the ability to use XL C/C++ in an SRB. This is the full XL C/C++, with some restrictions, not METAL-C. Chapter 4, Interfaces for Preinitialization,describes the general setup. The summary is that it is done by calling CEEPIPI from a TCB to establish an init_sub_dp environment. The environment token returned from the init_sub_dp call is then passed to the SRB. The SRB in turn calls CEEPIPI using the call_sub_addr_nochk (12) or call_sub_addr_nochk2(14) functions and the environment token returned by init_sub_dp. Additionally, the LE Service Routine vector must be used to provide suitable replacements. Question: Has anyone used this facility? If you have, I would like to exchange some emails with you to better understand the nuances involved in getting this to work. Thanks, Sam --**--** -- 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 >>> >>> --**--** >> -- >> 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 > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ESDS extent ...
W dniu 2013-01-09 20:09, Don Williams pisze: When HSM (or equivalent product) recalls a data set, it has to allocate the space on the primary DASD. That allocation will need data class attributes. In my opinion, the HSM manuals are not clear how or where HSM gets the data class attributes. I believe you, but it would be nice if the HSM manuals clearly stated that the data class attributes of a recalled data set were solely obtained from the migrated copy of data set and not from the current SMS data class. HSM role is to re-create the dataset as it was previously created. It is not the moment to change "physical shape" of the dataset like LRECL. Is EA "physical" like RECFM or RECSZ or CISZ or rather "potential" like DVC or Secondary allocation? That's the question. I bet it is physical, I'm sure Extended FOrmat is physical (it does affect allocation). Dataclass change could affect (change) parameters of newly-created datasets, for example change LRECL (RECSZ for VSAM). Such change cannot be performed for existing datasets, including scenario when a dataset is restored. THat would destroy data. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.555.904 zotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Language Environment SRB code
>>> Sam Siegel posted: On Wed, Jan 9, 2013 at 12:07 PM, Steve Thompson wrote: > >>> Sam Siegel posted: My intention is to do all I/O on a TCB and provide buffer of data to the SRB to perform some CPU intensive tasks. The processed buffer is then used by the TCB to write output data. There would be no cases where I/O occurs in the C/C++ SRB code. Is there anyway to tell by looking at the binder map, compiler listing, etc. to see if SRB prohibited code (svc, etc.) is generated? None that I know of. But I am not a C/C++ programmer. I have just heard a lot of grumbling over the cube tops from a few people I know who are doing this kind of thing for SRB Enclaves for specialty processor exploitation. And we have talked about the strange / interesting problems they have had. Regards, Steve Thompson -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Language Environment SRB code
On Wed, Jan 9, 2013 at 12:56 PM, Steve Thompson wrote: > >>> Sam Siegel posted: > > On Wed, Jan 9, 2013 at 12:07 PM, Steve Thompson > wrote: > > > >>> Sam Siegel posted: > > > My intention is to do all I/O on a TCB and provide buffer of data to the > SRB to perform some CPU intensive tasks. The processed buffer is then > used > by the TCB to write output data. > > There would be no cases where I/O occurs in the C/C++ SRB code. > > Is there anyway to tell by looking at the binder map, compiler listing, > etc. to see if SRB prohibited code (svc, etc.) is generated? > > > None that I know of. But I am not a C/C++ programmer. I have just heard a > lot of grumbling over the cube tops from a few people I know who are doing > this kind of thing for SRB Enclaves for specialty processor exploitation. > And we have talked about the strange / interesting problems they have had. > I was afraid of that. > > Regards, > Steve Thompson > > -- > 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: ESDS extent ...
No, because on a recall, the data class ACS routine is not called. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of O'Brien, David W. (NIH/CIT) [C] Sent: Wednesday, January 09, 2013 2:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... Isn't the assigning of a dataclass upon recall dependent on the coding of the dataclass acs routine rather than HSM? -Original Message- From: Don Williams [mailto:donb...@gmail.com] Sent: Wednesday, January 09, 2013 2:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... When HSM (or equivalent product) recalls a data set, it has to allocate the space on the primary DASD. That allocation will need data class attributes. In my opinion, the HSM manuals are not clear how or where HSM gets the data class attributes. I believe you, but it would be nice if the HSM manuals clearly stated that the data class attributes of a recalled data set were solely obtained from the migrated copy of data set and not from the current SMS data class. >From the z/OS V1R12.0 DFSMShsm Storage Administration manual: = Chapter 54. RECALL command: Recalling a specific migrated data set The RECALL command recalls a migrated data set. If you want, you can specify the volume and type of unit where DFSMShsm is to recall the data set. If you specify the volume and type of unit when recalling an SMS-managed data set, the volume and unit type will be passed to the automatic class selection (ACS) Routines. ACS ultimately determines to which volume the data set is recalled. The FORCENONSMS parameter allows the ability to force recall of an SMS-managed data set to a non-SMS-managed volume. It is not possible to convert a data set that is not extended format to a data set that is extended format during a recall. However, you can convert an extended format data set to a data set that is not extended format during a recall, if you specify the FORCENONSMS optional parameter. = Don Williams -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Tuesday, January 08, 2013 3:32 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... W dniu 2013-01-08 21:26, Don Williams pisze: > HSM Recall does not re-invoke the DataClas ACS routine (several years > ago, I had to proof that to my teammates). Therefore a recalled data > set will have the same data class name. Since a data class could > affect many hundreds or thousands of data sets (we still have some > applications that cannot handle extended data sets), I've never > changed a data class from non-extented to extended then tried to > recall the data set. It would be interesting to know if that would work. It is not matter whether DC is called or not (it's not AFAIK). It's matter that even changed DC does not affect existing dataset parameters. It will not affect. Caution: parameters like DVC can be changed dynamically, but actually DVC is some "potential bahavior" not "actual shape" of the physical object. Of course REPRO or EXPORT/IMPORT will change the EA parameter. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Reje
Re: ESDS extent ...
The ACS Data Class routine selects a data class name, but does not provide the associated data class attributes. Therefore an allocation could refer to the data class to obtain the attributes without the data class ACS routine being invoked. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of O'Brien, David W. (NIH/CIT) [C] Sent: Wednesday, January 09, 2013 3:04 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... Don, Please refer to 11.6.5 ACS routines invoked for restoring, recalling, recovering, and converting data sets in DFSMSdfp Storage Administration. Table 11 clearly shows that Dataclass in not invoked by HSM Recall or Recover. -Original Message- From: Don Williams [mailto:donb...@gmail.com] Sent: Wednesday, January 09, 2013 2:09 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... When HSM (or equivalent product) recalls a data set, it has to allocate the space on the primary DASD. That allocation will need data class attributes. In my opinion, the HSM manuals are not clear how or where HSM gets the data class attributes. I believe you, but it would be nice if the HSM manuals clearly stated that the data class attributes of a recalled data set were solely obtained from the migrated copy of data set and not from the current SMS data class. >From the z/OS V1R12.0 DFSMShsm Storage Administration manual: = Chapter 54. RECALL command: Recalling a specific migrated data set The RECALL command recalls a migrated data set. If you want, you can specify the volume and type of unit where DFSMShsm is to recall the data set. If you specify the volume and type of unit when recalling an SMS-managed data set, the volume and unit type will be passed to the automatic class selection (ACS) Routines. ACS ultimately determines to which volume the data set is recalled. The FORCENONSMS parameter allows the ability to force recall of an SMS-managed data set to a non-SMS-managed volume. It is not possible to convert a data set that is not extended format to a data set that is extended format during a recall. However, you can convert an extended format data set to a data set that is not extended format during a recall, if you specify the FORCENONSMS optional parameter. = Don Williams -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Tuesday, January 08, 2013 3:32 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... W dniu 2013-01-08 21:26, Don Williams pisze: > HSM Recall does not re-invoke the DataClas ACS routine (several years > ago, I had to proof that to my teammates). Therefore a recalled data > set will have the same data class name. Since a data class could > affect many hundreds or thousands of data sets (we still have some > applications that cannot handle extended data sets), I've never > changed a data class from non-extented to extended then tried to > recall the data set. It would be interesting to know if that would work. It is not matter whether DC is called or not (it's not AFAIK). It's matter that even changed DC does not affect existing dataset parameters. It will not affect. Caution: parameters like DVC can be changed dynamically, but actually DVC is some "potential bahavior" not "actual shape" of the physical object. Of course REPRO or EXPORT/IMPORT will change the EA parameter. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and de
Re: ESDS extent ...
The HSM manuals do not clearly state that the objective of HSM is to re-create the dataset as it was previously created. For example, with the right options a HSM recall can convert a SMS-managed data set to non-SMS-managed and vice versa (with some restrictions, of course). I agree that some changes like making the LRECL smaller or converting from/to EBCDIC to/from ASCII would destory data. However, HSM could be designed to perform useful minor format changes during a recall. I would love it, if HSM had recall options to change the primary and secondary allocation quanities, non-EA to EA, change blksize or cisize, etc. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Wednesday, January 09, 2013 3:52 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... W dniu 2013-01-09 20:09, Don Williams pisze: > When HSM (or equivalent product) recalls a data set, it has to > allocate the space on the primary DASD. That allocation will need data class attributes. > In my opinion, the HSM manuals are not clear how or where HSM gets the > data class attributes. I believe you, but it would be nice if the HSM > manuals clearly stated that the data class attributes of a recalled > data set were solely obtained from the migrated copy of data set and > not from the current SMS data class. HSM role is to re-create the dataset as it was previously created. It is not the moment to change "physical shape" of the dataset like LRECL. Is EA "physical" like RECFM or RECSZ or CISZ or rather "potential" like DVC or Secondary allocation? That's the question. I bet it is physical, I'm sure Extended FOrmat is physical (it does affect allocation). Dataclass change could affect (change) parameters of newly-created datasets, for example change LRECL (RECSZ for VSAM). Such change cannot be performed for existing datasets, including scenario when a dataset is restored. THat would destroy data. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.555.904 zotych. -- 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: ESDS extent ...
There's a difference between data set attributes and DATACLAS attributes. DATACLAS can assign data set attributes, but not at RECALL, the routine is not driven. The data set already has its attributes. The ACS routines in the quotation from the manual you provided would be STORCLAS and STORGRP (and MGMTCLAS? - I can't recall, don't have HSM here...) Regards, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Don Williams Sent: Wednesday, January 09, 2013 3:29 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... The ACS Data Class routine selects a data class name, but does not provide the associated data class attributes. Therefore an allocation could refer to the data class to obtain the attributes without the data class ACS routine being invoked. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ESDS extent ...
W dniu 2013-01-09 22:53, Don Williams pisze: The HSM manuals do not clearly state that the objective of HSM is to re-create the dataset as it was previously created. For example, with the right options a HSM recall can convert a SMS-managed data set to non-SMS-managed and vice versa (with some restrictions, of course). I agree that some changes like making the LRECL smaller or converting from/to EBCDIC to/from ASCII would destory data. However, HSM could be designed to perform useful minor format changes during a recall. I would love it, if HSM had recall options to change the primary and secondary allocation quanities, non-EA to EA, change blksize or cisize, etc. Well, it depends on definition of "minor change". ExtFmt, CISZ, BLKSIZE are NOT minor changes in my understanding because they change format of *existing* data. There are aplications CISZ or BLKSIZE dependent, Ext Fmt *is* physically different, etc. SMS-managed or not does not affect the data itself. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.555.904 zotych. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Backing up data with the help of dasd snapshots
DFPdss DUMP provides a option (DUMPCONDITIONING ?) which allows you to take a full-volume flashcopy of a DASD volser on IBM DASD Subsystems, but preserve the original target volser so both volumes can be online to allow a follow-up slower destaging of the target volume copy to tape with dss of the on-line target volume. As long as the volume has a VTOC Index or a VVDS, dss is able to do this in a way that allows a restore the full volume dump of the copy with the funny volser to end up with the correct original volser. This enables you to make snap copies of all significant system volumes in a few seconds to a second set of unique volsers, which with other suitable precautions can give acceptable consistency across all volume backups, while allowing destaging to tape (or remote DASD) to cover a much longer period without compromising backup consistency. This can provide a simple stategy for generating point-in-time system backups for total system recovery to a point-in-time. You are somewhat restricted in what you can do with individual data sets on the FlashCopy target volume with the different volser, but this seems a saner solution than a product that allows you to access and dump an "off-line" DASD volume. If a volume is "off-line" that should mean it's inaccessible to MVS, and that taking the related hardware off line would be non-disruptive to MVS and safe to do -- obviously not the case if you could somehow be dumping the "off-line" volume. I can't recall the rules, but I believe IBM DASD Subsystems also interface with z/OS to provide ways to group a collection of volumes together in a "consistency group" for FlashCopy of multiple volsers in a way that suppresses updates to the volumes until all in the group are flashed. JC Ewing On 01/09/2013 08:24 AM, Darth Keller wrote: Some simple answers as requested - Each hardware vendor supplies it's own software providing the 'snapshot' functionality. Changing hardware may necessitate changing jobs or parameters to accommodate the different hardware functionality provided. There are basically 2 levels - Full Volume & Dataset Level. In my experience, the full volume functionality is generally part of the deal when you buy the hardware. If it wasn't, you need to bargain harder. Dataset level may or may not have an extra cost - again depends on your deal. Full Volume level provides an identical copy of the volume - volser, datasets, everything. Because it's an identical volume, you can't bring it on line to the same LPAR, but you can bring it online to another LPAR if the original volume is not already online there. There are products which allow you to back the copy up while it is offline. These issues limit dataset accessibility and carry some risk if you need to understand if you use the volume on another system. There are also issues with multi-volume datasets. For the purposes of your discussion, I don't think you're interested in Full Volume. Now Dataset Level Flashcopy is more interesting because you can flash datatsets (even multi-volume ds's) to a new name. The new dataset is nearly instantaneously available while the actual physical copy happens in the background. This new dataset is available to other programs & utilities. There are also issues to consider when there are multiple subsystems involved. Luckily I don't have to deal with them except at DR as we can fit into a single subsystem. HTH's dd keller Please bear with me, but this is an area where my knowledge is very limited. I'd need a quick and simple answer for a discussion here. Don't go too much into various possibilities. I just need to get the big picture for now. Snapshot functionality is offered by DASD subsystems, not by z/OS, right? What granularity can one get with snapshorts? - On the sub-volume level, i.e. on the individual MVS data set level ? - On a multi-volume level within one storage subsystem? - On a multi-volume level within multiple storage subsystems? -How can an application access the data in a snapshot, i.e. to create a point in time backup? -Is it reasonable to program, say in Java or PL/1, to backup data with the help of snapshot technology? - Does this require authorized functions? -- Peter Hunkeler -- 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: LLA Management of Linklst datasets
On Wed, 9 Jan 2013 12:38:37 -0800, retired mainframer wrote: >My rule of thumb, drilled into me long before z/OS, was "any change to the >link list merits a refresh of LLA." Don't know if it's still valid but it >never caused a problem. To me, it looks like very cheap insurance. > That would be true of changing something in an existing library in the LNKLST, but not to dynamic add of a library. The second statement about cheap insurance isl true, although I would change it to LLA UPDATE. A refresh of the entire LNKLST could break something (plus has a negative performance impact). Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: ESDS extent ...
Thanks for the reminder that data set attributes are not same as DATACLAS attributes. DATACLAS provides many but not all of the possible data set attributes. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Greg Shirey Sent: Wednesday, January 09, 2013 4:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... There's a difference between data set attributes and DATACLAS attributes. DATACLAS can assign data set attributes, but not at RECALL, the routine is not driven. The data set already has its attributes. The ACS routines in the quotation from the manual you provided would be STORCLAS and STORGRP (and MGMTCLAS? - I can't recall, don't have HSM here...) Regards, Greg Shirey Ben E. Keith Company -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Don Williams Sent: Wednesday, January 09, 2013 3:29 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... The ACS Data Class routine selects a data class name, but does not provide the associated data class attributes. Therefore an allocation could refer to the data class to obtain the attributes without the data class ACS routine being invoked. -- 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: ESDS extent ...
I agree. My definition of "minor change" is a change that does not affect the application's logical view of the file as seen through its access methods. Some types of change might be "minor" for one application, whereas the same type of change for a different application would be catastrophic. Of course, I need to understand how the application accesses its files, in order to succesfully make these kinds of "minor changes". So I would love it if I could use HSM recall to do that. I can remember a stone-age application that required its master file to be a specific size on a particular volume at specific location on that volume. Hopefully, all applcations like that are long dead and gone. Nowdays, most (but not all) applications are written to be independent of the CISZ or BLKSIZE, therefore changing the CISZ or BLKSIZE makes no logical difference to the application. For an application that uses standard access methods, even changing the file from non-EA to EA should make no logical difference. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Wednesday, January 09, 2013 5:53 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... W dniu 2013-01-09 22:53, Don Williams pisze: > The HSM manuals do not clearly state that the objective of HSM is to > re-create the dataset as it was previously created. For example, with > the right options a HSM recall can convert a SMS-managed data set to > non-SMS-managed and vice versa (with some restrictions, of course). I > agree that some changes like making the LRECL smaller or converting > from/to EBCDIC to/from ASCII would destory data. However, HSM could be > designed to perform useful minor format changes during a recall. I > would love it, if HSM had recall options to change the primary and > secondary allocation quanities, non-EA to EA, change blksize or cisize, etc. Well, it depends on definition of "minor change". ExtFmt, CISZ, BLKSIZE are NOT minor changes in my understanding because they change format of *existing* data. There are aplications CISZ or BLKSIZE dependent, Ext Fmt *is* physically different, etc. SMS-managed or not does not affect the data itself. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.555.904 zotych. -- 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: LLA Management of Linklst datasets
I don't know if they still exist, but there use to be applications that did BLDLs of linklist modules. Refreshing LLA was moot. Compressing those libraries could be hazardous to those applications. Then there was the co-worker who liked to stage changes in linklist and not do the LLA refresh until implelemtation time. aghhh... Dynamically adding or deleting libraries was not possible back then. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Zelden Sent: Wednesday, January 09, 2013 6:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: LLA Management of Linklst datasets On Wed, 9 Jan 2013 12:38:37 -0800, retired mainframer wrote: >My rule of thumb, drilled into me long before z/OS, was "any change to >the link list merits a refresh of LLA." Don't know if it's still valid >but it never caused a problem. To me, it looks like very cheap insurance. > That would be true of changing something in an existing library in the LNKLST, but not to dynamic add of a library. The second statement about cheap insurance isl true, although I would change it to LLA UPDATE. A refresh of the entire LNKLST could break something (plus has a negative performance impact). Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- 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: LLA Management of Linklst datasets
Why are these posts being duplicated? I saw this, originally, around the timestamp on it. Amd, again, around 8 hours later. - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -Original Message- From: sunil mirchandani Sender: IBM Mainframe Discussion List Date: Thu, 10 Jan 2013 01:05:44 To: Reply-To: IBM Mainframe Discussion List Subject: LLA Management of Linklst datasets Hello All, I have a small doubt on LLA management of datasets. I know LLA managed all Linklst datasets by default and my query is if I have added a new dataset in a new lnklst set and activated this set so will it be come under lla management Or do i need to refresh/modify LLA. I am sure for deletion of lnklst datasets I have to refresh/modify LLA also but not sure for addition I tried to find in manual to see if addition also require LLA refresh/modify but didn't see however manual says about deletion. Any inputs. -- Thanks & Regards: Sunil Mirchandani 9243116830 "Yesterday I dared to struggle. Today I dare to win" -- 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: LLA Management of Linklst datasets
And, again! - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -Original Message- From: sunil mirchandani Sender: IBM Mainframe Discussion List Date: Thu, 10 Jan 2013 01:08:18 To: Reply-To: IBM Mainframe Discussion List Subject: LLA Management of Linklst datasets Hello All, I have a small doubt on LLA management of datasets. I know LLA managed all Linklst datasets by default and my query is if I have added a new dataset in a new lnklst set and activated this set so will it be come under lla management Or do i need to refresh/modify LLA. I am sure for deletion of lnklst datasets I have to refresh/modify LLA also but not sure for addition I tried to find in manual to see if addition also require LLA refresh/modify but didn't see however manual says about deletion. Any inputs. -- Thanks & Regards: Sunil Mirchandani 9243116830 "Yesterday I dared to struggle. Today I dare to win" -- Thanks & Regards: Sunil Mirchandani 9243116830 "Yesterday I dared to struggle. Today I dare to win" -- 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: ESDS extent ...
Don: Sorry to say that there are still (to this day) datasets (SAS) comes to mind. I (Long ago) opened a problem with them asking that they at the minimum change it to dsorg=dau (direct access unmovable) but got the stupid ass reply well it moveable if you use sas. SIGH... I gave up and did a campaign in the company that if you used sas do not create sas db's. I got a willingness to comply but we dropped SAS ($$ and other issues) so it really didn't make a whole lot of difference. Ed On Jan 9, 2013, at 5:59 PM, Don Williams wrote: I agree. My definition of "minor change" is a change that does not affect the application's logical view of the file as seen through its access methods. Some types of change might be "minor" for one application, whereas the same type of change for a different application would be catastrophic. Of course, I need to understand how the application accesses its files, in order to succesfully make these kinds of "minor changes". So I would love it if I could use HSM recall to do that. I can remember a stone-age application that required its master file to be a specific size on a particular volume at specific location on that volume. Hopefully, all applcations like that are long dead and gone. Nowdays, most (but not all) applications are written to be independent of the CISZ or BLKSIZE, therefore changing the CISZ or BLKSIZE makes no logical difference to the application. For an application that uses standard access methods, even changing the file from non-EA to EA should make no logical difference. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM- m...@listserv.ua.edu] On Behalf Of R.S. Sent: Wednesday, January 09, 2013 5:53 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ESDS extent ... W dniu 2013-01-09 22:53, Don Williams pisze: The HSM manuals do not clearly state that the objective of HSM is to re-create the dataset as it was previously created. For example, with the right options a HSM recall can convert a SMS-managed data set to non-SMS-managed and vice versa (with some restrictions, of course). I agree that some changes like making the LRECL smaller or converting from/to EBCDIC to/from ASCII would destory data. However, HSM could be designed to perform useful minor format changes during a recall. I would love it, if HSM had recall options to change the primary and secondary allocation quanities, non-EA to EA, change blksize or cisize, etc. Well, it depends on definition of "minor change". ExtFmt, CISZ, BLKSIZE are NOT minor changes in my understanding because they change format of *existing* data. There are aplications CISZ or BLKSIZE dependent, Ext Fmt *is* physically different, etc. SMS-managed or not does not affect the data itself. -- Radoslaw Skorupka Lodz, Poland -- Tre tej wiadomoci moe zawiera informacje prawnie chronione Banku przeznaczone wycznie do uytku subowego adresata. Odbiorc moe by jedynie jej adresat z wyczeniem dostpu osób trzecich. Jeeli nie jeste adresatem niniejszej wiadomoci lub pracownikiem upowanionym do jej przekazania adresatowi, informujemy, e jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne dziaanie o podobnym charakterze jest prawnie zabronione i moe by karalne. Jeeli otrzymae t wiadomo omykowo, prosimy niezwocznie zawiadomi nadawc wysyajc odpowied oraz trwale usun t wiadomo wczajc w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorised to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. BRE Bank SA, 00-950 Warszawa, ul. Senatorska 18, tel. +48 (22) 829 00 00, fax +48 (22) 829 00 33, www.brebank.pl, e-mail: i...@brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237, NIP: 526-021-50-88. Wedug stanu na dzie 01.01.2013 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 168.555.904 zotych. -- 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, se
Using DFS/SMB binary mode for VB datasets
Hi, Does anyone know whether DFS/SMB can treat the RDW as part of the data if you mount a VB file in binary mode? Reading a VB file in binary mode requires the record length information, as record delimiters can't be inserted. A search of the documentation didn't find anything obvious (to me). Or perhaps DFS/SMB can be persuaded to treat the file as RECFM=U, without splitting it into records at all? The aim is to read SMF data from a PC by mapping the SMF dump datasets to a network drive on the PC. Thanks, Andrew Rowley -- Andrew Rowley Black Hill Software Pty Ltd and...@blackhillsoftware.com +61 413 302 386 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
