Conference iosg::all-in-1_v30

2548.0. "FILECAB functions not working from script symbiont" by OASS::VALDEZ_C (A smile is the same in any language) Thu Apr 08 1993 19:36

Hi,

I am having trouble with FILECAB functions when calling them from a script 
which is submitted via the script symbiont.  (I've cut it down to this test 
piece of code.)  

! FCTEST.SCP
GET #OLDF="DOCS-TEST1"
GET #F="TEST1"
GET #D="MYDRAWER"
FILECAB REFILE_FOLDER (DRAWER="MAIN",FOLDER=#OLDF,TO_DRAWER=#D,TO_FOLDER=#F)
.EXIT

Drawer, MYDRAWER, already exists.  When I run this bit interactively 

Enter Command> DO FCTEST

it works fine.  When I submit it with

Enter Command> SUBMIT_SCRIPT
(SCRIPT="USERDISK2:[VALDEZ_C.A1]FCTEST.SCP",ACCOUNT="VALDEZ_C",NOTIFY)

it is retained on error in the queue,

%NONAME-E-NOMSG, Message number 00000002

and the FILECAB REFILE_FOLDER does not work.  I enabled tracing for the server 
and for myself as a client and saw that when I invoke the script 
interactively, the server trace log has

FILE CABINET NAME: AMERIG.VALDEZ_C

When I submit the script the server trace log has

FILE CABINET NAME: AMERIG.

(AMERIG is the node I am working on.)  The TRACE EVENT in this log shows 
"CONNECTION RECEIVED" and then "CONNECTION REJECTED".

I've tried variations of the above with no luck.  I tried on another node and 
got the same results.  I tried using another FILECAB function and still had 
the same problem.  What should I do to get the server to recognize the file 
cabinet for the account I've submitted the script for?

Thanks in advance.

Cindy

Hi Cindy,

I've looked at the code, and the news is bad. The FILECAB function uses
a piece of data which ought to be set up by the script symbiont prior to
script execution, but isn't.

The file cabinet name which FILECAB constructs is wrong due to this piece of
data not being set up. The file cab server correctly rejects the connection
when it is given a bad file cabinet name. 

I'm afraid the only solution to this problem is a code fix to OAINI.BLI.

Sorry,
Derek

Hi Derek,

Thank you very much for taking the time to look at the code and clear this up 
for me.  I'll submit this through the proper channels.

Thanks again.

Cindy