× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Passing Parms to BPCS Programs
  • From: Mark Ramsden <markeramsden@xxxxxxxxx>
  • Date: Fri, 9 Apr 1999 02:45:11 -0700 (PDT)

Robert,

I had the self same problem at my current site.
We are running v.6.0.04 full C/S. RPG source code is not shipped with
the product so trying to determine the exact parameters is a tad
tricky. You mentioned MRP500 as an example. My first scheduling issue
was with MRP500. I contacted the SSA helpdesk and their solution was to
issue a software request for a BMR associated with MRP500 and on the
request specify that you require the program source code for the given
object. I was surprised to hear that I could have access to source code
and tried chancing my arm and requesting the code for the 'whole'
system. The response was that I would need to issue several thousand
software requests in order to recieve each source member. This is my
solution to job scheduling and parameters, any others would be
appreciated.  Mark.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.