× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Many thanks all,

problem is solved by UK HelpLine.
It was the first time we set up an environment from an empty database, and some
files weren't re-populate as described in member SSALOG00 in BPCSO/BPCSDOC
source file.

Regards


-----Original Message-----
From:   novakg@ssax.com 
Sent:   Wednesday, February 23, 2000 8:13 PM
To:     BPCS-L@midrange.com
Subject:        Re: Client problem

Hello,

You should search for an/or check the job log  on the AS/400. You don't say
what BPCS program(s) you are trying to sign into, but your job log will
either be under the name of the user who started the daemon (1st generation)
or under your name (2nd generation Full C/S only). This message means that
required programs on the server could not be started - the daemon does not
know why, but only knows required programs failed to start. Either a library
list is wrong, authorities to some objects are absent or a host of other
problems could be the cause (configuration is the problem in any case, but
there are many flavors of configuration problems). I suggest you phone the
AS/400 HelpLine to get this resolved most quickly.

Thanks

Genyphyr Novak
SSA
-----Original Message-----
From: FRANCISCO.ZABALETA@roche.com <FRANCISCO.ZABALETA@roche.com>
To: BPCS-L@midrange.com <BPCS-L@midrange.com>
Date: Wednesday, February 23, 2000 9:40 AM
Subject: RE: Client problem



Thank you Marc for your advises but problem still remain:

- User password OK (8 & 5 chars)
- User valid (Prod All 1)
- Daemon is up and running. I can see my job (in WRKACTJOB) arriving and
leaving
immediately. What do you mean by 'well configured'?
- 'Q' and 'X' *DTAARA deleted
- SSASYS *DTAARA reviewed and OK (as other environments)

I'm wondering why the error message states: Could not start Server Program.
(Check INI file)?
When daemon isn't running it states: Connection refused.

Thanks,
Francisco


-----Original Message-----
From:   LACELLE@rcmint.ca
Sent:   Tuesday, February 22, 2000 7:11 PM
To:     BPCS-L@midrange.com
Subject:        RE: Client problem

Hi Ho.

        I'm about to change my Hi Ho to Ho Ho Ho. Where is that snow coming
from. Just kidding it's been rather nice for the past few hours.

        That is not a MM problem that is a Client Server Problem.

How to solve the problem

1. User password may be to long
2. Make sure user is a valid user in that Environment
3. Make sure Job Daemon is up and running (and well configured)
4. Delete all DTAARA that starts with a "Q" or "X" in data file library of
that environment
5. Make sure that in data file SSASYS(dtaara) found in Data file library:
                position 59 - 10 characters long is the library were your
BPCSOUTQ object lives
                position 140 - 10 characters long is the library were your
JOBD lives
        Please note: You may have changed the layout of this DTAARA
(SSASYS). Position 59 and 140 are based on original settings of this file.

        Give it a whirl

        Marc Lacelle
        Royal Canadian Mint

> ----------
> From:
> FRANCISCO.ZABALETA@roche.com[SMTP:FRANCISCO.ZABALETA@roche.com]
> Reply To:     BPCS-L@midrange.com
> Sent:         Tuesday, February 22, 2000 9:58 AM
> To:   BPCS-L@midrange.com
> Subject:      Client problem
>
>
> Hello,
>
> we are on AS/400 6.0.04 MM April Cumulative.
> For just one environment, when we sign in (userid & password) we got:
>
> - Fatal Error: Cannot Start Physical Server. Error is: Could not start
> Server
> Program. (Check INI file)
>
> we have dozens of environments and it is the first time we got this. Even
> if we
> take another environment that works fine and we go to the 'Workstation
> Settings'
> to change the library names, we still have the same problem.
>
> Has somebody experienced already the same?
> Thanks,
>
> Francisco
>
> +---
> | This is the BPCS Users Mailing List!
> | To submit a new message, send your mail to BPCS-L@midrange.com.
> | To subscribe to this list send email to BPCS-L-SUB@midrange.com.
> | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner: dasmussen@aol.com
> +---
>
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---


+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---

+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---

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.