|
Hi there, I'm trying to remember how the BIR key used to work - but I think it just used the same key as BPCS. However, did the library names change? You could try this: (The BIR libs are normally called BPCSRW, BPCSDD, and BPCSGPL) Add the BIR libs to your library list, CALL RW9012 This brings up a screen, where you enter the new library names. Then change the job description 'RW' to have these libraries in its inllibl. Hope this helps, cheers, Clare Clare Holtham Director, Small Blue Ltd - Archiving for BPCS web: www.smallblue.co.uk IBM Certified AS/400 Systems Professional E-Mail: Clare.Holtham@btinternet.com Mobile: +44 (0)7960 665958 ----- Original Message ----- From: <WASHBURNCCINC@aol.com> To: <bpcs-l@midrange.com> Sent: Wednesday, November 13, 2002 3:57 PM Subject: OLD System-36 version of BPCS question on BIR product. > I ran into a company the other day that has a very old version of BPCS running in Sys-36 Environment on the AS/400. > > They have long since dropped maintenance with SSA and they had a company come in and move their BPCS software from the System-36 to the AS/400 running in Sys-36 environment. > > The only problem they are having is with the old BIR product. > > They get the following error message when try to create a new report. " Software Licence violation check.Call supplier for assistance." > > Does anyone know a solution to this? Thanks in advance for any help giving. > _______________________________________________ > This is the SSA's BPCS ERP System (BPCS-L) mailing list > To post a message email: BPCS-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/bpcs-l > or email: BPCS-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/bpcs-l. > >
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.