Re: Why is it still there?

[Shmuel Metz (Seymour J.)]

In
<[EMAIL PROTECTED]>,
on 08/25/2006
   at 04:58 PM, "Hunkeler Peter (KIUB 34)"
<[EMAIL PROTECTED]> said:

>Any program that returns to the operating system by branching  to the
>address it was told when it initially got control is  assumed to have
>completed successfully.

FSVO successfully. In general the caller will look at the return code
in R15. If it's the jobstep task, then the initiator may skip
subsequent steps depending on the value in R15 and the COND keywords
in EXEC statements.

>If the program fails either becaue some OS service it called 
>decided to abnormally end (abend) the program of because the
>programmer decided that in a specific case it should ABEND  (which
>is an MVS service), then and only then does MVS consider the program
>has abnormally ended.

Where programmer includes the authors of IBM and 3rd party libraries
used by the program.

>If you see
> "COMPLETION CODE - SYSTEM=sss USER= REASON=" then
>the program has or has been abnormally ended.
>If sss in nonzero, it was abended by a service routine and sss is
>the hexadecimal abend code. If  is nonzero, the abended was
>coded by the programmer asked for an abend with  the decimal abend
>code  (0-4095).

The user may consider LE and other IBM libraries to be service
routines even though they issue user ABEND's.

-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[Vernooy, C.P. - SPLXM]

Gee man, this thread makes me think of the problem: how many system
programmers does it take to change a lightbulb? Well: an entire forum of
them. The question is answered but still there is a lot to say,
consider, add, contradict, supplied, etc.etc. If the OP is to wait
untill all information has been gathered, then it is clear why IT
projects often run out of their schedule.

As I mentioned before, it is alright to drift off-topic to dig deeper
into certain side-track details, but it would be nice if the subject
were changed accordingly then.

Kees.

"Captain Paralytic" <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> 
> Mickey wrote:
> 
> > Captain Paralytic wrote:
> > > Vernooy, C.P. - SPLXM wrote:
> > >
> > > > Paul,
> > > >
> > > > The third disposition is only taken when the step abends. This
step did
> > > > not abend, so the second disp is taken.
> > > >
> > > > Kees.
> > > >
> > > > <[EMAIL PROTECTED]> wrote in message
> > > > news:<[EMAIL PROTECTED]>...
> > > I had assumed that "Normal completion" was RC=0 and "Abnormal
> > > completion" was a non-zero RC. So Normal completion is anything
apart
> > > from an abend?
> >
> > For the purpose of the DISP parameter, yes.
> >
> > Mickey
> Smashing, thanks Kees and Mickey for your prompt responses.
> 
> I've coded an EXEC PGM=IEFBR14,COND=(0,EQ) with a DISP=(MOD,DELETE) to
> get rid of the dataset on a non-zero return code.
> 


**
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286 
**


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[J R]

