跳到主要內容

IBM MQ 5.3 如何匯出Qmgr

使用IBM MQ探險家也沒有匯出的功能,這樣其實在一些備份或是Cluster時,滿困擾的,不過你也知道IBM就是喜歡用SupportPacs等等的方式,ms03這個SupportPacs就是可以匯出Qmgr中所有的資訊也可以選擇想要的,以下是他的連結
http://www-1.ibm.com/support/docview.wss?rs=171&q1=mA1J&uid=swg24000673&loc=en_US&cs=utf-8&lang=en

若是Window的版本可以直接使用,若是unix或是linux系列的就請重新編譯了﹝makeFile﹞我有試過在RHEL編譯使用是可以的。

※請注意一定要在有安裝MQ的Server方可執行喔

使用方式如下:
saveqmgr -m xxx -v 53 -o xxx.cfg

-m 指定需要匯出的Qmgr名稱
-v 版本
-o 匯出後檔案名稱

以下是相關參數的列表
Usage is:
./saveqmgr. [options], where [options] are one or more of the following optional switches
-h | -? : gives help (this)
-v version : determines which version of MQSC to generate
and can be '2','5','51','52','53' or '6'
The default is to generate mqsc at the version of the connected queue manager
-m lqmgr : is the name of the local qmgr to connect (MQCONN)
-r rqmgr : is the name of the remote qmgr (XMITQ name)
-f [file] : allows the output file to be named,
if -f is not specified, the output file defaults to SAVEQMGR.TST
if -f is specified without a filename, it is named "qmgrname".MQS.
-o : specifies to replace (overwrite) the output file
if the -o flag is not specified, then the default is to append if the file exists
(on iSeries, *REPLACE,*APPEND must be specified after the -o flag)
-F [file] : behaves the same as -f except no header line is created in the output file
(and CURDEPTH, ALTDATE and ALTTIME are not reported)
-c : directs output to STDOUT and overrides use of -f flag
-s : suppress creation of objects that begin with "SYSTEM*"
-R : create RESET CHANNEL commands for non-client/svrconn channels
-p : Create 'local queue' definitions from PERMDYN queues.
-i : Ignore 'pcf' error codes 'damaged object' 'unknown object'.
Sets RetCode to WARNING if this error encountered.
-q : Quiet mode, do not issue warning about unknown PCF attributes
-1 : generate entire DEFINE command on one line (which does NOT include ALTDATE etc)
-2 : on a 2nd line, generate the DEFINE as a comment (which DOES include ALTDATE etc)

The Client version of this program supports these additional flags:

If either the -a or -x switch is used, then MQCONNX will be used for the client connection
-a host : is the address of the host for a client connection (default is "localhost")
-x channel : is the SVRCONN name for a client connection (default is "SYSTEM.DEF.SVRCONN")
-C cipher spec : indicates to use an SSL cipher spec for this client connection
-k key repository : name of key respository directory if using SSL for client connection
-eX channel exit: X = 'y' for security, 's' for send, 'r' for receive
-dX "channel exit data": X = 'y' for security, 's' for send, 'r' for receive

Notes on the '-v' flag:

Normally, the "-v (version)" flag does not need to be specified. saveqmgr will
automatically generate the correct level of MQSC based on the CMDLEVEL setting
of the queue manager that it is connected to. So, if it is connected to a v5.3
queue manager, it will generate v5.3 compatible mqsc, regardless of the actual
level of saveqmgr itself. The "-v" flag should only be needed to generate back-level
MQSC. For example, if saveqmgr is connected to a V6 queue manager and you want to
generate v5.3 MQSC.

留言

這個網誌中的熱門文章

IReport中的條碼類別BcImage

最近有一個繳費單的專案,需要列印條碼,因為IReport本身就有提供列印條碼的功能,所以就用IReport設計繳費單然後再用Jasperreport API寫批次程式去產生PDF,資料量大概3000多筆(頁)拆成幾個檔案,可是就發生了一個問題居然發生部分繳費單的條碼有問題,看了一下程式研判是Race Condition因為程式採用的是多執行緒,若是依序個別產生是不會有問題,但是同時執行的時候就會亂掉,而且都錯在條碼,令我覺得很奇怪,後來我查了一下發現it.businesslogic.ireport.barcode.BcImage 類別我猜是這裡的問題,就先加上synchronized重新編譯在去執行,嘿嘿條碼就對了,做了一下壓測也正常,程式碼如下,不過這樣事不是對了可能還要仔細查查看。 public class BcImage { private static net.sourceforge.barbecue.Barcode bc = null; public synchronized static net.sourceforge.barbecue.Barcode getBarcode() { return bc; } public synchronized static BufferedImage getBarcodeImage(int type, Object aText, boolean showText, boolean checkSum) { return getBarcodeImage(type, aText, showText, checkSum,"",0,0); } public synchronized static BufferedImage getBarcodeImage(int type, Object aText, boolean showText, boolean checkSum, String applicationIdentifier, int width, int height) { // 2of7, 3of9, Bookland, Codabar, Code128,...

Ext-Js Grid + DWR

Ext-Js中有Grid的sample,想說試試看加上DWR的效果如何?感覺上還不錯,以下是我參考Ext-Js附的grid array sample,加上DWR調整一下的code,我想可能還要加上資料在Loading的效果會比較好。 array-grid.js Ext.onReady(function(){ Ext.state.Manager.setProvider(new Ext.state.CookieProvider()); // example of custom renderer function function change(val){ if(val > 0){ return ' ' + val + ' '; }else if(val ' + val + ' '; } return val; } // example of custom renderer function function pctChange(val){ if(val > 0){ return ' ' + val + '% '; }else if(val ' + val + '% '; } return val; } //要設定Dwr傳回的Map的對應格式 var recordType = Ext.data.Record.create( [ {name:"reportid",mapping:"reportid",type:"string"}, {name:"reportName",mapping:"reportName",type:"string"} ] ); var myReader = new Ext.data.JsonReader( { totalProperty:"totalSize", root:"data" },recordType ); // create the data store //這裡是很重要的,這裡還可以加上listener等等的屬性喔 var store = new Ext.da...