It has come to our attention that the SHARE member directory is being
used by the employee of a SHARE member company to advertise a new
product. The SHARE member directory provides a facility for members to
contact one another directly. It does not reveal the email of the
recipient, but does
You either have 2 NVR entries for this data set in the VVDS, or this
data set is cataloged in 2 different catalogs. List the VVDS to see
what catalog the NVR points to and whether there are 2 NVR's. Then run
a LISTCAT ENT(dsn) CATALOG(catname) ALL using the catname from the
NVR to see if the
There is not a way to turn this off. This should not be an issue when
moving data sets. I am not sure I understand what type of problem you
are encountering.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Clark, Kevin
Sent: Tuesday, April
We have been using RLS for our HSM CDS's for over 8 years. It is very
beneficial for a sysplex when there are more than 3 systems in the
sysplex. With less than 3, there are not as many benefits.
There are 2 main benefits 1) Things like Autobackup, Primary Space
Management, EXPIREBV, RECYCLE,
We use ACC, and it has been a great product for us. We have been able
to solve some very interesting problems with this product.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Steve Mann
Sent: Thursday, March 22, 2007 10:41 AM
To:
I agree with Sam. PDSE data sets had some major problems during the
first 10 years after they were introduced, but IBM has made some major
improvements over the past 3 or 4 years. We have over 32,900 PDSE data
sets in our main production sysplex, and we are heavy users of this
technology. In
Can you provide some details about your problem? Was it a known problem
or a new problem?
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Ted MacNEIL
Sent: Monday, March 26, 2007 8:49 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Start of a PDSE
ISC limits the amount of cache used for each catalog, and ISC is a
dumb cache when compared to VLF.
When a catalog using ISC is shared with multiple systems and the Catalog
Address Space (CAS) detects an update from another system, CAS will
invalidate all the records in ISC. When a catalog using
Some suggestions:
SETSYS DUMPIO(4,4) -- Read a cylinder at a time when backing up or
migrating data sets
PATCH .MCVT.+391 X'05' VERIFY(.MCVT.+391 X'00') -- INCREASE THE
NUMBER OF I/O BUFFERS USED FOR A DATA SET TO 5 WHEN IT IS BACKED UP,
MIGRATED, RECALLED, OR RECOVERED (DEFAULT IS 1)
PATCH
Perhaps you did not enter something in your test case that your ACS
routines are checking for (DSORG or SPACE for example).
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Lizette Koehler
Sent: Friday, March 02, 2007 1:25 PM
To:
Try the following commands.
HSEND LIST TTOC SELECT(CONNECTED) TERMINAL or HSEND LIST TTOC
SELECT(CONNECTED) ODS(dsn)
HSEND LIST TTOC SELECT(EXCESSIVEVOLUMES) ODS(dsn)
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2S440/24.4
.16?SHELF=EZ2ZO10GDT=2005071036
-Original
Not-deferred is the default when writing to a VSAM KSDS, so if you are
getting deferred writes it is because something is overriding the
default. Did you specify MACRF=DFR on your ACB? Did System Managed
Buffering (SMB) get invoked?
-Original Message-
From: IBM Mainframe Discussion
Since z/OS 1.5, VSAM RLS is not required in order to make the HSM MCDS,
BCDS, and OCDS an Extended Addressability data set, but as another
poster pointed out RLS provides some very nice performance benefits in a
multi-system sysplex.
You should re-consider your policy to reorganize your HSM CDS's
All of the product that help maintain catalogs have the ability to
delete a specific VVR. The main ones are T-REX from Dino-Software,
Catalog Recovery Plus from Mainstar, and Catalog Solutions from EMC.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Judy,
Your MCDS is your catalog for all of your migrated data sets. You
should not use FIXCDS to delete records because that will cause your
MCDS to get out of synchronization with your ICF catalogs. If you want
to delete migrated data sets, use the IDCAMS DELETE command, the ISMF
DELETE
You will find this to be necessary reading.
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2U241/11.0
?SHELF=EZ2ZO10GDT=20060126014004
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Lester, Bob
Sent: Thursday, January 25,
For SMS managed data sets, EXPIREBV uses what is specified in the
MGMTCLAS to determine when to delete old backup versions.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Larry Burch
Sent: Thursday, December 21, 2006 9:58 AM
To:
There are lots of reasons primary space management is not finishing.
This may be one of them.
What version of DFSMShsm are you running?
How many tasks are you using the Primary Space Management?
Do most of your MGMTCLAS definitions specify to go to ML1 or directly to
ML2 or both?
What type of
Put all of the volumes in the connected set in the same VTS.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
Chiam, Susan Mee-Shia
Sent: Wednesday, December 13, 2006 2:30 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: HSM msg ARC0962A
Hi listers,
I
We have several REXX execs that issue HSM commands and then interrogate the
output. We do this using our automation product, OPS/MVS. The following is an
example of the command used to issue a QUERY ACTIVE WAITING command.
OPSCMD COMMAND('F hsmid,QUERY ACTIVE cdsparm WAITING'),
Beginning with z/OS 1.5, DSS supports copying HFS data sets (you had to
dump and then restore them before that). You will need to unmount them
in order to copy them.
In order to change a data set from being SMS managed to a non-SMS
managed data set with DSS, you will need to specify
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Jan MOEYERSONS
Sent: Thursday, November 30, 2006 4:12 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: MB to Cyl Conversion
Is there a formula for this ? Also Gb to cyl.
Thanks
Here is a little REXX
IBMLink via green-screen has been working all week.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at
You can use the FIXCDS command to correct these records. You will need to
reference the z/OS V1R6.0 DFSMShsm Diagnosis Guide and Reference manual to get
the record layout for the MCP record. IBM dropped lots of information from the
z/OS 1.7 manuals, including the MCP record.
-Original
Did HSM abend or get cancelled while using the SDSP the ML1 data set is
in and/or the tape the ML2 data set is on? If so, the in-use bit may
be on for these resources.
To check the system identifier for the tape TTOC record --
FIXCDS T L2-123456- DISPLAY(X'00') LENGTH(4)
To turn off the
Check out the text in APAR's OA11362, OA13098, and OA11603.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of John Benik
Sent: Monday, November 13, 2006 3:24 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: ARC0103I when adding STK VSM to virtual tape
Yes, primary space management would restart when HSM comes back up and
run until 09:00.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of esmie moo
Sent: Tuesday, October 31, 2006 8:52 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: DFHSM - PRIMARY SPACE
Jim,
1. Yes
2. All
3. N/A
4. N/A
5. I do not know why SAP would have a problem? The sharing protocol is
completely transparent to the application.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Petersen, Jim
Sent: Friday, October 27,
Thanks, Paul
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Paul Dineen
Sent: Wednesday, October 25, 2006 11:26 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Large Format Sequential Data Sets (OA17875 may cause LARGE
when not requested)
Michael,
Are these LPAR's in 2 different SMS-plexes, and if so, are they sharing
DASD? That is a no-no.
DSS dump the data sets to tape in one LPAR and restore them in the other
LPAR.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Lester, Bob
Sent:
With PDSE and SMS compressed data sets, there is the concept of a
logical blocksize and a physical blocksize. In both cases, the physical
blocksize is 4096. That is the blocking factor used to store the data
on disk. The logical blocksize, either specified by the user or
selected by System
I believe APAR OA13742 will resolve your problem.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Jean Pernet
Sent: Tuesday, October 03, 2006 2:11 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Large Block Interface
Situation:
zOS 1.4, DFDSS 1.3
What is the value you are specifying in your ARCCMDxx parmlib member for
SETSYS UNIT()? If you are using an esoteric, is that esoteric
specified in the SETSYS USERUNITTABLE command?
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Doyle
We had the same situation, and yes, you have to issue 10,000 eject
commands. I wrote a REXX program to create the commands, too.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of McKown, John
Sent: Monday, October 02, 2006 8:31 AM
To:
Initialize the volume, vary it online, define the VVDS, and then add it
to the SMS configuration. If it has not been added to an SMS storage
group, SMS will not try to allocate a data set on it.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf
If the data set was SMS managed when it was backed up, you need to
specify NULLSTORCLAS and NULLMGMTCLAS. Otherwise, DSS will pass the
original STORCLAS and MGMTCLAS to Allocation since you are bypassing the
ACS routines (which may assign a different STORCLAS and MGMTCLAS, or
none at all, if not
We set TAPEBLKSZLIM=32760 in SYS1.PARMLIB(DEVSUPP00) as the default and
either use a DATACLAS definition or JCL to override it. Not everything
we have is large block enabled, and we do not want to risk jobs abending
just because we changed the default to 256K.
The ZDVT.MGDC001.IDCUT1 data set is being allocated with a DISP=OLD, but
it does not look like it exists.
By the way, I have not used internal IDCAMS sort in years. You will get
better performance removing the IDCAUT1 and IDCUT2 DD statements and
using your installed SORT product instead of
There are lots of ways to determine how full a VSAM data set it, and
many ways to monitor it. Products that can tell you how full a data set
is include IDCAMS LISTCAT, IDCAMS DCOLLECT, Catalog Solutions from EMC,
Catalog Recovery Plus from Mainstar, T-REX AMS/E from Dino Software,
Vantage from
Yes.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Joe jeffries
Sent: Thursday, August 17, 2006 10:32 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: PDA on DFHSM
Hi folks,
Just double checking. If PDA=none is set in the hsm parmlib, you can use
a
VSAM OPEN will run an implicit VERIFY if it detects the data set was not
closed properly the last time it was open for update.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Jim McAlpine
Sent: Tuesday, August 15, 2006 8:29 AM
To:
HSM RECYCLE has to update the BCDS with the new volser for every data
set moved to the new tape. If you have lots of small data sets on these
tapes, that update activity will slow things down. If you are running
other processes like Auto Backup or EXPIREBV at the same time, you may
be
See section 1.5.1.2.1 of the same manual. The HSM proc must point to
these data sets.
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Joe jeffries
Sent: Monday, July 31, 2006 8:45 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: HSM PDA Datasets
We
van der Eynden
Sent: Tuesday, March 28, 2006 11:20 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Anyone Using IBM 3592, Sun/STK 9940, or Sun/STK T1
Cartridges for HSM ML2?
On Tue, 28 Mar 2006 16:01:03 -0600, Friske, Michael
[EMAIL PROTECTED] wrote:
Is anyone using IBM 3592, Sun/STK 9940, or Sun
Is anyone using IBM 3592, Sun/STK 9940, or Sun/STK T1 cartridges for
HSM ML2? If so, have you had any issues (slow recall times, recall tape
takeaway, recycle, audit, duplexing, or other)?
If you can answer yes to the first question, please take a moment to
reply. Otherwise, disregard this
45 matches
Mail list logo