|
Request FAILED : Messages containing FW: or RE: or UNDELIVERABLE: in the subject line are not processed by HELPSTAR mail sentry. Your request is not logged , please try again without RE: or FW: or UNDELIVERABLE in the subject line. ++++++++++++++ ORIGINAL REQUEST ++++++++++++++ One thing to be careful of (apologies if it is mentioned elsewhere):- The various System 21 background jobs also use some of the 99 files. We clear the 99 files each night, but only when the background jobs have all been ended pre-backup. Regards, Neil. -----Original Message----- From: owner-jbausers-l@midrange.com [mailto:owner-jbausers-l@midrange.com]On Behalf Of Jeff_Klipa/Harvard@harvardind.com Sent: Friday, December, 01 2000 15:00 To: JBAUSERS-L@midrange.com Subject: Re: MSP99 MSP99 is a record locking file (this is old logic that was developed prior to the advent of modern operating systems that control record locking for you... Be that as it may, we're stuck with record locks...) that was designed to prevent two users trying to update the same record at the same time and perhaps having one set of changes step on another users changes... If a users job fails while maintaining a route for instance, then that MSP99 lock record will remain and no-one will be allowed to maintain that route until the record is cleared from MSP99... There is a conspicuous lack of consistency between the different '99' files in terms of date and time stamping... It would have been nice if they had given us both date and time in all of the records, but alas, they did not... This makes it difficult sometimes to know when you are clearing a valid lock as opposed to a bogus lock... It is not uncommon for users terminal sessions to end abnormally for a variety of reasons... The net result is you are going to get locks in the '99' files in many applications... We have written a rather handy set of programs to allow for maintenance of the '99' files and even to clear them automatically every night... You might want to tackle this yourself... Here is a list of the files... Note SAP93 - do not clear SAP99...!!! File Name Applications that use it The Standard library you will find it in... AIP99 EDI D1 CHP99 Product Data Management PD CNP99 AOE, Configurator D1 CRP99 Customer Returns D1 CSP99 Cash Manager, A/R CS DRP99 DRP D1 DYP99 Document Processing D1 FCP99 Forecasting D1 FIP99 AFI FI FLP099 G/L GL INP99 Customer Service and Logistics, EDI, Warehousing D1 MSP99 Capacity Planning, MPS, MRP, PC, PDM, Warehousing PD PLP99 Cash Management, A/P, A/R PL PMP99 Adv. Ship, Adv. OE, Purc, Requis, Vendor Sched D1 RWP99 Financial Manager RW SAP93 Forecasting, Sales Analysis D1 SLP99 Cash Management, A/P, A/R GL WHP99 Warehousing D1 WTP99 World Trade D1 There are basically 3 forms of record locking that you are faced with in JBA - the '99' files we mentioned above where a key to the record is stored in the '99' file. The next is an ACTIVE FLAG stored in the master record itself... And the next is EXCLUSIVITY which is controlled by the Application Manager itself... We automatically clear all 3 types of locks in our night job. To clear the Active Flags you need to edit the file with DFU, DBU or WRKDBF (WRKDBF is Freeware you can get from the internet)... Here is a list of the files we have identified that have Active Flags...: There may be more... 1. Purchase Order Header PMP02 2. Inventory Item Master INP35 3. Stockroom Details INP60 4. Job Management Header JM23 5. Customer Returns Header CRP02 Each file has a different field and scheme for the active flag so you'll have to figure that out... Again no consistency... To clear any and all bogus Exclusivity locks you can issue a CALL to XA705CLP from any JBA command line and it will clear the bogus Exclusivity locks which are stored in APG02PHY... You can also add the command CLNUSRALC to your night job... Check out the GEAC - System 21 Redbook for more on Record Locking... http://www.redbooks.ibm.com/abstracts/sg245967.html Good Luck... +--- | This is the JBA Software Users Mailing List! | To submit a new message send your mail to JBAUSERS-L@midrange.com. | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com. | To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: doug333@aol.com. +--- +--- | This is the JBA Software Users Mailing List! | To submit a new message send your mail to JBAUSERS-L@midrange.com. | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com. | To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: doug333@aol.com. +--- _________________________________________________________________________ Help Desk software by HelpSTAR.com, Inc., http://www.helpstar.com +--- | This is the JBA Software Users Mailing List! | To submit a new message send your mail to JBAUSERS-L@midrange.com. | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com. | To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: doug333@aol.com. +---
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
