date:20180525

Re: empty KSDS behavior - why?

2018-05-25 Thread Mike Schwab

I remember working with HSM migration control datasets a few years
ago.  Even for that you had to load a high key value dummy record
before using the dataset.

On Fri, May 25, 2018 at 7:20 PM, Frank Swarbrick
 wrote:
> Pointless issue of the day.  This has bothered me for 20 years.  I figured 
> its about time I ask, why?  Why does an "empty" KSDS (a KSDS that has never 
> been "loaded") have what seems to be to be a "special" behavior, one that is 
> different than a KSDS that had records but no longer has any (all records 
> have been deleted).
>
> For example, if a file in this "never loaded" state is opened for input by 
> IDCAMS you get this:
>
>  PRINT INFILE(CCMIGR)
> IDC3300I  ERROR OPENING DVFJS.CCARD.CCMIGRX
> IDC3351I ** VSAM OPEN RETURN CODE IS 160
> IDC0005I NUMBER OF RECORDS PROCESSED WAS 0
>
> where
> 160
> The operands specified in the ACB or GENCB macro are
> inconsistent with each other or with the information in the
> catalog record. This error can also occur when the VSAM
> cluster being opened is empty.
>
> If opened by SORT (DFSORT)
> IEC161I 
> 072-053,DEFVSAM,PRINT1,CCMIGR,,,DVFJS.CCARD.CCMIGRX,DVFJS.CCARD.CCMIGRX.DATA,CATALOG.USERCAT.PPCAT
>
> where
> IEC161I (072)
>
>   Specific information for this return code: The data set was empty, but the 
> ACB (access method control block) for the data set indicated that it was 
> being opened for input only.
>
> System action
>
>   OPEN processing ends for the data set. The error flag (ACBERFLG) in the ACB 
> (access method block) for the data set is set to 160 (X'A0').
>
>
> When opened by a COBOL program, you get file status 35 (An OPEN statement 
> with the INPUT, I-O, or EXTEND phrase was attempted on a non-optional file 
> that was unavailable.), unless you declare it as OPTIONAL, in which case you 
> get file status 05 (An OPEN statement was successfully executed, but the 
> referenced optional file was unavailable at the time the OPEN statement was 
> executed. The file had been created if the open mode was I-O or EXTEND.)
>
> Is this "feature" supposed to be helpful in some obscure edge case?  Or is it 
> simply always annoying?
>
> The OPTIONAL solution in COBOL is generally how we get around this issue, 
> rather than loading a dummy record or something.  But why?  Why, why, why 
> does this behavior even exist?
>
> Frank
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Potter (was: CLIP?)

2018-05-25 Thread Paul Gilmartin

On Fri, 25 May 2018 19:47:47 -0500, Edward Gould  wrote:
>
>What we did use from potter was their printer. All the programmers seem to 
>love it as the page size was 8 1/2 by 11.
>I do not remember specifically anything wrong with it although I think it got 
>used heavily. It may have had more down time, I don’t remember.
>
Laser?  Impact?  Matrix?  Other (specify)?  Landscape?  Portrait?  Character 
pitch?
What year?

>All I know is that one day it was there and the next day the 1403 was back.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: empty KSDS behavior - why?

2018-05-25 Thread Paul Gilmartin

On Sat, 26 May 2018 00:20:34 +, Frank Swarbrick wrote:

>Pointless issue of the day.  This has bothered me for 20 years.  I figured its 
>about time I ask, why?  Why does an "empty" KSDS (a KSDS that has never been 
>"loaded") have what seems to be to be a "special" behavior, one that is 
>different than a KSDS that had records but no longer has any (all records have 
>been deleted).
> 
I suppose it's like formatting a disk: no VTOC is different from an empty VTOC.
But, yes, Why‽  Why does SMP/E require me to REPRO GIMZPOOL?  Why isn't
this embedded in DEFINE CLUSTER?

How do you create your KSDS?  IDCAMS?  Other (specify)

At least nowadays SMS properly terminates a NEW PS data set.  How many decades
did that take?

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: CLIP?

2018-05-25 Thread Edward Gould

> On May 25, 2018, at 1:34 PM, Seymour J Metz  wrote:
> 
> Have you used Potter tape drives in that time frame? If not, I don't see any 
> reasonable argument that you could make.
My mind is cloudy here so I can’t remember anything during that time frame. At 
the time the boss was looking at automatic tape mount products and not a one 
would have worked in our environment.
No, we did not use any of their tape drives. 
What we did use from potter was their printer. All the programmers seem to love 
it as the page size was 8 1/2 by 11.
I do not remember specifically anything wrong with it although I think it got 
used heavily. It may have had more down time, I don’t remember.
All I know is that one day it was there and the next day the 1403 was back.

Ed


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: smp/e question - PTF relinks, but missing CSECTs.

2018-05-25 Thread Edward Gould

