Brad -
You might want to take a look at the IOCINFO macro. The IODFINFO subparm is
probably what you're looking which returns both the IODF DSN and VOLSER.
Frank.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Brad Wissink
Sent:
Rex -
When you say 'remove the tapes' what is it you are attempting to do exactly. Is
there a TMS consideration of any kind or are all these old volumes disposable ?
If they are, you can build a volume list to use as input to IDCAMS DELETE
VOLENT to remove them from the TCDB. The library does
Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Bonaduce, Frank
Sent: Thursday, April 05, 2012 11:29 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: manual tape library question
Rex -
When you say 'remove the tapes' what is it you are attempting to do exactly. Is
there a TMS
Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Bonaduce, Frank
Sent: Thursday, April 05, 2012 12:45 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: manual tape library question
Rex -
Good, only 100 volumes is easily manageable. I really can't answer to RMM as we
use CA-1 where an IDCAMS
John -
There is a utility available from CBTTAPE.ORG called BYPASSNQ that was
developed by Gilbert St. Flour (RIP). It has worked quite well on a number of
occasions so you might want to check it out. I believe it is FILE183 on that
site.
Frank.
-Original Message-
From: IBM
Lizette -
I would be happy to take a look at it for you and offer my opinion. Please
reply to me directly.
Frank.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Lizette Koehler
Sent: Thursday, February 23, 2012 12:33 PM
To:
As an aside, we DO use a local UJV exit which allows system symbolic
substitution in batch jobs. It has proven to be very helpful in our
environment. If anyone is interested, please advise.
Frank Bonaduce
VP GSG Systems Engineering
-Original Message-
From: IBM Mainframe Discussion
Steve -
Attached is an extract of a dialog I had with the vendor on this some time ago
which you may find useful. We have not as yet implemented their solution.
VENDOR-SUPPLIED INFORMATION:
Attached is the
Dale -
Yes, that is indeed true but since I am not really well versed in REXX (I still
write my CLISTs the old-fashioned way), I went with what I knew when making my
suggestion.
Frank.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Another possibility in addition to those mentioned is using the Catalog Search
Interface, IGGCSI00. If you are versed in Assembler, it offers a lot of
flexibility to design a reporting mechanism to meet your requirements.
-Original Message-
From: IBM Mainframe Discussion List
Mark -
I guess that might depend on the configuration. We use individual VOLCATs for
each of our volume ranges which are unique to each system so I never even
considered it given that the individual volume entries are sporadically
referenced at best. I suppose if a single VGENERAL is used for
Raising the Reclaim Threshold Percentage will generally cause volume
reclamation to release more physical stacked volumes but there are a number of
factors that come into play, like the distribution of the expiration dates of
the virtual volumes. We occasionally bump the RTP up to increase the
help needed
On Mon, 12 Sep 2011 15:27:10 -0400, Bonaduce, Frank frank.bonad...@gs.com
wrote:
Availability/Accessibility is another issue determined by how the CHPIDs are
defined in each LCSS. If they are to be accessible to all LCSSs then they
should be defined as SHARED. Once a CHPID is defined
Mike -
The RESOURCE statement addresses defining the LCSS that any given LPAR 'lives'
on; ie: LPAR SYSTEMA is defined on LCSS0 and LPAR SYSTEMB is defined on LCSS1,
so the LPAR only exists in a single LCSS.
Availability/Accessibility is another issue determined by how the CHPIDs are
defined in
Peter -
Yes, that would be correct and a partial assumption on my part since the work I
had been doing recently was with IEFUTL. At least in that case, there is no
doubt that it runs under the Initator. This is evidenced by what is seen in the
TCB chain where you do eventually reach the
This is the information that I passed down to the original poster with a
suggestion of how I follow the TCB 'chain' down to the JOBSTEP TCB, assuming
that's what he needs to do. The reason for this is that the point of origin is
an SMF exit, presumably hung as an IRB off of the Initiator so the
Greg -
As Kevin said, at some point in HCD you specified LIBRARY=YES hence the 'L' for
library.
Frank.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Greg Caserta
Sent: Tuesday, August 30, 2011 4:06 PM
To: IBM-MAIN@bama.ua.edu
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Schwarz, Barry A
Sent: Monday, August 29, 2011 8:53 AM
To: IBM-MAIN@bama.ua.edu
Subject: CA-1 TMSXITJ
We are migrating our CA-1 TMSXITJ accounting exit from OS/390 (where it was
called
Barry -
Sorry for the empty reply earlier (finger-check). You are definitely on the
right track. ASXBFTCB is the first TCB on a TCB queue for the address space,
which is likely the RCT (Region Control Task). For the 'average' batch job you
have to drill down to the fourth or fifth TCB in the
Bob -
I recall reading something about a chip inside the 3592 cartridge that, among
other things, contains a tape 'VTOC' which is presumably used to perform a high
speed search to locate multiple files on the cartridge. We have a small pool of
several hundred 3592s in our ATLs that we use
Chip -
Is this out-of-sync condition a pervasive problem for you ? By design, the
hardware tokens are always in sync whether the configuration is loaded via CPC
ACTIVATE (POR) or Dynamic Activation. The only 'out-of-sync' condition you may
experience is the hardware (CSS) token and the
As the issue has been pretty much addressed, I just wanted to add that in
addition to TMSCOPY to backup the TMC/AUDIT files, there should be at least a
daily execution of maintenance utilities like TMSCTLG, TMSEXPDT, TMSCYCLE and
TMSCLEAN. This will ensure that volumes which should be expiring
Has anyone been able to successfully reproduce the pseudo-code example provided
in the HCD User's Guide for this interface in Assembler ? I developed a module
which I expected would do exactly that but even after numerous adjustments to
the various parameters, I cannot get the service to
23 matches
Mail list logo
