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



I worked in the past with the Product Structure Offline Maintenance 
process.  In the offline file it, there is a "Transaction Code"  (TRID) (8 
char) and it indicates what type of offline maintenance is being performed 
on this record:

E0PS0400 - Total structure delete
E0PS0500 - Delete record
E0PS0600 - Add record
E0PS0700 - Change record

The Offline Product Structure Maintenance (OLMPST) command is used to 
process a file containing offline product structure maintenance 
transactions. Information regarding the layout of the transactions can be 
found in an appendix of the application user's guide:

PROMPT Specifies whether the function should prompt for the application 
values at run-time.
1) *YES Application should prompt user for run-time values.
2) *NO Application should use run-time values supplied by command.

ENDS Specify the MAPICS environment designators to be validated when 
executing the command. If the environment designator specified here
does not match the environment designator associated with the current 
AS/400 job, this function will not execute. This will stop functions from 
inadvertently being executed against the wrong MAPICS environment.

OPTION Specifies how the application should process the offline 
transactions.
1) *EDIT Transactions are only edited.
2) *UPDATE Transactions are edited and the database is updated.

FILE Specifies the name of the file containing the offline transactions. 
The possible library values are:
1) *LIBL The library list is used to locate the file name. 
2) library-name Specify the name of the library where the file is located.
3) file-name Specify the name of the file to be processed.

DELREC Specifies what offline transactions should be retained after the 
file has
been processed.
1) *ALL All transactions should be retained.
2) *ERRORS Only error transactions should be retained.
3) *NONE No transactions should be retained.

All this is in the manual.  You can get more details there.

Hope this helps somehow...

Peter Vidal 
PALL Corporation / SR Programmer Analyst, IT Development Group
10540 Ridge Rd., Ste 203, New Port Richey, FL 34654-5111
http://www.pall.com

"I not only use all the brains that I have, but all that I can borrow."
Woodrow Wilson (1856-1924)

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.