Re: AIX ASSIGN problems
From: Frederico Fonseca (real-email-in-msg-spam_at_email.com)
Date: 10/21/03
- Next message: Daniel Klopfer: "Re: Vutil Automation"
- Previous message: Vince Coen: "Re: Micro-Focus Cobol/ Contract/ NC"
- In reply to: bspiegel00: "AIX ASSIGN problems"
- Next in thread: William M. Klein: "Re: AIX ASSIGN problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 21 Oct 2003 21:45:57 +0100
On Tue, 21 Oct 2003 14:45:12 -0400, bspiegel00
<member12146@dbforums.com> wrote:
>
>Hello, friends.
>
>We're trying to compile and run our first COBOL programs on AIX (we've
>done it endlessly on MVS). As you might imagine, we're running into
>some problems, probably from cluelessness -- can't fix or prevent what
>you don't know enough to look for. We're hoping that someone out
>there can help.
It would help if you told us which COBOL brand and version you are
using.
>From the error messages I presume it is AIX COBOL, but I am probably
wrong.
>
>
>We're using the ASSIGN clause to tie FD statements to AIX environmental
>variables in the program:
>
>FILE-CONTROL.
>
> SELECT O-CLM0110-XTRCT-FILE ASSIGN TO CLM0100.
> SELECT FINC-RECON-FILE ASSIGN TO FINRECON.
> SELECT ERROR-REPORT-FILE ASSIGN TO ERRRPT.
> SELECT ICN-INPUT-FILE ASSIGN TO ICNINPT.
Some of the COBOL's I have worked with will allow this only if the
assigned variable is within quotes. e.g. ASSIGN TO "CLM0100".
>
>In the execution of the load module that results from a clean bldapp,
>we've got these environmental variables set up:
>
>export CREATOR=udbtest1
>export DIR=/amirs/eds/dev/test/data
>export EXE=/amirs/eds/dev/test/copy
>export OUT=/amirs/eds/dev/test/out
>export ICNINPT="< cat ${DIR}/amirxicn.txt"
>export CLM0100=$DIR/clm0110_clm0110.txt
>export FINRECON=$DIR/clm0110_finrecon.txt
>export ERRRPT=$DIR/clm0110_errrpt.txt
Your users guide/language reference manual should say if this is
possible.
ACUCOBOL does and I think that MICROFOCUS also allows this, but not
sure they allow it using environment variables.
>
>We verify the environmental variables are accurately set up by executing
>env just prior to executing the load module:
>
>env > ${OUT}/clm0110.out
>
>We then move to the executable directory:
>
>cd ${EXE}
>
>And then we execute the load module:
>
>clm0110 >> ${OUT}/clm0110.out
>
>If you're sharper than us -- and you must be -- you know we're failing.
>Here are the gory details -- indicating a file access error for our
>input file, except it's already got all permissions turned on:
>
>IWZ200S Error detected during OPEN for file 'ICN-INPUT-FILE'. File
>status is:
>
> 91. File system indicated: Not authorized to File.
>
> Message routine called from offset 0x38 of routine
> iwzWriteERRmsg.
>
> iwzWriteERRmsg called from offset 0x490 of routine
> _iwzCallUseProc.
>
> _iwzCallUseProc called from offset 0x10a8 of routine
> _iwzSeqOpen.
>
> _iwzSeqOpen called from offset 0x4cc of routine
> _iwzGenericOpen.
>
> _iwzGenericOpen called from offset 0x14c4 of routine CLM0110.
>
>IWZ901S Program exits due to severe or critical error.
>
>
>Any idea what we're doing wrong?
No following the manual??
>
>
>
>Thanks for the help.
>
>
>
>Barry Spiegel
>
>EDS
>
>Phoenix, AZ
>
>barry.spiegel@eds.com
Frederico Fonseca
ema il: frederico_fonseca at syssoft-int.com
- Next message: Daniel Klopfer: "Re: Vutil Automation"
- Previous message: Vince Coen: "Re: Micro-Focus Cobol/ Contract/ NC"
- In reply to: bspiegel00: "AIX ASSIGN problems"
- Next in thread: William M. Klein: "Re: AIX ASSIGN problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
