On 12/23/2005 7:04 AM, Seremis wrote:
Thanks, Willy, for the answer! But I am sorry to say that until now
it's not the solution to my problem. Maybe I didn't describe clear
enough that the LISTCAT-commands are issued from user program level.
For some reasons we must check file existences on program level and
cannot do it in a REXX exec (where SYSDSN could be used easily).
Please let me show the sequence:
At the beginning there's a REXX exec:
x = msg("OFF")
t = outtrap("DUMMY.")
address tso "ALLOC DD(PEPEXEC) DSN('"my.exec"') SHR REUSE"
address tso "ALTLIB ACT APPL(EXEC) LIBRARY(PEPEXEC)"
address tso "ALLOC DD(PEPPUSR) DSN('"my.panel"') SHR REUSE"
address ispexec "LIBDEF ISPPLIB LIBRARY ID(PEPPUSR) STACK"
address tso "ALLOC DD(PEPLUSR) DSN('"my.load"') SHR REUSE"
address ispexec "LIBDEF ISPLLIB LIBRARY ID(PEPLUSR) STACK"
address ispexec "SELECT CMD(OP70) NEWAPPL(PEP) PASSLIB"
From here on the user program OP70 is active which ist written in
COBOL. It
contains:
CALL 'ISPEXEC' USING V-TSO-CMD-LENGTH V-TSO-CMD.
where V-TSO-CMD is for example:
SELECT CMD(LISTCAT ENTRIES(PEPE99P.A2345678.LOCK) OUTFILE(OUTLST))
These commands produce the rubbish screen output I want to get rid off.
I think you will need to change that user program so it invokes a REXX
exec rather than invoking LISTCAT directly, and have that REXX exec
enable output trapping. In fact, the REXX exec could probably invoke
SYSDSN and just give a return code to the COBOl program telling it
whether the data set existed or not, rather than the program having to
read LISTCAT output.
Or, you could have the COBOL program use the catalog search interface to
query the catalog directly, rather than using LISTCAT.
Walt
----------------------------------------------------------------------
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
