new non-db file with the same name higher in the libl?

Jim Horn

------------------------------

message: 7
date: Wed, 7 Apr 2010 08:03:57 -0500
from: "Don Cavaiani" <dcavaiani@xxxxxxxxxxxxx>
subject: Something got whacked ??

Here is an age old, unchanged procedure which failed today (first time I
can remember this happening). Any clue on what might be happening?

-----------------------------------------------------------------------------------


CALL SFC520C
Open of member FSOAM was changed to SEQONLY(*NO).
Open of member FSO was changed to SEQONLY(*NO).
Open of member FOD was changed to SEQONLY(*NO).
Open of member FMA was changed to SEQONLY(*NO).
Open of member FMAL02 was changed to SEQONLY(*NO).
Open of member FODL02 was changed to SEQONLY(*NO).
Open of member FSOL01 was changed to SEQONLY(*NO).
Member (MBR) parameter allowed only with data base file.
<-------------------------------------------
Error occurred during processing of command.
Function check. CPF9899 unmonitored by SFC000 at statement 1900,
instruction X'0012'.
CPF9899 received by SFC000 at 1900. (C D I R)


Don F. Cavaiani
IT Manager
Amerequip Corp.
920-894-7063
This email is intended only for the person or entity
to which it is addressed and may contain information
that is privileged, confidential or otherwise protected
from disclosure. If you are not the named addressee
or an employee or agent responsible for delivering
this message to the named addressee, you are not
authorized to read, print, retain copy, and disseminate
this message or any part of it. If you have received this
message in error please notify us immediately by email,
discard any paper copies and delete all electronic files
of this message.


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.