× 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.



If you have access to HelpSystems ROBOT scheduler, it has a feature that
it captures ALL variables necessary to submit the batch.

Good luck!

Norman K. Boyd



From: Arnie Flangehead <arnie.flangehead@xxxxxxxxx>
To: bpcs-l <bpcs-l@xxxxxxxxxxxx>
Date: 06/09/2010 01:02 PM
Subject: [BPCS-L] Rebuilding V8.2 BPCS Literal (message) Database
Sent by: bpcs-l-bounces+norman.boyd=showaaluminum.com@xxxxxxxxxxxx



Hi All

In V8.2 BPCS there's a utility to maintain literals (e.g. the headings
on display screens), which underneath the covers is using *MSGF
SSAZ03, but it also has its own files built over the message file to
enable advanced features like search and replace, etc.

If you maintain a message using this utility your changes will be
immediately visible, but if you update SSAZ03 directly, the changes
will not appear in the utility till the database is rebuilt.

I want to update messages in a batch process using the CHGMSGD, but I
don't want to confuse other users/developers who might try to access
them via the BPCS utility. Therefore I want to also run the database
update in batch. The program appears to be SYS709[C], but I don't know
what the parameters are (I've tried with the obvious library, file and
vice versa). The programs are shipped without source and have no
observability data included so cannot be viewed or debugged.

Has anyone faced and solved this problem, or have a way to figure out
the parameters?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.