> On May 25, 2018, at 12:39 PM, Jesse 1 Robinson  
> wrote:
> 
> I'm sympathetic to the argument that new stuff should be investigated, but 
> the problem is whether that really happens in practice. We've all met the 
> sysprog who meticulously codes parameter defaults as a kind of in-your-face 
> documentation so that 'we will all know' what's happening. Then years later 
> the defaults change, but the user-coded list does not get updated. Call me 
> Pollyanna, but I'm willing to trust the latest default.
> 
> As for getting inconsistent results, I suspect that SMP/E results can be 
> influenced by the particular mix of elements being processed in a given run. 
> That is, applying SYSMOD-A and SYSMOD-B in the same step might uncover a 
> sinkhole that applying one sysmod or the other alone would not. This problem 
> is very difficult to detect in development and may require a lot of customer 
> activity to unearth. 
> 
> .
Jess1,
*YEARS* ago with a well known vendor I was trying to apply a zap (gotten in 
Hardcopy from the vendor) the module was right but the csect did not exist in 
the module flushed the zap, I called the vendor and the person I talked to 
started to argue with me about how I coded the zap. I was annoyed and said fine 
I will fax you the output. I faxed him the sheet of paper.. I did not hear back 
from him in an hour so I called him. He said I had coded the zap wrong, I 
looked at the zap again because I do not miscode zaps. I did this on the phone 
with him. I said the first column is blank and then the word "name” and then 
there is the module name and a blank and the csect name,  the rest of the card 
out to 72 is blank. What is wrong with it? He said you must be a beginner you 
never code zap statements like that. I said EXCUSE me that is how a the first 
zap statement is coded, I do this daily with another vendor and that is by the 
book how its done.  He told me I was wrong and not to bother him again. I said 
what? He hung the phone up on me. I went to the boss and explained to him what 
had transpired and he took a look at my zap statements and he said OK we will 
get him on the line. The guy hung up the phone and soon as he heard the 
company. My boss called the marketing rep and explained what was going on, the 
marketing rep followed the top-down chart as to who the guys boss was. 5 
minutes later we get a call from the guys boss and explains that the guy had a 
bad day. We explained the situation and he said what you are telling me you are 
correct, let me check with another technician he puts us on hold (with lousy 
music on top of it). The technician gets back on the the phone and said there 
was a typo on the sheet and its being faxed to all the customers as we speak. I 
said OK, but the treatment I got from this other technician was just wrong and 
a customer should never be treated that way. He said he will take it up with 
his management. My boss was surprised at me speaking up like I did, but I was 
pissed. The next day I called in with a small question on a wording of a zap 
and what sequence it was supposed to go on. A technician got on and I asked the 
question and he said he was happy we had caught the issue. I said OK thank you. 
He said was I going to report him? I said no why should I, you handled the call 
correctly. He said the technician I had talked to yesterday was fired.

 

> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler 
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-543-6132 Office ⇐=== NEW
> robin...@sce.com 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Pointless issue of the day. This has bothered me for 20 years. I figured its
about time I ask, why? Why does an "empty" KSDS (a KSDS that has never been
"loaded") have what seems to be to be a "special" behavior, one that is
different than a KSDS that had records but no longer has any (all records have
been deleted).

For example, if a file in this "never loaded" state is opened for input by
IDCAMS you get this:

PRINT INFILE(CCMIGR)
IDC3300I ERROR OPENING DVFJS.CCARD.CCMIGRX
IDC3351I ** VSAM OPEN RETURN CODE IS 160
IDC0005I NUMBER OF RECORDS PROCESSED WAS 0

where
160
The operands specified in the ACB or GENCB macro are
inconsistent with each other or with the information in the
catalog record. This error can also occur when the VSAM
cluster being opened is empty.

If opened by SORT (DFSORT)
IEC161I
072-053,DEFVSAM,PRINT1,CCMIGR,,,DVFJS.CCARD.CCMIGRX,DVFJS.CCARD.CCMIGRX.DATA,CATALOG.USERCAT.PPCAT

where
IEC161I (072)

Specific information for this return code: The data set was empty, but the
ACB (access method control block) for the data set indicated that it was being
opened for input only.

System action

OPEN processing ends for the data set. The error flag (ACBERFLG) in the ACB
(access method block) for the data set is set to 160 (X'A0').

When opened by a COBOL program, you get file status 35 (An OPEN statement with
the INPUT, I-O, or EXTEND phrase was attempted on a non-optional file that was
unavailable.), unless you declare it as OPTIONAL, in which case you get file
status 05 (An OPEN statement was successfully executed, but the referenced
optional file was unavailable at the time the OPEN statement was executed. The
file had been created if the open mode was I-O or EXTEND.)

Is this "feature" supposed to be helpful in some obscure edge case? Or is it
simply always annoying?

The OPTIONAL solution in COBOL is generally how we get around this issue,
rather than loading a dummy record or something. But why? Why, why, why does
this behavior even exist?

58 matches

Mail list logo