ACF2 also does (or did) this I think (I'm not sure). It may have gone away 
when it went to the SAF interface as opposed to ZAPing SVCs.


This is one of the very few justifiable uses of system abend codes by 
non-IBM code.  If you are replacing SVCs 130-133, it makes perfect sense to 
use x82, x83, x84 and x85 abend codes.  Of course, if you can make them 
coincide with the descriptions in the manual, so much the better.  
Appropriately unique reason codes can draw attention to product unique 
situations.




From: "Robert A. Rosenberg" <[EMAIL PROTECTED]>
Reply-To: IBM Mainframe Discussion List 
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Why is it still there?
Date: Sat, 26 Aug 2006 22:31:50 -0400

At 19:57 -0500 on 08/26/2006, =?ISO-8859-1?Q?Tom_Marchant?= wrote about Re: 
Why is it still there?:



If you can find any reference in any manual that says that you should use
_any_ system abend code, I would like to see it.  It has always been my
expectation that if i see a system abend code that it would be documented 
in

the System Codes manual.  I don't remember ever seeing an ISV product that
issues any System abend code.  Does anyone here know of one


I seem to remember that TMS (UCC-1 now CA-1) issues SYSTEM ABENDs from its 
SVC when needed.


ACF2 also does (or did) this I think (I'm not sure). It may have gone away 
when it went to the SAF interface as opposed to ZAPing SVCs.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


_
Call friends with PC-to-PC calling -- FREE   
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[Andy Wood]

On Sat, 26 Aug 2006 19:57:29 -0500, Tom Marchant  wrote:

. . .

>  I don't remember ever seeing an ISV product that
>issues any System abend code.  Does anyone here know of one?
>

It has been a long time since I was anywhere near CA-1, but that certainly 
used to issue 'system' abends based on its SVC numbers.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[Robert A. Rosenberg]

At 19:57 -0500 on 08/26/2006, =?ISO-8859-1?Q?Tom_Marchant?= wrote 
about Re: Why is it still there?:



If you can find any reference in any manual that says that you should use
_any_ system abend code, I would like to see it.  It has always been my
expectation that if i see a system abend code that it would be documented in
the System Codes manual.  I don't remember ever seeing an ISV product that
issues any System abend code.  Does anyone here know of one


I seem to remember that TMS (UCC-1 now CA-1) issues SYSTEM ABENDs 
from its SVC when needed.


ACF2 also does (or did) this I think (I'm not sure). It may have gone 
away when it went to the SAF interface as opposed to ZAPing SVCs.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[Tom Marchant]

On Sat, 26 Aug 2006 17:12:17 -0400, Robert A. Rosenberg <[EMAIL PROTECTED]>
wrote:
>
>I'll have to check the manuals that cover how to wrote you own SVC.
>I'd assume that it will say that you should use a XYY code and lacks
>the warning that "We have appropriated the following codes so you
>can/should not try to use them yourself".

Bad assumption, I think.
>
>While I am looking for documentation, I'll counter with the query of
>"What ABEND codes am I supposed to use if not xyy (x=1-E and yy=My
>SVC Number)?". XYY being an ABEND from SVC-XX seems to be (as you
>stated) the normal (ie: Expected/Assumed Convention) and the few
>non-standard codes that IBM has defined will cause problems for ISV
>Type SVCs (where the User tells the Installer what SVC Number to use)
>if one of the SVCs whose ABEND Codes IBM overlaps is selected. At
>least for User Written SVCs, the coder can work around the IBM ABEND
>Codes if the User wants to use one of the "bad" SVC Numbers.
>
If you can find any reference in any manual that says that you should use
_any_ system abend code, I would like to see it.  It has always been my
expectation that if i see a system abend code that it would be documented in
the System Codes manual.  I don't remember ever seeing an ISV product that
issues any System abend code.  Does anyone here know of one?

Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[Robert A. Rosenberg]

At 20:56 -0500 on 08/25/2006, Tom Marchant wrote about Re: Why is it 
still there?:



On Fri, 25 Aug 2006 21:20:54 -0400, Robert A. Rosenberg <[EMAIL PROTECTED]>
wrote:


You also have to watch out for the Sxyy Abend Codes that are supposed
to belong to user SVCs (SVC 200 - 255 [yy=c8-ff]) but IBM has
Hijacked for non-User-SVCx Purposes. The only valid use I can name is
Fyy for the SVC-yy undefined case (but that still leaves 15 of the 16
possible codes for the user to use unless it is one of the IBM
hijacked Abend Codes in which case the user either needs to not use
that SVC-Number or only use those ABEND Codes IBM has not invalidly
appropriated).


Pretty strong words.  Can you reference any documentation to support your
claim that those system abend coded "belong" to user SVCs?


I'll have to check the manuals that cover how to wrote you own SVC. 
I'd assume that it will say that you should use a XYY code and lacks 
the warning that "We have appropriated the following codes so you 
can/should not try to use them yourself".




While most system abend codes except for S0xx follow the convention that the
'xx' is the SVC that issued the abend, I've never seen any documentation
that said that any system completion codes are reserved for user SVCs.


OOPS: I forgot the S0yy codes so revise my comment above to say 14 of 
16 possible codes.


While I am looking for documentation, I'll counter with the query of 
"What ABEND codes am I supposed to use if not xyy (x=1-E and yy=My 
SVC Number)?". XYY being an ABEND from SVC-XX seems to be (as you 
stated) the normal (ie: Expected/Assumed Convention) and the few 
non-standard codes that IBM has defined will cause problems for ISV 
Type SVCs (where the User tells the Installer what SVC Number to use) 
if one of the SVCs whose ABEND Codes IBM overlaps is selected. At 
least for User Written SVCs, the coder can work around the IBM ABEND 
Codes if the User wants to use one of the "bad" SVC Numbers.




Tom Marchant


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[Tom Marchant]

On Fri, 25 Aug 2006 21:20:54 -0400, Robert A. Rosenberg <[EMAIL PROTECTED]>
wrote:
>
>You also have to watch out for the Sxyy Abend Codes that are supposed
>to belong to user SVCs (SVC 200 - 255 [yy=c8-ff]) but IBM has
>Hijacked for non-User-SVCx Purposes. The only valid use I can name is
>Fyy for the SVC-yy undefined case (but that still leaves 15 of the 16
>possible codes for the user to use unless it is one of the IBM
>hijacked Abend Codes in which case the user either needs to not use
>that SVC-Number or only use those ABEND Codes IBM has not invalidly
>appropriated).

Pretty strong words.  Can you reference any documentation to support your
claim that those system abend coded "belong" to user SVCs?

