|
Hi, Wow - now we are an Omen movie ;-) Just a correction to all - it's known as a daemon, not damien! ;-) You do not need to create ports. The iSeries operating system maintains these as part of TCP/IP (assuming TCP/IP is started on your box). You just need to ensure with use of the NETSTAT command that a port number that you want to use with BPCS is not already being used for something else. Any number between 1 and 65535 is usually valid, though you will find that other software might be using other ports and in general ports over 5000 are safer, as many lower port numbers get reserved for system functions. When you use NETSTAT if a job is started to that port, there is an option to view the job - ensure it is really the ALAUNCH job and that there is no MSGW or other odd status (you can end and restart the job if there is some abnormal error). If it's not ALAUNCH but something else which is taking up that port, maybe you now have installed some new software which is already using that port? Write down the program name and figure out whose software it belongs to. If this is the case, you can either reconfigure that software to use another port and restart that software, or you can start the BPCS ALAUNCH daemon to a new port (but in this case all your users will need to update their workstation settings to point to the new port number). If things are really a mess, you can end and restart TCP/IP, though generally this should not be required. BMR 67665 is required for V5R3 and higher releases of OS/400 to run any Client/Server daemon (Newi or Alaunch). If you order and apply this BMR for Alaunch, your command to start ALAUNCH will change (STRALD) and you will get some better diagnostic messages (and will be able to configure your environment differently and more flexibly if you like) - but it's not a required upgrade at V5R2. Thanks, Genyphyr Novak Senior System Software Engineer SSA Global R&D ------------------------------ message: 4 date: Tue, 25 Jul 2006 22:21:31 +0200 from: "Davide Roveda" <Davide.Roveda@xxxxxxxxxxxxx> subject: Re: [BPCS-L] CEA Damien job start Hello Please, check if needed BMR 67665. I do not remember exactly if for V5R2 or V5R3. Regards Davide ------------------------------ message: 7 date: Wed, 26 Jul 2006 10:50:11 -0400 from: "Wes Reinhold" <WesR@xxxxxxxxxxx> subject: Re: [BPCS-L] CEA Damien job start You can allocate a port to the job using WORK WITH PORT RESTRICTIONS in CFGTCP so nothing else grabs that port. That's what we had to do. After that it worked fine. (V5R3) -----Original Message----- From: bpcs-l-bounces+wesr=scc-inc.com@xxxxxxxxxxxx [mailto:bpcs-l-bounces+wesr=scc-inc.com@xxxxxxxxxxxx] On Behalf Of Steve Segerstrom Sent: Wednesday, July 26, 2006 10:14 AM To: SSA's BPCS ERP System Subject: Re: [BPCS-L] CEA Damien job start The last time I spent 3 days solving a problem like this:1 1. Moved to a new port - using netstat as a tool to make sure had a good port. I used both 5000 and 5001 successfully. 2. There was a job that hung up 5000; ended and started 5000. 5000 worked after we switched back from 5001. 3. We ran fine on version v5r2 (and beyond) good luck. looks like you have -----Original Message----- From: bpcs-l-bounces+ssegerstrom=intermatic.com@xxxxxxxxxxxx [mailto:bpcs-l-bounces+ssegerstrom=intermatic.com@xxxxxxxxxxxx]On Behalf Of Moy, Bill Sent: Tuesday, July 25, 2006 2:24 PM To: SSA's BPCS ERP System Subject: Re: [BPCS-L] CEA Damien job start IF using TCP/IP You should be able to use the NETSTAT command prompt use otion *CNN this will show the ports. Look for your port 5000 in the local col. It should be in the listen state. If working correctly. Bill -----Original Message----- From: rfolsom@xxxxxxxx [mailto:rfolsom@xxxxxxxx] Sent: Tuesday, July 25, 2006 1:23 PM To: SSA's BPCS ERP System Cc: bpcs-l-bounces+rfolsom=yupo.com@xxxxxxxxxxxx; bpcs-l@xxxxxxxxxxxx Subject: Re: [BPCS-L] CEA Damien job start I'm sure someone will correct me if I'm wrong, but I don't believe you can "create" the port. The installation instructions say that you can use any unused port (they suggest 5000, but I guess 5100 is just as good). Have you reconfigured the session manager settings since going to V5R2? That may be all you need to do. Rick Folsom, IT Administrator Yupo Corporation America 757-819-9230 fwsoftware@xxxxxx m Sent by: To bpcs-l-bounces+rf bpcs-l@xxxxxxxxxxxx olsom=yupo.com@mi cc drange.com Subject [BPCS-L] CEA Damien job start 07/25/2006 02:03 PM Please respond to SSA's BPCS ERP System <bpcs-l@midrange. com> Hello, I'm trying to get BPCS CEA going and keep getting the same error, Physical server not started. I believe it has something to do with the Daemon job on the server. Question, how do we create a port on the AS/400 that will service the Daemon job and incoming CEA jobs? Here is the command I'm running and it's worked before on v5r1 OS/400 I'm running this on a v5r2 box, again I believe the problem is that port 5100 does not exist now on the new box how the heck do I create this port. I have not heard of any problems of running CEA on v5r2. Thanks in advance Dave SBMJOB CMD(CALL PGM(MMTCP/ALAUNCH) PARM('5100')) + JOB(XX_IPJOB) JOBD(MMTCP/TCPIPJOBD) + JOBQ(QGPL/BPCSTCPIP) INLLIBL(MMTCP + BPCSTCPUSR QGPL) ________________________________________________________________________
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.