ISFCALLS failing to populate token. stem! Suddenly!

[Steve Coalbran]

I was using ISFCALLS within a batch ISPF/REXX procedure.
It was working quite happily until recently when it started to not populate the token. stem!
Despite giving a return code of 0.
I would have expected this to be caused only by:

Code: Select all

RC Description
01 Host command environment query failed, environment not added
02 Host command environment add failed

TRACE output...

Code: Select all

  199 *-*    token. = 0                                  
       >>>      "0"                                      
   200 *-*    RC = ISFCALLS("ON")                        
       >>>      "0"                                      
   201 *-*    SAY "RC="RC                                
       >>>      "RC=0"                                    
RC=0                                                      
   202 *-*    DO t = 0 TO token.0                        
       >>>      "0"                                      
       >>>      "0"                                      
   203 *-*     SAY token.t                                
       >>>       "0"                                      
0                                                        
   204 *-*    END                                        
   202 *-*    DO t = 0 TO token.0                        
   205 *-*    IF( token.0>0 )                            
       >>>      "0"                                      
   294 *-*    ELSE                                        
   295 *-*     CALL ABEXIT 8,"NO TOKENS SET BY ISFCALLS."
       >>>       "8"                                      
       >>>       "NO TOKENS SET BY ISFCALLS."            
   484 *-*      ABEXIT:                                  
       *-*      PROCEDURE                                
       *-*      TRACE "O"                                
NO TOKENS SET BY ISFCALLS.                                
ISPD117                                                  
The initially invoked CLIST ended with a return code = 8                        
******************************** BOTTOM OF DATA ********************************

All suggestions why this should suddenly happen would be welcome!

[enrico-sorichetti]

nowhere in the docs is told that ISFCALLS should populate something

quoting the manual

Using SDSF with REXX requires that you add a host command environment prior to any other SDSF host environment commands. The host command environment is what allows you to use Address SDSF on the ISFEXEC and ISFACT commands. You add the host command environment with the ISFCALLS() function.

nothing will passed back apart the return code

[Steve Coalbran]

Yes. But ISFCALLS() should create the token. stem.
It certainly used to. I listed it in previous executions, it produced 2060 separate tokens.
The token.1 is used toass to an ISFACT...

Code: Select all

ADDRESS SDSF "ISFACT ST TOKEN('"token.1"') PARM(NP XDC) "

I realize I had the statement in the wrong order!
The ISFCALLS should be followed by a ISFEXEC! It is this that sets the token. stem.
However now when I issue the ISFACT...

Code: Select all

SDSF OUTPUT DISPLAY PFTPJOBF JOB09992  DSID   103 LINE 209     COLUMNS 02- 81  
 COMMAND INPUT ===>                                            SCROLL ===> CSR  
   218 *-*      CALL ISF 00,"ISFACT ST TOKEN('"token.1"') PARM(NP XDC) "        
       >>>        "00"                                                          
       >>>        "ISFACT ST TOKEN('3T0VNDMqE5KVd/f3c/PxQO1z9+PP89xA3M1qA7omBLcn
CJgQABAU3GZE3NxURNivOJYk=') PARM(NP XDC) "                                      
   373 *-*       ISF:                                                          
   374 *-*       /*-------------------------------------------------------------
   375 *-*       /* initialize and accept arguments                            
   376 *-*       /*-------------------------------------------------------------
   377 *-*       __tv = TRACE("C")                                              
   446 *-*        ADDRESS SDSF __cmd                                            
       >>>          "ISFACT ST TOKEN('3T0VNDMqE5KVd/f3c/PxQO1z9+PP89xA3M1qA7omBL
iaCJgQABAU3GZE3NxURNivOJYk=') PARM(NP XDC) "                                    
       +++ RC(8) +++                                                            
                                                                               
COMMAND: ISFACT ST TOKEN('3T0VNDMqE5KVd/f3c/PxQO1z9+PP89xA3M1qA7omBLcnAwQCt2PwTh
ZE3NxURNivOJYk=') PARM(NP XDC)                                                  
ENDED RC=8                                                                      
ISPD117                                                                        
The initially invoked CLIST ended with a return code = 8                        
******************************** BOTTOM OF DATA ********************************

[enrico-sorichetti]

lets close the topic the IBM way ... USER ERROR

[Steve Coalbran]

lets close the topic the IBM way ... USER ERROR

The first certainly was.
However I still don't understand the RC(8) on the ISFACT call.
The exact same logic has worked before.

[enrico-sorichetti]

nope ... the whole topic should be closed for that reason ...

the manual is clear

After the ISFACT host environment command completes, a return code is set in the REXX variable RC. The values are:

00
The request completed successfully.
04
The request completed successfully but not all functions were performed.
08
An incorrect or invalid parameter was specified for an option or command.
12
A syntax error occurred in parsing a host environment command.
16
The user is not authorized to invoke SDSF.
20
A request failed due to an environmental error.
24
Insufficient storage was available to complete a request.
Note that a return code of 0 indicates that SDSF successfully processed the ISFACT command. It does not indicate that specific functions were authorized or that commands were executed.
Check the ISFMSG and ISFMSG2 variables to determine if a request completed. See Messages for more information.

[Steve Coalbran]

OK, just one parting shot.
I did study the manual closely several times.
In fact I generally, right from the '70s, read the whole manual before I start and refer to it frequently.
I also looked up the error messages received and the function ISF sets the default message for any return code and uses that if ISFMSG is blank (as it was).

I should get myself an RTFM T-shirt actually, not a bad idea?!

This is also exactly the same syntax I have used before which has worked.

But I will consider the topic...
Closed
(the forum should perhaps consider adding a button/function for the 'poster' to [Close] a post? )

[Terry Heinze]

(the forum should perhaps consider adding a button/function for the 'poster' to [Close] a post? )

Closing a post would deprive others who are looking for an answer similar to ones already posted.

[enrico-sorichetti]

Closing a post would deprive others who are looking for an answer similar to ones already posted.

NOPE ... the topic would still be visible,
the closest equivalent would be locking the topic, it would prevent further posts.