Re: Problems w/ CBL_* Routines On NFS Mounts

I have run into the same problem.  I will post what I find.  Does anyone
have the definition for the 14605 return code?

Jason

I am not sure if my problem is the same as yours except for the error code
14605.

What I did was place a " around each file name.

STRING """           DELIMITED BY SIZE
WS-INPUT-PATH DELIMITED BY SPACE
WS-FILE-NAME  DELIMITED BY "   "
"""           DELIMITED BY SIZE
INTO WS-CBL-FILE-NAME-1

STRING """           DELIMITED BY SIZE
WS-OUTPUT-PATH DELIMITED BY SPACE
WS-FILE-NAME  DELIMITED BY "   "
"""           DELIMITED BY SIZE
INTO WS-CBL-FILE-NAME-2

CALL "CBL_COPY_FILE" USING WS-CBL-FILE-NAME-1
WS-CBL-FILE-NAME-2
RETURNING WS-CBL-RETURN-STATUS.


Hope this helps.

-Jason

I am not sure if my problem is the same as yours except for the error code
14605.

What I did was place a " around each file name.

STRING """           DELIMITED BY SIZE
WS-INPUT-PATH DELIMITED BY SPACE
WS-FILE-NAME  DELIMITED BY "   "
"""           DELIMITED BY SIZE
INTO WS-CBL-FILE-NAME-1

STRING """           DELIMITED BY SIZE
WS-OUTPUT-PATH DELIMITED BY SPACE
WS-FILE-NAME  DELIMITED BY "   "
"""           DELIMITED BY SIZE
INTO WS-CBL-FILE-NAME-2

CALL "CBL_COPY_FILE" USING WS-CBL-FILE-NAME-1
WS-CBL-FILE-NAME-2
RETURNING WS-CBL-RETURN-STATUS.


Hope this helps.

-Jason

When I have looked up return codes I have never been able to determine what
a specific code means.  The only thing I could find out was that anything
other than a "00" return code is a problem.

I have checked the microfocus web site and on the internet and have never
found a listing of the return codes.

"Jason_Thomas" <jthomas@medata.com> wrote in message
 news:97891f2a1e9389cd8d597da17e7eba49@lo
calhost.talkaboutprogramming.com...
> I have run into the same problem.  I will post what I find.  Does anyone
> have the definition for the 14605 return code?
>
> Jason
>

I don't know if this will help or not, but at:
http://supportline.microfocus.com/s...ndx
.htm

under the topic

"Interpreting the return code as a file status code"

it says,

"If any of the routines

CBL_CHECK_FILE_EXIST
CBL_COPY_FILE
CBL_CREATE_FILE
CBL_DELETE_FILE
CBL_OPEN_FILE
CBL_READ_FILE
CBL_RENAME_FILE
CBL_WRITE_FILE
CBL_CHANGE_DIR
CBL_CREATE_DIR
CBL_DELETE_DIR
CBL_READ_DIR

fails, the RETURN-CODE register contains a file status value indicating the
failure. This file status is always the standard ANSI'74 file status value. 
If
no ANSI'74 file status is defined for the error, an extended file status is
returned (9/nnn where nnn is the run-time system error number).

You should, therefore, use RETURN-CODE and not a RETURNING clause. If
RETURN-CODE is non-zero after calling one of these routines, you must proces
s it
as a file status, for example:
01 file-status      pic xx comp-x.
01 redefines file-status.
03 fs-byte-1  pic x.
03 fs-byte-2  cblt-x1-compx
. . .
call "CBL_xxx_xxx" using parameters
if return-code not = 0
move return-code to file-status
. . .
At this point fs-byte-1 contains "9" and fs-byte-2 contains the run-time sys
tem
error number."



--
Bill Klein
wmklein <at> ix.netcom.com
"Jason_Thomas" <jthomas@medata.com> wrote in message
 news:97891f2a1e9389cd8d597da17e7eba49@lo
calhost.talkaboutprogramming.com...
>I have run into the same problem.  I will post what I find.  Does anyone
> have the definition for the 14605 return code?
>
> Jason
>