Script to bring down multiple SBS on multiple LPAR’s

15 pts.
Tags:
AS/400 scripts
V6R1
I'm wanting to write script(s) where multiple (V6R1)LPAR's will have different SBS's brought down, ROBOT, JDE applications brought down, and SQL packages deleted. Once verified all brought down cleanly, another script(s) will bring them all back up on their perspective LPAR's cleanly. Of course I will be notified of any issues where recycle isn't working correctly... Can someone point me where I can view examples of scripts. Any advice is welcomed on my new project...

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.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 4  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.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    What kind of "script" are you looking for? AIX? REXX? Qshell? Something else? Although some discussions refer to CL programming as 'scripting', it is definitely very different. This isn't as simple as it might seem. Bringing subsystems down shouldn't be done in a production environment without preparation. Ending the subsystems is easy, but handling all of the possible active work going on within a subsystem can be difficult. Asking a question for an example 'script' indicates some uncertainty about system management software. A multi-LPAR system with a JDE environment, ROBOT products and others indicates a reasonably sophisticated production environment that shouldn't be shut down without care. Simply coordinating management of multiple system images brings challenges of its own without consideration for applications that might be active. What programming background will you be working from? Tom
    125,585 pointsBadges:
    report
  • Splat
    Don't know if this is quite what you're asking, but we use the QWCRSVAL and QWCRSSTS APIs to retrieve the system serial number, system name, and partition identifier. That information is used to determine the processes for starting and stopping the various partitions and/or systems.
    7,625 pointsBadges:
    report
  • Mlegarde
    This is a normal recycle of an application I do on weekends. Client is aware of the JDE application coming down. This was going on before I arrived to the company. I'm just looking to make my life a little easier where I'm not manually running it. I'm looking to automate the recycle of this application. I will using STRPDM.
    15 pointsBadges:
    report
  • TomLiotta
    Client is aware of the JDE application coming down. Using JDE as a base example, my comments weren't about making the application unavailable. They were about correctly bringing down servers that may be in use by an application. If the *DATABASE host server has been serving connections into the JDE database, using ENDSBS to end host server connections can (and eventually probably will) cause damage to the database. Most often it can be corrected with RCLSTG *DBXREF because only the system catalog synchronization is disturbed. One difficulty can be that you won't know that it all must be resynchronized until days or weeks later. In the meantime, odd inexplicable errors get signaled that seem to go away simply by logging off and back on or by rerunning jobs or other weird actions. But every once in a while, actual object damage is caused to tables in the database. Recovery from that can be painful. So, instead of ENDSBS used to force jobs to shutdown, the proper sequence depends on what's going on in the subsystem. For QUSRWRK, for example, it should include ENDHOSTSVR *DATABASE ENDACTCNN(*DATABASE) to cause connections to be ended before the server jobs are ended. Then, before ENDSBS QUSRWRK is done, the jobs in the subsystem should be tested to see if they're gone. If they aren't, then ENDSBS should not be run yet. The *DATABASE server is only one of many server functions. And QUSRWRK is only one example subsystem. And each LPAR may be configured to break work into different subsystems or to have different kinds of work. But all of that is just warning that there are meaningful risks. It's separate from your question. What kind of “script” are you looking for? And What programming background will you be working from? (I.e., what languages have you worked with?) If 'scripts' are provided, is there a language that'd you'd be more comfortable with? Because this involves system control functions, CL is most appropriate. If you understand that CL is a compiled language rather than a 'script', it won't be a problem. Also, if you're already going through steps manually, those steps might easily be converted into the exact 'script' that you want. If you simply listed the steps, we could probably turn them around quickly. Tom
    125,585 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.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

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

Following