[EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]...
In a recent note, Mark Thomen said:
Date: Fri, 6 Jan 2006 12:13:52 -0800
Will it continue to allow invalid data set names to be
deleted/uncatalogued even when syntax checking is enabled?
No - if an invalid data
On Fri, Jan 06, 2006 at 12:13:52PM -0800, Mark Thomen ([EMAIL PROTECTED]) wrote:
[snip]
Will it continue to allow invalid data set names to be
deleted/uncatalogued even when syntax checking is enabled?
No - if an invalid data set name is in a catalog, you'll have to use other
methods to
On Mon, Jan 09, 2006 at 08:37:14AM -0800, Mark Thomen ([EMAIL PROTECTED]) wrote:
However, we recognized the problem a few years ago (because
of a particular product that was creating invalid names) and that's why we
added the support to Catalog to prevent invalid data set names from being
Leonard Woren [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]...
On Fri, Jan 06, 2006 at 12:13:52PM -0800, Mark Thomen ([EMAIL PROTECTED])
wrote:
[snip]
Will it continue to allow invalid data set names to be
deleted/uncatalogued even when syntax checking is enabled?
No - if
In a recent note, Leonard Woren said:
Date: Mon, 9 Jan 2006 10:42:30 -0800
On Mon, Jan 09, 2006 at 08:37:14AM -0800, Mark Thomen ([log in to unmask])
wrote:
However, we recognized the problem a few years ago (because
of a particular product that was creating invalid names) and
The semantics confuses me. Why was anything ever permitted
but deemed invalid?
read that as not conforming to documented syntax rules for cataloged
datasets.
Back in the days of CVOL catalogs, the rules were enforced almost by
default, since a CVOL is a hierarchical structure, where each
In a recent note, Bruce Black said:
Date: Fri, 6 Jan 2006 10:04:44 -0500
Back in the days of CVOL catalogs, the rules were enforced almost by
default, since a CVOL is a hierarchical structure, where each level in
the hierarchy corresponds to one index level in the dataset name (thus
Bruce Black wrote:
Back in the days of CVOL catalogs, the rules were enforced almost by
default, since a CVOL is a hierarchical structure, where each level in
the hierarchy corresponds to one index level in the dataset name (thus
the name index level). The max size of each level was 8
In a recent note, Gilbert Saint-Flour said:
Date: Fri, 6 Jan 2006 10:48:07 -0500
If I'm not mistaken, CVAF seems to behave similarly when the VTOC is
indexed. You can allocate a data set with any dsname you want on a
DASD volume that doesn't have an indexed VTOC, but when there's
Gilbert Saint-Flour wrote:
Bruce Black wrote:
Back in the days of CVOL catalogs, the rules were enforced almost by
default, since a CVOL is a hierarchical structure, where each level in
the hierarchy corresponds to one index level in the dataset name (thus
the name index level). The max
That strikes me as a foolish decision, imposing unnecessary
constraints on the customer. Was there any rationale for it
other than developer laziness?
Boy, Gil, you sure know how to make friends. Remember that Mark is the
developer (or at least the architect).
--
Bruce A. Black
Senior
At 09:18 -0700 on 01/06/2006, Paul Gilmartin wrote about Re: Invalid
DSN in Catalog:
Did CVOL ever impose a five-level limit, or was this an urban
legend?
It had a 22 level limit - 21 single character levels, one 1 or 2
character level, plus 21 inter-level periods for a total file name
Shmuel Metz , Seymour J. [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]...
In [EMAIL PROTECTED], on 01/03/2006
at 11:26 AM, Binyamin Dissen [EMAIL PROTECTED] said:
Something builds it.
Are you sure about that? Have you seen an SIOT for a dynamically
allocated data set?
Shmuel Metz , Seymour J. [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]...
In [EMAIL PROTECTED], on 01/03/2006
at 11:26 AM, Binyamin Dissen [EMAIL PROTECTED] said:
Something builds it.
Are you sure about that? Have you seen an SIOT for a dynamically
allocated data set?
Oh -
In a recent note, Mark Thomen said:
Date: Thu, 5 Jan 2006 12:27:01 -0800
Oh - and I forgot to mention: syntax checking is automatically enabled
beginning in HDZ11G0 (z/os 1.3), unless the installation disables it. So
no invalid data set names should get cataloged.
Will it
On Wed, 4 Jan 2006 12:16:39 -0500 Shmuel Metz (Seymour J.)
[EMAIL PROTECTED] wrote:
:In [EMAIL PROTECTED], on 01/03/2006
: at 11:26 AM, Binyamin Dissen [EMAIL PROTECTED] said:
:Something builds it.
:Are you sure about that? Have you seen an SIOT for a dynamically
:allocated data set?
I have
PROTECTED] On Behalf
Of Shmuel Metz (Seymour J.)
Sent: Wednesday, January 04, 2006 11:17 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Invalid DSN in Catalog
In [EMAIL PROTECTED], on 01/03/2006
at 11:26 AM, Binyamin Dissen [EMAIL PROTECTED] said:
Something builds it.
Are you sure about that? Have you seen
On Mon, 2 Jan 2006 17:35:37 -0500 Shmuel Metz (Seymour J.)
[EMAIL PROTECTED] wrote:
:In [EMAIL PROTECTED], on 12/30/2005
: at 11:35 AM, Paul Gilmartin [EMAIL PROTECTED] said:
:Is there, then, no SIOT for dynamically allocated data sets?
:Not that I'm aware of; I believe that the relevant data
In [EMAIL PROTECTED], on 12/30/2005
at 11:35 AM, Paul Gilmartin [EMAIL PROTECTED] said:
Is there, then, no SIOT for dynamically allocated data sets?
Not that I'm aware of; I believe that the relevant data are in the
DSAB.
Does SVC 99 at some point invoke Interpreter code to construct a
In [EMAIL PROTECTED], on 12/29/2005
at 01:57 PM, Paul Gilmartin [EMAIL PROTECTED] said:
Are you saying, then, that unlike Assembler and the TSO parse
utility, both of which remove quotes, the JCL C/I passes them on to
the Allocation component which sets the SIOTDSQU bit and removes the
quotes?
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of R.S.
Chase, John wrote:
Doing some year-end cleanup and encountered a catalog entry for a
non-existent dataset: HLQ.MLQ.LLQ(0) (yes, the parentheses were
part of the DSN). While I was able to delete the
Apparently not via IDCAMS DEFINE
I thought that you might be able to do it in JCL, putting the dsname in
quotes, e.g.,
//STEP1EXEC PGM=IEFBR14
//TEST DD DSN='BAB.TEST.TEST(0)',UNIT=SYSALLDA,
// SPACE=(TRK,1),DISP=(,CATLG),VOL=SER=SH20C0
In a recent note, Bruce Black said:
Date: Thu, 29 Dec 2005 09:52:05 -0500
However, I know from experience that names which do not conform to the
normal naming convention can be cataloged using the CATALOG/CAMLST
macros in an assembler program. ...
It's a blunder in design
//STEP1EXEC
PGM=IEFBR14
//TEST DD DSN='BAB.TEST.TEST
(0)',UNIT=SYSALLDA,
// SPACE=(TRK,1),DISP=
(,CATLG),VOL=SER=SH20C0
NAMED IN QUOTES, IS NOT ELIGIBLE TO BE SMS-
MANAGED
-teD
Me? A skeptic? I trust you have proof!
NAMED IN QUOTES, IS NOT ELIGIBLE TO BE SMS-
MANAGED
Yes, that is what you get if the dataset is SMS-managed. In my example,
it was not SMS. Of course, that is a function of local ACS routines, etc.
--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
In a recent note, Ted MacNEIL said:
Date: Thu, 29 Dec 2005 12:12:42 -0500
Hmmm. I notice your timestamp is no longer flashing midnight
like a lobotomized VCR. Hasn't been since Nov. 10.
//STEP1EXEC
PGM=IEFBR14
//TEST DD DSN='BAB.TEST.TEST
(0)',UNIT=SYSALLDA,
//
29, 2005 2:18 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Invalid DSN in Catalog
In a recent note, Dan said:
Date: Thu, 29 Dec 2005 14:45:41 -0500
The SIOT contains a Quoted Data Set Indicator, SIOTDSQU...
change id JBB2223 93/05/13.
It's been around a while.
And how does this get set
In a recent note, Binyamin Dissen said:
Date: Thu, 29 Dec 2005 22:12:47 +0200
: 10.39.42 JOB08819 IEF452I SMSNAME - JOB NOT RUN - JCL ERROR
:But how does SMS know the JCL text contained quotes? Doesn't
:the JCL converter strip them off and use only the interior content
:as the
On Thu, 29 Dec 2005 13:43:06 -0700 Paul Gilmartin [EMAIL PROTECTED]
wrote:
:In a recent note, Binyamin Dissen said:
: Date: Thu, 29 Dec 2005 22:12:47 +0200
: : 10.39.42 JOB08819 IEF452I SMSNAME - JOB NOT RUN - JCL ERROR
: :But how does SMS know the JCL text contained quotes?
In a recent note, Wayne Driscoll said:
Date: Thu, 29 Dec 2005 14:32:35 -0600
The first form, is clearly NOT quoted, and never appears to be. In order
for it to be quoted, the quotes would have to be the data area passed to SVC
99, ie.
DSNAMEDCCL44'''MY.DATA.SET'''
In
On Thu, 29 Dec 2005 22:52:32 +0200, Binyamin Dissen [EMAIL PROTECTED] wrote:
I would like to see the JCL and SYSMSGS from that job.
(sent privately)
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
On Thu, 29 Dec 2005 15:04:58 -0600 Paul Gilmartin [EMAIL PROTECTED]
wrote:
:On Thu, 29 Dec 2005 22:52:32 +0200, Binyamin Dissen [EMAIL PROTECTED] wrote:
:I would like to see the JCL and SYSMSGS from that job.
Interesting.
I tested with a single index, 'ABC*DEF', which caused the mount
Hi, All,
Doing some year-end cleanup and encountered a catalog entry for a
non-existent dataset: HLQ.MLQ.LLQ(0) (yes, the parentheses were part of
the DSN). While I was able to delete the entry by specifying HLQ.MLQ.*
for the entryname in the IDCAMS DELETE NOSCRATCH command, I'm curious how
Chase, John wrote:
Hi, All,
Doing some year-end cleanup and encountered a catalog entry for a
non-existent dataset: HLQ.MLQ.LLQ(0) (yes, the parentheses were part of
the DSN). While I was able to delete the entry by specifying HLQ.MLQ.*
for the entryname in the IDCAMS DELETE NOSCRATCH
R.S. wrote:
Someone provided DSN in apostrophes. Been there, seen that, even 9+
character qualifiers.
|Command - Enter / to select action Message
Volume
| Tracks % XT Device Dsorg Recfm Lrecl Blksz CreatedExpires
Referred
35 matches
Mail list logo
