I had this same issue last week when scheduling a BPCS job, CIM600. So
what we did was to wrap the job in a CL and in the CL did a call to SYS656
with the parameter as SYS656. It worked like a charm. The job didn't blow
up. This happens when BPCS tries to validate the security settings in the
environment you are calling the job from.
Hope this helps.
From: rob@xxxxxxxxx
To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Date: 08/30/2012 08:08 AM
Subject: Re: [BPCS-L] Billing re-print automation
Sent by: bpcs-l-bounces@xxxxxxxxxxxx
It's not the product you use for job scheduling that's the cure. Whether
it's the standard WRKJOBSCDE, some Robot product, or whatever. It's
whether or not you use some standard calls to get started.
I can't find the link right now but there's a standard doc on how to
submit a bpcs job to batch from a job scheduler. We've also had to use
this technique when calling bpcs programs from Lotus Notes.
Some is dependent on whether or not you are using LX or an earlier
version.
Search these archives for SYS664 for earlier versions. Like this:
http://archive.midrange.com/bpcs-l/200902/msg00042.html
For an LX version a coworker has this document:
LX Scheduled job setup
Call to SYS550W sets up environment and *LDA
Call to SYS610C or SYS664 sets up security. SYS610C is to verify
security, and SYS664 is to ram it through.
Example from CSTROLL:
callp SYS550W('ERPLXEC':RTPARM)
callp SYS610C(User:'CST600B':Err)
Rob Berendt
midrange.com