While most system abend codes except for S0xx follow the convention that the
'xx' is the SVC that issued the abend, I've never seen any documentation
that said that any system completion codes are reserved for user SVCs.

Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[Robert A. Rosenberg]

At 14:46 -0500 on 08/25/2006, =?ISO-8859-1?Q?Peter_Hunkeler?= wrote 
about Re: Why is it still there?:




Usually, Sxxx abends are for system code, user abend for application
code. You can of course code an SD37 abend and confuse everybody.


You also have to watch out for the Sxyy Abend Codes that are supposed 
to belong to user SVCs (SVC 200 - 255 [yy=c8-ff]) but IBM has 
Hijacked for non-User-SVCx Purposes. The only valid use I can name is 
Fyy for the SVC-yy undefined case (but that still leaves 15 of the 16 
possible codes for the user to use unless it is one of the IBM 
hijacked Abend Codes in which case the user either needs to not use 
that SVC-Number or only use those ABEND Codes IBM has not invalidly 
appropriated).


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[Gerhard Postpischil]

J R wrote:

You can of course code an SD37 abend and confuse everybody.

That's not something I would do.


A long, long time ago, a friend of mine protected our system by turning 
on all the password bits in SYS1 DSCBs (before RACF, etc.), without 
actually having passwords for them (and miscellaneous hooks in the 
system to permit normal running, and prevent addition of passwords). We 
also had a utility, used just before and after applying maintenance 
service, to toggle the bits on a volume basis. We also had a member of 
the systems group who repeatedly caused problems; e.g., he applied a PTF 
 to the system even though it wasn't applicable (and we had to restore 
from backup). When he found out he no longer had access to the SYS1 data 
sets, he went to our boss and complained. Per direction, I provided 
documentation on how to run the utility to set/reset the password bits. 
However, whenever he ran, he got 122 & 222 (sans dump), 804, 80A, x37, 
E04, F03, and other weird abends. None of these would have happened if 
he had copied the sample JCL exactly as shown in the writeup!


Gerhard Postpischil
Bradford, VT

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[J R]

You probably mean the fact that the "code type" parameter of the
ABEND macro detemines whether it will be seen as a user or a
system abend, right?


No.  My quibble was with your characterization of system vs. user
as service routine vs. programmer.


Usually, Sxxx abends are for system code, user abend for application
code.


That's better.


You can of course code an SD37 abend and confuse everybody.


That's not something I would do.



From: Peter Hunkeler <[EMAIL PROTECTED]>
Reply-To: IBM Mainframe Discussion List 
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Why is it still there?
Date: Fri, 25 Aug 2006 14:46:17 -0500

>>Any program that returns to the operating system by branching
>>to the address it was told when it initially got control is
>>assumed to have completed successfully.
>
>SVC 3 = normal completion
>SVC 13 = abnormal completion

Absolutely correct but programs usually don't issue SVC3 directly
but rather exit with a "BR R14". R14 points to an "SVC 3" instruction
when programs get control from MVS.

>That's not entirely accurate.  It depends how the SVC 13 is issued.

You probably mean the fact that the "code type" parameter of the
ABEND macro detemines whether it will be seen as a user or a
system abend, right?

Since the OP's question seemed to more of a beginner's type of
question, I didn't want to go into more (assembler) details.

Usually, Sxxx abends are for system code, user abend for application
code. You can of course code an SD37 abend and confuse everybody.

Peter Hunkeler
Credit Suisse

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


_
Check the weather nationwide with MSN Search: Try it now!  
http://search.msn.com/results.aspx?q=weather&FORM=WLMTAG


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[Peter Hunkeler]

>>Any program that returns to the operating system by branching
>>to the address it was told when it initially got control is
>>assumed to have completed successfully.
>
>SVC 3 = normal completion
>SVC 13 = abnormal completion

Absolutely correct but programs usually don't issue SVC3 directly 
but rather exit with a "BR R14". R14 points to an "SVC 3" instruction
when programs get control from MVS.

>That's not entirely accurate.  It depends how the SVC 13 is issued.

You probably mean the fact that the "code type" parameter of the 
ABEND macro detemines whether it will be seen as a user or a 
system abend, right? 

Since the OP's question seemed to more of a beginner's type of 
question, I didn't want to go into more (assembler) details.

Usually, Sxxx abends are for system code, user abend for application
code. You can of course code an SD37 abend and confuse everybody.

Peter Hunkeler
Credit Suisse

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[J R]

Any program that returns to the operating system by branching
to the address it was told when it initially got control is
assumed to have completed successfully.


SVC 3 = normal completion
SVC 13 = abnormal completion


If sss in nonzero, it was abended by a service routine and
sss is the hexadecimal abend code. If  is nonzero, the
abended was coded by the programmer asked for an abend with
the decimal abend code  (0-4095).


