JCL calling REXX - getting IKJ56246I and ISPF RC27 warning

jzhardy · Posted: Thu Jul 17, 2014 1:17 pm

hi,

I'm running a set of REXX scripts within JCL. They run successfully, but getting an RC27 and IKJ56246I warning. Any ideas where they are coming from or how to suppress them?

ISPSTART CMD(%NEWC VACZCLHB NC)
IKJ56246I TERMINAL NOT ALLOCATED, FILE IN USE
NEWC successful for VACZCLHB in region NC (autoinstall)
ISPD117
The initially invoked CLIST ended with a return code = 27

here's the cut from my JCL:

//VACZCLHB EXEC PGM=IKJEFT01,DYNAMNBR=250
//SYSUDUMP DD SYSOUT=*

.... (not showing all the lib allocations)

//SYSTSIN DD *
PROFILE PREFIX(UCOY2) WTPMSG
ISPSTART CMD(%TIXBKGN3 PROGRAM(IEFBP1) TRACE(OFF) +
TIUDEBUG(X))
%TICGRETC TIUDEBUG(X)
ISPSTART CMD(%$BATCOPY)
ISPSTART CMD(%NEWC VACZCLHB NC)
ISPSTART CMD(%NEWC OJAAWAE1 NC)
ISPSTART CMD(%NEWC IJAA0511 NC)
/*

Paul Voyner · New User Joined: 26 Nov 2012 Posts: 52 Location: UK

It's not possible to say why rc=27 or even which of the 6 REXXs is giving the problem, based on the information you supplied.
But the ISPD117 message simply means that one of the REXXs ended with a RETURN 27 or EXIT 27. That's not a standard return code, so look at the code of the failing REXX and see if 27 is a coded value anywhere. You may have to do some debugging e.g. setting TRACE R.

Paul Voyner · New User Joined: 26 Nov 2012 Posts: 52 Location: UK

Oops - the messages do make it clear that the rexx ISPSTART CMD(%NEWC VACZCLHB NC) is the one causing the problem.
But the rest of my comment still applies: you'll have to look inside the NEWC rexx and maybe trace it.