FDL is :-
ALPHA_ROB$$ typ dcllog.fdl
TITLE "DCLLOG Output File"
IDENT " 3-JUN-1999 15:43:26 OpenVMS FDL Editor"
SYSTEM
SOURCE "OpenVMS"
FILE
ALLOCATION 150000
BEST_TRY_CONTIGUOUS yes
EXTENSION 15000
ORGANIZATION sequential
RECORD
BLOCK_SPAN yes
CARRIAGE_CONTROL carriage_return
FORMAT variable
SIZE 100
My original post isn't to try and get help on fixing my RMS problem though,
I'm capable of doing that using other tools/languages. I was (and still am)
worried about what Perl does when it encounters errors, either file or
otherwise.
Remember, you're talking to someone who's used to programming in DCL, which
will almost always tell you when it encounters problems. Now I've begun using
this 'new' language Perl, I expect it to act similarly. When it doesn't, I
need to find out..
- Why?
- How do I make it act correctly, i.e. trap errors?
- What other problems am I going to encounter, because Perl doesn't report
errors?
These may seem simplistic or even stupid questions if your used to Perl, but
for a novice, these are the fundamentals for learning how a language works.
Until I know the 'gotchas', I cannot trust what I'm writing and the results I
get out.
Rob.
-----Original Message-----
From: Craig Berry [mailto:[EMAIL PROTECTED]
Sent: 04 November 2003 22:23
To: Atkinson, Robert
Cc: [EMAIL PROTECTED]
Subject: RE: File Read Error
On Tuesday, November 04, 2003, at 03:40AM, Atkinson, Robert
<[EMAIL PROTECTED]> wrote:
>Craig,
> can you give me an idea where this should go in my original code.
>Where will Perl jump to if the <INFILE> fails?
As Jordan suggested, I believe the loop you have will exit on failure. As
has also been suggested, I think you should consider more traditional methods
of file analysis and manipulation instead of or alongside of Perl. Perl for
this purpose is really just a wrapper around the C RTL. Stream files with
overlong records can sometimes be easier to deal with in C/Perl than in other
languages, but unless I'm forgetting something I don't think you've told us
whether this is a stream file or not. ANALYZE/RMS/FDL would give folks a
much less speculative sense of what you're actually facing.
>
>-----Original Message-----
>From: Craig A. Berry [mailto:[EMAIL PROTECTED]
>Sent: 03 November 2003 14:21
>To: Atkinson, Robert; [EMAIL PROTECTED]
>Subject: RE: File Read Error
>
>
>At 9:04 AM -0500 11/3/03, Henderson, Jordan (Contractor) (DAASC) wrote:
>>The <> operator just stops on EOF or error.
>>
>>You have to explicitly access the error codes. Try printing the system
>variable
>>$! at this point.
>
>Or $^E, which should give you the full VMS error message.
***********************************************************************************
The Random House Group Ltd.
Registered address 20 Vauxhall Bridge Road,
London
SW1V 2SA
http://www.randomhouse.co.uk
Telephone +44 (0) 20 7840 8400.
Any opinions expressed in email are those of the individual and not necessarily those
of the company. This email and any files transmitted with it are confidential and
solely for the use of the intended recipient or entity to who they are addressed. It
may contain material protected by attorney-client privilege. If you are not the
intended recipient, or a person responsible for delivering to the intended recipient,
be advised that you have received this email in error and that any use is strictly
prohibited.
Random House Group IT Department helpdesk +44 (0) 1206 255900.
***********************************************************************************
