Ron,
Thank you for the good response. It is true that the DFSMSdss
COMPRESS keyword and HWCOMPRESS keyword do not perform the same types of
compression. Like Ron said, the COMPRESS keyword is using a Huffman
encoding technique, and works amazing for repeated bytes (just the types of
things
Esmie,
I would add the UTILMSG=YES parameter to the backup EXEC statements.
This will tell you if DFSMSdss is invoking ICKDSF to init the volumes
instead of simply issuing the FCWITHDRAW after the DUMP is completed. If
ICKDSF is being invoked, it is because the VTOC tracks of the DASD volume
I am very sad to hear this news. I had always looked forward to meeting
Mr. Black someday. I had great respect for him through his responses
on this list. His ability and willingness to equally answer questions about
FDR as well as DFSMSdss spoke volumes to me about his character. I
was always
When you use ICKDSF to init a volume, it will issue an FCWITHDRAW for
that volume just as Joel said. Since the volume is newly inited, then there
is no reason to have a relationship as all those tracks are free space.
If you are using DFSMSdss to dump, we have an FCWITHDRAW keyword
that requests
Tom,
I'm sorry, but there is no way that I know of to do that.
Thanks,
Andrew Wilt
IBM DFSMSdss Architecture/Development
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 07/05/2007
11:28:50 AM:
I think I'm out of luck, but wanted to verify first. We're z/OS 1.7.
We've had
Hello Errol,
I hope this can allay your fears. The default tape blocksize of 64k
was done in 1988 in APAR PL18193. Your DR site should be able to read
DFSMSdss dump tapes with that block size. What OA13742 did was to
cause the block size that we were using to be put into the tape label where
Hi John,
I think that is just a requirement of DFSMSdss that when it is to
process
a Catalog, then you have to specify the fully qualified name. I don't know
off the top of my head what the rationale at the time was, but I imagine it
is to protect you from accidentally processing a User
Yes. Either way should work. (**,SYS2.AM.MYCAT) or (SYS2.AM.MYCAT,**)
Thanks,
Andrew Wilt
IBM DFSMSdss Architecture/Development
Tucson, Arizona
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 05/02/2007
07:16:54 AM:
So Andrew, are you saying that
Include(**,SYS2.AM.MYCAT)
I'd like to second John's request/recommendation on adding your
voices to either the marketing request or the SHARE requirement.
The more people interested in a particular change that add their
voices/votes, the more it helps the priority get set so that the
change gets done.
Thanks,
Andrew
Hello,
If you are using the Application Programming Interface for DFSMSdss, then
you
have access to the various exits that ADRDSSU calls during its processing.
Exit option 23 would be the one to look for. It is the Data Set Processed
Notification
exit, and comes with return codes indicating
Hello,
The DELETECATALOGENTRY keyword may be responsible for what you are
seeing. However, it should only be issuing a DELETE NOSCRATCH for data set
names
that are catalog entries, not for aliases. I guess it could be the case
that your alias may be
exactly the same as the name of a data set
I was very saddened to hear that Dr. Griswold had passed away. I had him
for a course at the University of Arizona in his Icon programming
language.
He was a great teacher. I was always impressed at his down-to-earth style
especially in light of his lifetime of accomplishments.
Thanks,
Radoslaw and all,
You are correct in that ADRDSSU 64kB blocks. In APAR OA13742, we made
a change
to how we opened the output data set when writing to tape. This change
allows our 64Kb
blocksize to show up in the new blocksize field and be recorded by tape
management systems.
Thanks,
Dennis,
I believe that if you have the FlashCopy v2 Extension for your HDS,
DFSMSdss
should act just like it is working with an ESS and attempt to use the
FlashCopy interface
to do an instant copy of the volume. (I can't say for sure since I haven't
had the chance
to try it on an HDS. We
Mark,
I looked through our publications for a specific mention of what you
would like to have documented and couldn't find one. I will see about
getting
it included in the next round of publications.
I would like to take the opportunity to share our rationale and
accept
your feedback
Rex,
The REPLACEUNCONDITIONAL keyword isn't documented in the z/OS v1.4
manuals because it was a feature we shipped via SPE (APAR) long after z/OS
v1r4 was in the field. If you check a current version of the publications,
say z/OS v1r7, it is documented there.
Thanks,
Andrew Wilt
IBM
John,
Off the top of my head, I think the reason that the offline volumes
are being requested for mount is due to RACF (Security) processing.
Because the source data set catalog is available to the target system,
DFSMSdss is seeing that the original data set is cataloged. Since it is
17 matches
Mail list logo
