Suggested Help approaches:

BBLL99 is not a logical which comes with BPCS. It is a name typically used
in modifications. You should ask the contractor what library/file the
source code for that logical resides in.
Many contractors create libraries, outside of BPCS *LIBL to hold their
additions, until testing completed.
It needs to be compiled into a library normally in the BPCS *LIBL.
Source code is often not in *LIBL, does not need to be during execution.
It is easy for a BPCS novice to screw that up.

BPCS naming conventions and concepts explained in SSALOG00 member of
BPCSDOC file (the BPCS logic manual).
BPCS comes with logicals named file-L- 01 and up, while modifications
typically 99 and down.
Different logicals are needed for different sequences and selections of the
records.
While you can get something to compile, doing an over-ride for a standard
logical, L99 is in the code for a reason, which you need to figure out and
fix, before the new code will work properly.
You may find an occasional logical with J instead of L, for those where 2 or
more physical files are joined by a logical. Beware of modifications whose
naming is inconsistent with SSALOG00 rules.

SSALOG00 also lists the correct compile commands for BPCS.
Depending on the libraries of your modifications, those commands may need
modification.

There's an OS400 command to view a file to see programs & work stations
currently using them for update lock . I have been off for a couple years,
not remember its name.

BBL and its logicals are generally not available because they are in use,
when anyone is working in shipping, since the shipping process (ORD590
series) populates BBL with details of shipments in need of billing.

Do a DSPDBF on BBL to locate all BBL logicals in the library list. Do a
display BBL* in *ALL libraries to find any BBL logical which have been
established in any wrong libraries.

XRF is broken in V405 CD but you can get most of it via
1. Locate the OS400 command to Display Program References.
2. Run that for BIL5* (and maybe also BIL6* which may need
modifications similar to what were done in BIL5*) in relevant *LIBL output
to *OUTFILE.
3. You then can do bottom up where used to locate everything which
calls or uses the program, or file, of interest, in BIL5* collection.
4. You may also need to do step 2 for *ALL BPCS software into an
*OUTFILE for reference between modifications, since some work files are used
across BPCS modules. We set it up to refresh weekly, because we had so many
ad hoc queries.

Alister Wm Macintyre (Al Mac).
Panama Papers group: https://www.linkedin.com/groups/8508998


-----Original Message-----
From: BPCS-L [mailto:bpcs-l-bounces@xxxxxxxxxxxx] On Behalf Of
Bacon_Arlete_M
Sent: Sunday, January 01, 2017 5:52 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: [BPCS-L] Trying to compil V4.0.05 BIL501

I am getting an error trying to compile V4.0.05 BPCS BIL501. It is saying
that BBLL99 is not available.
I have had a contractor change and compile. But I don't know the trick.
There is no BBLL99 on my production as400 or my development AS400. Someone
mentioned that maybe the trick is to do an ovrdbf with an existing file for
BBLL99.

Can anyone help??

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2021 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.