How to Pass the Security Check in a Scheduled Job

I have hit a wall.  I am trying to run the CST900C batch jobstream from a 
scheduled
job entry in V4.0.5.  We have a CL load the LDA with the required information 
(outq,
copies, etc) and am even calling SYS008C.

SFC900 runs fine, but I believe at CST900 there is a call to SYS650C, SYS656 
and the
security validation blows up.  I notice that a user space named BKFLUSH20 is 
created
during the run since this is the job name, not the workstation ID it is 
expecting.
So this brings a possible solution to mind; what if I make a copy of the current
workstation LDA and name it BKFLUSH20?  I believe the security information is
imbedded in the LDA and certain processes probe it.  So, in theory this should 
work.

Any thoughts, or much better suggestions?

Bill

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---