|
I can't locate the exact command,
But here is another log message - yet it looks like all the file types
are OK.SFC000
30 04/07/10 06:57:13.121952 QLICKOBJ QSYS 0195
base
Message . . . . : Member (MBR) parameter allowed only with data
filehappening?
Cause . . . . . : Only a data base file can contain members.
Recovery .
: Either change the object value to a data base file and the
object typ
value to *FILE, or omit the member (MBR) parameter. Then try the
request
again.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: Wednesday, April 07, 2010 8:17 AM
To: Midrange Systems Technical Discussion
Subject: Re: Something got whacked ??
What command caused that message?
On Wed, Apr 7, 2010 at 9:03 AM, Don Cavaiani
<dcavaiani@xxxxxxxxxxxxx>wrote:
Here is an age old, unchanged procedure which failed today (first
time
I can remember this happening). Any clue on what might be
--------------------------------------------------------------------
--
-------------
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
"It's amazing what you can accomplish if you don't care who gets the
credit." Harry S. Truman
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,--
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,http://archive.midrange.com/midrange-l.
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,--
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-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.