How to create a startup program for WAS61. The program to start the subsystem (QWAS6/QWAS6). 2 JOBS under qwas6 (wmp and wmpappsvr) after every IPL.

170 pts.
Tags:
AS/400
CL Program
IPL
I was assigned to create a CL program to call a startup program to start subsystem automatically after every IPL. the program WAS61 located here: /QIBM/ProdData/WebSphere/AppServer/V61/ND/bin. I do not know where to start and how. Please help anyone. I have tried the steps mentioned here http://www.itjungle.com/fhg/fhg062106-story02.html but I'm not sure does the command working or not. Please help.


Software/Hardware used:
as400
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 12  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Splat
    We use this: QSH CMD(/QIBM/ProdData/WebSphere/AppServer/V61/Express/bin/startServer [application server] -profileName [profile name])
    12,895 pointsBadges:
    report
  • ejaaje
    Thanks splat. I have the call program cmd :( CALL PGM(QWAS61A/QWASSTRSVR) PARM('-profilePath' '/QIBM/UserData/WebSphere/AppServer/V61/ND/profiles/Workplace' '-server' 'wsappsvr')                    

    i have created a job to run under qas61 subsystem. 
    Job            Job Description     Library   
    MWP              QWASJOBD          QWAS61    
    WSAPPSVR         WSAPPJOBD         QWAS61    

    it works fine for mwp(this was created few years ago by someone else) 
    however, i do not know how to start wsappsvr and how do i know this is actually working or not. thanks
    170 pointsBadges:
    report
  • Splat
    Is WSAPPSVR an application server?
    12,895 pointsBadges:
    report
  • ejaaje
    Hi all, please both jobs are not working now. I have created a schedule job, running under qbatch as a workaround. Please help me how to correct this. I have addje for both in autostartjob entries but when I restart the subsystem, both are not running. This is so serious.
    170 pointsBadges:
    report
  • ejaaje
    Splat,
    Yes, the WSAPPSVR is an appserver. It works the same lime mwp. but now, both are not working. :((
    170 pointsBadges:
    report
  • Splat
    Go to [your iSeries IP address]:2001/HTTPAdmin, click on the Manage tab, click on the Application Servers tab, select your application server, then select View Logs under Problem Determination.  The logs are a bit cryptic but may well tell you what the problem is.

    You can also use that interface to stop & start your application & HTTP servers.

    I'd also suggest you find the job logs for the jobs you ran.  There's going to be some information in there that may help.
    12,895 pointsBadges:
    report
  • ejaaje
    hi splat. thanks. i managed to see the httpAdmin. but the auto job that was previously running and the new one also not working now. the web service (schedule job is running to cover the failed job under qwas61). could you pls show me how to bring up the two jobs below. 

    Job            Job Description     Library   
    MWP              QWASJOBD          QWAS61    
    WSAPPSVR         WSAPPJOBD         QWAS61

    thanks
    170 pointsBadges:
    report
  • Splat
    ejaaje, Are the application servers running?  If so, why do you think the autostart jobs have failed?
    12,895 pointsBadges:
    report
  • ejaaje
    Hi Splat, i Check in [your iSeries IP address]:2001/HTTPAdmin it is running. But, how do i know that the auto job is running and not the schedule job.because i have created both as a backup. 
    170 pointsBadges:
    report
  • Splat
    The autostart job only needs to run once as it's issuing a start command to the WAS application server.

    If you need to know which job - the autostart or the scheduled - is responsible for starting the WAS application server, change the name of the scheduled job (instead of MWP, make it MWP_1 or something) & change the job logging level to 4 00 *SECLVL to ensure you get a job log.

    FYI, when your application server is active, there is a .pid file created (in \\[IP Address\qibm\UserData\WebSphere\AppServer\V7\Express\profiles\[Profile]\logs\[Application Server] on our system).  It may be of use if you need your program to determine whether the application server is active or not.
    12,895 pointsBadges:
    report
  • ejaaje
    Hi Splat. thanks. it is running now.  I changed the name and submit immediate to see whether it is working or not. and it works. 

    ....+....1....+....2....+....3....+....4....+....5....+....
     ************Beginning of data**************               
    050050/QEJBSVR/SAPPSVR                                     
     ************End of Data********************               
      
    Question 1: , can i use this schedule job? means, i dont create the autojob. just i schedule this job to start after every IPL.                                                         
    Question 2:  Is there any issues if i only use this schedule to start the job. , or should i also create schedule job to stop?                                                    
                                                               
                                                               
                                                               
    170 pointsBadges:
    report
  • Splat
    ejaaje, Glad to know it's working.

    1)  Instead of scheduling the job to run after every IPL why not make it part of your startup process?  That way you know what kicked it off & don't have to worry about longer than usual IPLs & such.
                                                       
    2)  The primary application we were supporting - vendor supplied - was pretty bad at managing memory & we found it best to stop & start the application server (and associated HTTP servers) nightly.  It wasn't difficult to tie the process into the the day end procedures (that's what I used the existence of that .pid file for, to determine whether the application server had shut down).  I'd recommend just starting it following an IPL & keeping an eye on it.  If it gets balky or starts flooding QSYSOPR with messages you might want to consider stopping & starting it more frequently.

    Anyhow, glad it's worked out for you.
    12,895 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: