| Author |
Message
|
| Mahima |
 Posted: Mon Apr 09, 2012 6:46 am Post subject: MS03/Saveqmgr on ISeries/AS400 |
 |
|
Newbie
Joined: 09 Apr 2012
Posts: 5
|
Hi I am very new to AS400 machines,
I need to take backup of AS400 QueueManager using MS03 for iseries.
I followed the steps in the AS400read.me file. like
ftp> cd QGPL
ftp> bin
ftp> put MS03
Back on the AS/400, issue:
CRTSAVF (QGPL/MS03)
RSTLIB SAVLIB(MS03) DEV(*SAVF) SAVF(QGPL/MS03)--for this command its telling like you have no authority to restore library.
STRMQMCSVR MQMNAME(<QMGRNAME>)
MS03/QSAVEQMGR LCLQMGRNAM(<QMGRNAME>) FILENAME('MS03/QMQSC(<QMGRNAME>)')--for this command its giving like QSAVEQMGR command not there in MS03 file.
Help me in doing this.
Thank you
Mahima
 |
|
| Back to top |
|
 |
| yesar |
| Posted: Mon Apr 09, 2012 11:45 am Post subject: |
|
|
Newbie
Joined: 09 Apr 2012
Posts: 4
|
Step 1. End the MQ channels with one of the following commands:
WRKMQMCHL (then choose option 15)
ENDMQMCHL CHLNAME(some name) OPTION(*IMMED)
Step 2. Exit the Administrator Utility if running.
Step 3. End the Command Server with the command:
ENDMQMCSVR MQMNAME(QMNAME) Option(*IMMED)
Step 4. Reset the media recovery point with the command:
RCDMQMIMG OBJ(*ALL) OBJTYPE(*ALL)
Step 5. End the queue manager:
ENDMQM MQMNAME(queue manager name) OPTION(*IMMED)
Step 6. Sign off and sign on again.
Step 7. Restart the queue manager with STRMQM.
Step 8. Display the QSYSOPR message queue with DSPMSG QSYSOPR and
look for AMQ7460 and AMQ7462 messages. Write down the
receivers¢ numbers in these messages.
48 MQSeries Backup and Recovery
AS/400
Step 9. Issue WRKOBJPDM LIB(QMQMDATA). Delete the unwanted journal
receivers with the help of AMQ7462 and AMQ7460 messages. For
example, if AMQ7462 indicates receiver, AMQA000050 and
AMQ7460 indicate receiver AMQA000054, then delete any receiver
before AMQA000050. This will help reduce the number of
unwanted journal receivers present in QMQMDATA prior to
backing up QMQMDATA.
Further information on this aspect of journal receiver management
can fe found in 3.1.3.1, “Ensuring the Required Receivers Are
Present” on page 40.
Note: During deletion, you may get the following message:
CPA7025 Receiver AMQA000042 in QMQMDATA never fully saved. (I C)
Enter ²I² to ignore it.
Also, journal receivers must be deleted in the same order in which
they were attached. Additional information is given in 3.1.4.4,
“Deleting Journal Receivers” on page 46.
Step 10. Quiesce MQSeries: CALL QMQM/AMQIQES4.
Step 11. Tidy up the cache storage: CALL QMQM/AMQIQEM4.
Step 12. Save the local and remote journals:
SAVOBJ OBJ(AMQAJRN AMQRJRN) LIB(QUSRSYS) OBJTYPE(*JRN)
Step 13. Save the QMQMPROC library: SAVLIB LIB(QMQMPROC).
Step 14. Save the QMQMDATA library: SAVLIB LIB(QMQMDATA).
Note: It is a good practice to display the joblog of the save to
make sure that all the objects are saved.
Step 15. This ends the backup procedure. |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Apr 09, 2012 1:07 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| You can run MS03 on another platform - but accessing the i-series QM remotely - this is generally easier. We have a Unix script that backs up around 50 other QMs using this client channel method. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Apr 09, 2012 1:21 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| yesar wrote: |
| Step 15. This ends the backup procedure. |
that backs up the queue manager.
It doesn't help run saveqmgr.
I've never been good at the iseries side of this.
Hopefully the current maintainer of ms03 will provide some assistance.
 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Apr 09, 2012 8:43 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I thought that on Iseries like on zOS you would be using CSQUTIL to do this... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Apr 09, 2012 9:24 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| fjb_saper wrote: |
