In <[EMAIL PROTECTED]>, on 05/24/2007
at 03:19 PM, Mark Zelden <[EMAIL PROTECTED]> said:
>But you can do so if they are "read only". We've had this
>discussion many times and I suspect you have read the posts and the
>caveats.
One of the caveats from IBM was that you could break the library
On Thu, 24 May 2007 09:55:27 -0300, Shmuel Metz (Seymour J.)
<[EMAIL PROTECTED]> wrote:
>In <[EMAIL PROTECTED]>, on 05/23/2007
> at 10:21 AM, Mark Zelden <[EMAIL PROTECTED]> said:
>
>>I will probably not use the symbolic alias / catalog since we share
>>the same sysres set across sysplexes in so
In <[EMAIL PROTECTED]>, on 05/23/2007
at 10:21 AM, Mark Zelden <[EMAIL PROTECTED]> said:
>I will probably not use the symbolic alias / catalog since we share
>the same sysres set across sysplexes in some cases.
That's not supported for HFS and ZFS.
--
Shmuel (Seymour J.) Metz, SysProg
The "heavy-hand" is being applied by DFP. Since the ZFS is a VSAM dataset,
that means there is an entry in the VVDS dataset on that volume. But DFP
does not have the mechanism to build a VVDS dataset name based on a system
symbolic for the volume name when it goes looking for that information.
W
Alan Scott wrote:
On Tue, 22 May 2007 20:19:37 -0400, John Eells <[EMAIL PROTECTED]> wrote:
Which doesn't work for zFS. Which brings back similar issues
that there were when HFS had to be SMS controlled.
True. For zFS the usercat with symbolic aliasing is the
alternative. (You can like i
Matthew Stitt wrote:
ZFS is not the issue. HFS has the same restriction. Hence many shops use a
specific dataset name for them, probably with variable substitution, like
the matching sysres volser in the name. Of course this is assuming the
HFS/ZFS reside on different volumes than the target l
On Wed, 23 May 2007 10:45:02 -0500, Alan Scott <[EMAIL PROTECTED]> wrote:
>Mark,
>Let us know how it works out. I to have my HFS's cataloged to system
>symbols. &SRESH1 and $SRESH2. With HFS's I can use FDR and just duplicate
>the entire volume to propogate maintenance to other systems from m
Mark,
Let us know how it works out. I to have my HFS's cataloged to system
symbols. &SRESH1 and $SRESH2. With HFS's I can use FDR and just duplicate
the entire volume to propogate maintenance to other systems from my SMP/e
volumes. We have not come up with a solution that we like to handle
On Wed, 23 May 2007 10:08:56 -0500, Matthew Stitt <[EMAIL PROTECTED]> wrote:
>ZFS is not the issue. HFS has the same restriction.
What same restriction?
>Hence many shops use a
>specific dataset name for them, probably with variable substitution, like
>the matching sysres volser in the name. O
On Wed, 23 May 2007 09:54:35 -0500, Alan Scott <[EMAIL PROTECTED]> wrote:
>On Tue, 22 May 2007 20:19:37 -0400, John Eells <[EMAIL PROTECTED]> wrote:
>
>>>
>>> Which doesn't work for zFS. Which brings back similar issues
>>> that there were when HFS had to be SMS controlled.
>>>
>>
>>
>>True. For
On Wed, 23 May 2007 09:54:35 -0500, Alan Scott wrote:
>On Tue, 22 May 2007 20:19:37 -0400, John Eells <[EMAIL PROTECTED]> wrote:
>
>>> Which doesn't work for zFS. Which brings back similar issues
>>> that there were when HFS had to be SMS controlled.
>>
>>True. For zFS the usercat with symbolic
ZFS is not the issue. HFS has the same restriction. Hence many shops use a
specific dataset name for them, probably with variable substitution, like
the matching sysres volser in the name. Of course this is assuming the
HFS/ZFS reside on different volumes than the target library set. I've not
t
On Tue, 22 May 2007 20:19:37 -0400, John Eells <[EMAIL PROTECTED]> wrote:
>>
>> Which doesn't work for zFS. Which brings back similar issues
>> that there were when HFS had to be SMS controlled.
>>
>
>
>True. For zFS the usercat with symbolic aliasing is the
>alternative. (You can like it or de
Mark Zelden wrote:
On Tue, 22 May 2007 16:10:14 -0400, John Eells <[EMAIL PROTECTED]> wrote:
- From a software packaging standpoint, if your software lives on
the sysres target volume set you should provide support for
indirect cataloging using system symbols. People can define
system symbols
On Tue, 22 May 2007 16:10:14 -0400, John Eells <[EMAIL PROTECTED]> wrote:
>
>- From a software packaging standpoint, if your software lives on
>the sysres target volume set you should provide support for
>indirect cataloging using system symbols. People can define
>system symbols based on the val
Paul Gilmartin wrote:
On Tue, 22 May 2007 08:15:16 -0400, John Eells wrote:
I am completely naive of "indirect cataloguing". What book should
I read?
- The parameters for DEFINE NONVSAM in z/OS DFSMS Access Method
Services for Catalogs:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/B
On Tue, 22 May 2007 08:15:16 -0400, John Eells wrote:
>
>>> I am completely naive of "indirect cataloguing". What book should
>>> I read?
>
>- The parameters for DEFINE NONVSAM in z/OS DFSMS Access Method
>Services for Catalogs:
>
>http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/dgt2i25
In <[EMAIL PROTECTED]>, on 05/20/2007
at 03:25 PM, Paul Gilmartin <[EMAIL PROTECTED]> said:
>How fine a granularity do you wish? Should each data set be given a
>distinct symbolic volser for the customer to tailor, with the
>possibility of setting some of them equal? Be aware that what seems
Shane wrote:
On Mon, 2007-05-21 at 00:01 -0500, Paul Gilmartin wrote:
I am completely naive of "indirect cataloguing". What book should
I read?
Init and Tuning ref from memory - maybe look for "indirect volume
support" (or somesuch) references.
See:
- The parameters for DEFINE NONVSAM i
On Mon, 2007-05-21 at 00:01 -0500, Paul Gilmartin wrote:
> Since the RM requires a one-to-one correspondence between target
> zones and the SMPLTS, SMPMTS, SMPSCDS, and SMPSTS, are these
> considered "target" data sets?
Must admit this question had me confused for a while.
Possibly I contributed
On Mon, 21 May 2007 08:08:35 +0200, Robert Bardos wrote:
>>
>> Don't we all - symbolics in sysin (in general) that is,
>> not just the specific case you highlight.
>
>Add to that a feature that most scheduler products have.
>Something like 'substitute off'/'substitute on'.
>
I had assumed that in t
>
> > Damn! I wish JCL symbol substitution could be
> performed in the body of instream UCLIN.
>
> Don't we all - symbolics in sysin (in general) that is,
> not just the specific case you highlight.
>
Add to that a feature that most scheduler products have.
Something like 'substitute off'/'s
On Mon, 21 May 2007 08:03:09 +1000, Shane wrote:
>On Sun, 2007-05-20 at 15:25 -0500, Paul Gilmartin wrote:
>
>Symbolics per "class" of dataset would be a good start; target vs. dlib
>vs. SMPE
>
Since the RM requires a one-to-one correspondence between target
zones and the SMPLTS, SMPMTS, SMPSCDS,
On Sun, 2007-05-20 at 15:25 -0500, Paul Gilmartin wrote:
Tom appears to be falling into a hole I stumble upon a bit when I go to
different customers.
It ain't my shop, and I have to work with the environment as it is.
Were it "my shop", I'd have ACS code in place to accommodate a lot of
the vendor
On Sun, 20 May 2007 14:11:25 -0400, Pinnacle wrote:
>
>- one volume for the SMP installs, no separate volumes for SMP, target, and
>DLIBs. Yeah, I want my DLIB datasets on the same volume as my target
>datasets, sure.
>
How fine a granularity do you wish? Should each data set be given a distinct
On Sun, 2007-05-20 at 14:11 -0400, Pinnacle wrote:
> Compuware uses a brain-dead ISPF dialog to "help" generate JCL for the
> install.
Not just they.
> Now I know why nobody bothers
> reporting these error back to the vendors. You'd never get anything
> installed, so you just push through it
I've been tearing my hair out trying to install ECC, AbendAid, and XPEDITER.
Compuware uses a brain-dead ISPF dialog to "help" generate JCL for the
install. The dialog forgets variables and actually builds JCL that fails.
Some examples:
- one volume for the SMP installs, no separate volumes f
27 matches
Mail list logo
