Receive an error message indicating that Web Access for Information Management for z/OS (WAI) REXX exec cannot be found even though it is in the correct HFS directory
The bit mode setting must be 755 on the HFS file and path(s) leading to the file
Diagnosing the problem
Verify the mode bits are (755) on the REXX exec and ALL the directories traversed to reach the exec.
If one of the upper directories does not have the execute bit turned on then you can not execute in the lower directory.
Remember in Unix, execute means 'search a directory' when directories are transverses looking for a executable (aka rexx exec). So if the exec is not in a upper level directory the search stops at that level.
Read access really isn't needed, but we set it to 755 so that the ls command (and ishell) can list the files, technically 111 is all that is needed.
The solution is to go to BLQADMIN.html and click 'Test Web Server' (lower left). Near the top you will see:
Verify that the directory the modified code is in, is one of the directories listed. first one wins.
That should resolve the problem. If that doesn't resolve it then it's time for further debugging as follows.
Make sure the first line of the exec has /* REXX*/ (REXX inside of a comment - white space and extra *s don't matter ) - IF REXX is not on the first line, REXX just ignores the EXEC and keeps looking.
Open a browser and *LOGON* to get to a WAI home page. Then type:
REXX forms routine BUBBA was not found.
Please note the routine name and the following:(Use CTRL-P to Print, or cut & paste)
Rename the exec you *THINK* is run and call it BUBBA - or your pet name. Hit reload (HOLD the CTRL KEY and press F5): You should get:
Error routine in REXX routine BUBBA called.
(you get the 'Error routine' because calling the BL this way does not pass the right parms - but all you are after is the fact BUBBA was found.)
If you get NOT FOUND message instead of the 'Error routine' message then the path or mode bits, or REXX is not right. Review it all again carefully.
Assuming BUBBA gets the Error routine message verses NOT FOUND then find and RENAME ALL EXEC that have the RADxxxxx name they want to use, then using that RAD name in the address bar keep reloading until you get the 'NOT FOUND' message. Then rename BUBBA to RADxxxxx and it will be picked up and used.
Resolving the problem
This issue was resolved by setting the permission bits for the /rexx/ path to 755.