| I thought that on Iseries like on zOS you would be using CSQUTIL to do this... |
iSeries is not z/OS. i uses a UNIX-like filesystem, and really long commandnames.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Mahima |
| Posted: Tue Apr 10, 2012 12:36 am Post subject: This ends the backup procedure |
|
|
Newbie
Joined: 09 Apr 2012
Posts: 5
|
| Thank you.But I think in this you were not using MS03 saveqmgr. I need to take the back up using saveqmgr for iseries. |
|
| Back to top |
|
|
| Mahima |
| Posted: Tue Apr 10, 2012 1:33 am Post subject: |
|
|
Newbie
Joined: 09 Apr 2012
Posts: 5
|
You can run MS03 on another platform - but accessing the i-series QM remotely - this is generally easier. We have a Unix script that backs up around 50 other QMs using this client channel method.
May I know how to do that for other remote QM's we need saveqmgrc file but for AS400 there is no saveqmgrc file.I could see only one file i.e;MS03
Thank you
Mahima. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Apr 10, 2012 2:36 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| No, you run MS03 on another platform (Windows, Unix, Linux) and connect to the i-series as a MQ client. |
|
| Back to top |
|
|
| yesar |
| Posted: Tue Apr 10, 2012 3:44 am Post subject: |
|
|
Newbie
Joined: 09 Apr 2012
Posts: 4
|
If you know AS400 OS..then these are the easy steps.
1. Check the name of the journal libraries and save them to save file(s)
a. Enter the command wrkmqm to display all queue managers on the system
b. Select option 5 to display the queue manager details
c. Page down one page to display the name of the queue manager library for this queue manager
d. Stop the queue managers using the following command where QmgrName is the name of the queue manager to stop
ENDMQM MQMNAME(QmgrName) OPTION(*IMMED) ENDCCTJOB(*YES) RCDMQMIMG(*YES)
e. Create a save file for the queue manager library with the same name as the library
f. Save the library using the SAVLIB command to the save file
g. If there are more than one queue manager configured on the system repeat point b to f for each queue manager configured
2. Save the IFS objects
a. Create a save file with the name QM_IFS
b. Save the WebSphere MQ IFS folder to the save file. In this sample the save file have been created in the library MQS600
SAV DEV('/qsys.lib/mqs600.lib/qm_ifs.file') OBJ(('/qibm/userdata/mqm/*'))
3. Send all the save files to the new hardware using FTP
TO RESTORE:
Install MQ if you are moving to newer version or other system
2. Restore the queue manager library
a. Restore the libraries saved on the source system using the ordinary RSTLIB command
3. Restore the IFS objects
a. Restore the IFS objects using the command
RST DEV('/qsys.lib/mqs600.lib/qm_ifs.file') OBJ(('/qibm/userdata/mqm/*')) |
|
| Back to top |
|
|
| Mahima |
| Posted: Tue Apr 10, 2012 4:30 am Post subject: |
|
|
Newbie
Joined: 09 Apr 2012
Posts: 5
|
No, you run MS03 on another platform (Windows, Unix, Linux) and connect to the i-series as a MQ client.
If you don't mind can you tell me how to do that.
Thank you. |
|
| Back to top |
|
|
| yesar |
| Posted: Tue Apr 10, 2012 4:52 am Post subject: |
|
|
Newbie
Joined: 09 Apr 2012
Posts: 4
|
1. Use the client version (saveqmgrc) of this SupportPac to connect to the
queue manager for which you wish to save the definitions. You may use either
an MQSERVER variable, client channel tables or pass the connection information
as parameters to 'saveqmgrc'.
2. Connect to a local queue manager that has channel definitions to the queue
manager for which you wish to save the definitions. In that case, you would
specify a '-m' flag naming the local queue manager and a '-r' flag naming the
remote queue manager. |
|
| Back to top |
|
|
| yesar |
| Posted: Tue Apr 10, 2012 5:36 am Post subject: |
|
|
Newbie
Joined: 09 Apr 2012
Posts: 4
|
Here are the steps:
1) Create a batch file called SaveRemQmgr.bat
2) Add saveqmgrc -r %1 -a %2 -x SYSTEM.ADMIN.SVRCONN -f -z to batch file if you are using admin server connection channel.
3)place this batch file and saveqmgrc.exe into some folder( c:\SAVEQMGR).
4) open command line and cd c:\SAVEQMGR
5) execute batch file by supplying the -r which is remote q manager name and -a is host name.
ex :SaveRemQmgr.bat QMNAME hostname(1414)
hope that helps. |
|
| Back to top |
|
|
| zpat |
| Posted: Tue Apr 10, 2012 6:12 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
It's all in the support pac documentation. That's how we found out. Plus you can try it out. Learn by doing..
Try saveqmgrc ?
You can use a CCDT rather than passing all the connection details. |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Tue Apr 10, 2012 6:27 am Post subject: Re: MS03/Saveqmgr on ISeries/AS400 |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
| Mahima wrote: |
Hi I am very new to AS400 machines,
I need to take backup of AS400 QueueManager using MS03 for iseries.
I followed the steps in the AS400read.me file. like
ftp> cd QGPL
ftp> bin
ftp> put MS03
Back on the AS/400, issue:
CRTSAVF (QGPL/MS03)
RSTLIB SAVLIB(MS03) DEV(*SAVF) SAVF(QGPL/MS03)--for this command its telling like you have no authority to restore library.STRMQMCSVR MQMNAME(<QMGRNAME>)
MS03/QSAVEQMGR LCLQMGRNAM(<QMGRNAME>) FILENAME('MS03/QMQSC(<QMGRNAME>)')--for this command its giving like QSAVEQMGR command not there in MS03 file.
Help me in doing this.
Thank you
Mahima
|
You need to correct the part in bold. Run the command as QSECOFR or ask your sys admin to run it for you. Once you've successfully restored the MS03 library you will be able to run the QSAVEQMGR program (assuming you have access.
MS03/QSAVEQMGR (hit PF4):
SAVEQMGR: SAVE OBJECTS DEFS (QSAVEQMGR)
Type choices, press Enter.
Version of MQSC to Generate . . 700 520, 530, 600, 700
Local QMgr Name (for MQCONN) . .
Remote QMgr Name (XMITQ name) .
MQSC Output file . . . . . . . . '*CURLIB/QMQSC(SAVEQMGR)'
Output Mode . . . . . . . . . . *APPEND *APPEND, *REPLACE
Redefine system objects . . . . *YES *YES, *NO
Make GRTMQMAUT commands . . . . *NO *YES, *NO
GRTMQMAUT Command Ouput file . . '*CURLIB/QMAUT(SAVEQMGR)'
Make qlocal defs from PERMDYN . *NO *YES, *NO
Ignore DAMAGED OBJECT errors . . *NO *YES, *NO |
|
| Back to top |
|
|
|
|