That's not entirely accurate.  It depends how the SVC 13 is issued.

One problem here is of terminology.  "Return code", "condition code" and 
"completion code" tend to be used interchangably.




From: "Hunkeler Peter (KIUB 34)" <[EMAIL PROTECTED]>
Reply-To: IBM Mainframe Discussion List 
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Why is it still there?
Date: Fri, 25 Aug 2006 16:58:27 +0200

Any program that returns to the operating system by branching
to the address it was told when it initially got control is
assumed to have completed successfully.

The return code does not matter from MVS's point of view.
It does of course from the application's point of view, since
it tells the user whether the program could do its task as it
was requested.

If the program fails either becaue some OS service it called
decided to abnormally end (abend) the program of because the
programmer decided that in a specific case it should ABEND
(which is an MVS service), then and only then does MVS
consider the program has abnormally ended.

If you see
 "STEP WAS EXECUTED - COND CODE "
on the step end message, the program succeeded in MVS's eyes.
 is the decimal return code from the program and is in
the range of 0 - 4095

If you see
 "COMPLETION CODE - SYSTEM=sss USER= REASON="
then the program has or has been abnormally ended.
If sss in nonzero, it was abended by a service routine and
sss is the hexadecimal abend code. If  is nonzero, the
abended was coded by the programmer asked for an abend with
the decimal abend code  (0-4095).



Peter Hunkeler
CREDIT SUISSE

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


_
All-in-one security and maintenance for your PC.  Get a free 90-day trial!   
http://www.windowsonecare.com/trial.aspx?sc_cid=msn_hotmail


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[Hunkeler Peter (KIUB 34)]

Any program that returns to the operating system by branching 
to the address it was told when it initially got control is 
assumed to have completed successfully. 

The return code does not matter from MVS's point of view. 
It does of course from the application's point of view, since 
it tells the user whether the program could do its task as it 
was requested.

If the program fails either becaue some OS service it called 
decided to abnormally end (abend) the program of because the
programmer decided that in a specific case it should ABEND 
(which is an MVS service), then and only then does MVS
consider the program has abnormally ended.

If you see 
 "STEP WAS EXECUTED - COND CODE " 
on the step end message, the program succeeded in MVS's eyes. 
 is the decimal return code from the program and is in
the range of 0 - 4095

If you see
 "COMPLETION CODE - SYSTEM=sss USER= REASON="
then the program has or has been abnormally ended.
If sss in nonzero, it was abended by a service routine and
sss is the hexadecimal abend code. If  is nonzero, the
abended was coded by the programmer asked for an abend with 
the decimal abend code  (0-4095).



Peter Hunkeler
CREDIT SUISSE

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[Vernooy, C.P. - SPLXM]

"Captain Paralytic" <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> 
> Vernooy, C.P. - SPLXM wrote:
> 
> > Paul,
> >
> > The third disposition is only taken when the step abends. This step
did
> > not abend, so the second disp is taken.
> >
> > Kees.
> >
> > <[EMAIL PROTECTED]> wrote in message
> > news:<[EMAIL PROTECTED]>...
> I had assumed that "Normal completion" was RC=0 and "Abnormal
> completion" was a non-zero RC. So Normal completion is anything apart
> from an abend?
> 

ABEND is short for Abnormal End, if the job did not end abnormally
(abend), it must have ended normally.

Kees.


**
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286 
**


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Why is it still there?

[Vernooy, C.P. - SPLXM]

Paul,

The third disposition is only taken when the step abends. This step did
not abend, so the second disp is taken.

Kees.

<[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> The job step below failed with RC = 12. I know why it failed so that
> part's OK. However, since the step did not complete normally, I would
> have expected the DISP parameters to have caused the newly created
> dataset HLQ.OUTDS.CSD to have been deleted.
> 
> My question is: Why was it retained?
> 
> //*
> //DFHCSDUP EXEC PGM=DFHCSDUP,REGION=4M
> //STEPLIB  DD  DSN=SYSCICS.OS0CICS.SDFHLOAD,DISP=SHR
> // DD  DSN=SYS1.SCEERUN,DISP=SHR
> //DFHCSD  DD  DSN=CICS.GLOBAL.CICS620.DFHCSD,DISP=SHR
> //*CBDOUT REQUIRED IF EXTRACTING DATA
> //CBDOUT  DD  DSN=HLQ.OUTDS.CSD,
> //DISP=(NEW,CATLG,DELETE),
> //SPACE=(CYL,(10,10),RLSE),
> //DCB=(NU.MODEL.DSCB,
> //RECFM=FB,LRECL=80,BLKSIZE=0)
> 
> Any ideas?
> 
> TIA
> 


**
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286 
**


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html