Joined: 30 Aug 2006 Posts: 14 Location: Tampa, Florida
On an FTOPEN in a REXX EXEC, I get the ISPG117 - abend code ISPFITLR.
I can't find this abend code; can anyone tell me what it is?
Immediately preceeding it, I got a RC=12 on an allocate statement. I was trying to allocate (ispfile) a JOB with an LRECL of 80 (recfm f b) and I suspect the generated lines went over 80 bytes but I can't tell.
Whatever the problem, it obviously caused the abend ISPFITLR but I can't find a description of that abend.
Also, when I get an RC=12 in REXX, is there a way to get a problem description? That is, I have no idea what caused the return code of 12- I'm just guessing it was the lrecl, after the symbolics in the lines were resolved.
An ISPFITLR seams to be an File-Tayloring-Service Error.
make shure that your Skeleton-lib is correctly allocatet to ISPSLIB.
If output from file tailoring is not to be placed in a temporary file, the
desired output file must be allocated to the ddname ISPFILE before
invoking this service. ISPFILE can designate either a library or a
sequential file. The skeleton files can contain variable-length records,
with a maximum record length of 255.
The simple way is, to write output to temporary file like ZTEMPF
or ZTEMPN.
Specifies that the output of the file tailoring process should
be placed in a temporary sequential file. Output is fixed-length
80-byte records. The file is automatically allocated by ISPF.
Its name is available in system variable ZTEMPF.
If this parameter is omitted, the output is placed in the
library or sequential file designated by ddname ISPFILE.
ZTEMPF contains a fully qualified data set name. ZTEMPN contains
the ddname. Generated JCL in this file can be substituted for
background execution by using the following TSO command: SUBMIT '&ZTEMPF'
Systemcode RC=12 using FTOPEN could be Output file in use; ENQ failed.
Here's a little FileTayloring example:
THEN DO
TEMPDSN = "IER1337.USER.JCL.S000"
TEMPJOB = "B92SPOOL"
Joined: 30 Aug 2006 Posts: 14 Location: Tampa, Florida
Thanx much! I found the problem on the prior "alloc" and it was in fact generating records greater than 80 bytes. Then the FTOPEN wouldn't work properly because the file was not allocated.
Part of the confusion was when I reran the REXX EXEC, I got a different error the next time, involving the FTOPEN. It turned out that logging out & back in again, made sure I only got the original error. Evidently after the failed allocation and FTOPEN, the file was left in some lurch and any attempts to run the EXEC again thus caused a different error and made things more confusing.
