|
View previous topic :: View next topic
|
| Author |
Message |
John Poulakos
Active User
Joined: 13 Jun 2012
Posts: 178
Location: United States
|
|
|
|
I'm not a CLIST/REXX expert, by any stretch of the imagination, but my interpretation of this statement is it will attempt to open a REXX or CLIST found in the normal search order:
"ISPEXEC SELECT CMD(CALL *(CAZPMSEL)) ",
" NEWAPPL(CAZ3) PASSLIB MODE(FSCR) "
My problem is, CAZPMSEL is in a load library, not a REXX or CLIST library.
Am I interpreting this statement correctly? I'm getting this error: MEMBER CAZPMSEL NOT FOUND WITHIN THE STANDARD SEARCH ORDER |
|
| Back to top |
|
 |
John Poulakos
Active User
Joined: 13 Jun 2012
Posts: 178
Location: United States
|
|
|
|
| It was moved from Rexx/CLIST? I don't understand. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
It would help if you issued PROFILE MSGID before invoking the exec. It should provide a messages number that you can search for.
If you say: SELECT CMD(%myprog)
It searches rexx and clist only.
If you say: SELECT CMD(myprog)
It searches rexx and clist followed by load module search.
If you say: CALL *(myprog)
It searches load modules only. This is probably where you are failing. How are you adding your library to the standard search order. Perhaps you can get by by adding to the ISPLLIB concatenation before you start ISPF.
Consider using LIBDEF followed by: SELECT PGM(myprog)
You should read the discussion of 'User link libraries' in the ISPF Services manual, under LIBDEF. |
|
| Back to top |
|
|
John Poulakos
Active User
Joined: 13 Jun 2012
Posts: 178
Location: United States
|
|
|
|
| Thank you very much! That is just what I needed. I didn't know what it searched with this command. Now that I know, I found the problem. The library it needed to search should have been linklisted. It wasn't. |
|
| Back to top |
|
|
|
|
