Run oninit with verbose (-v) to see if will point you to what is missing. I
see it in the past and I believe it was to due to missing message file or
error file. The file exists but the file extension name was different and I
had to make/create a copy of that file with the extension name that
informix was looking for. Do not recall exactly the filename but it was not
a big issue?
Check your INFORMIXDIR/msg directory to verify the extension of your msg
file. (.pam)

Is this a re-install?
Else check with tech support.

jp

                                                                         
            Jonathan Leffler                                              
            <jleffler@earthli                                            
            nk.net>                                                    To
            Sent by:                  informix-list@iiug.org              
            informix-list-bou                                          cc
            nces@iiug.org                                                
                                                                  Subject
                                      Re: Unable to open input file 'c'  
            10/24/2007 12:17                                              
            AM                                                            
                                                                         
                                                                         
                                                                         
                                                                         

David Reed wrote:

I assume there is some long term plan to upgrade to more recent hardware
and software, and there is an immediate crisis that must be resolved.

What is the x in 7.x?

What has changed in your configuration files recently?

What does the online log say?

Does 'oninit -v' give any help?

--
Jonathan Leffler                   #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2007.0914 -- http://dbi.perl.org/

publictimestamp.org/ptb/PTB-1613 whirlpool 2007-10-24 03:00:05
AAC9108F434B737C3716B27E18E8339D0AAAC353561F377574BF4B1E82FD48FD2BA17E
E66F6457ADB50079A30AF546A23E9AB38B48A8A33BFDAAB96D37753AB
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list

In the file evidence.sh there are two  lines :

       ev_pretty $ONSTAT -g smb s
       ev_pretty $ONSTAT -g smb c

These onstats are used to print out sbspace information.
They make sense in 9.x but not in 7.x IDS version . When you call

%onstat -g smb s
or
%onstat -g smb c

in a 7.x environment onstat will report these messages about input files
that can't be opened.

Unfortunately the updated version of evidence.sh (that one that included
these onstat commands) made it into all IDS build environments (not only

So what it means when you see these messages on the terminal after you
typed

%oninit

simply is that IDS crashed upon the attempt to start it.
You may ignore the message about not being able to open input fil 'c' or
's'
but you probably want to investigate the reason for the crash. (look
online.log, af.xxxxx file)

I think they fixed evidence.sh in saome later IDS 7.31.xD but not sure.

Rgds
Tilman