MQSeries.net :: View topic - RUNMQSC can't write output to Guardian file

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » RUNMQSC can't write output to Guardian file - MQ 5.3.1

Goto page 1, 2 Next

RUNMQSC can't write output to Guardian file - MQ 5.3.1

« View previous topic :: View next topic »

Author

Message

delta7

Posted: Fri Nov 21, 2008 8:00 am Post subject: RUNMQSC can't write output to Guardian file - MQ 5.3.1

Newbie

Joined: 21 Nov 2008
Posts: 4

Hi,

We have just installed MQ v5.3.1 on a Tandem Integrity node. A TACL macro we previously used with MQ 5.1 is failing to get output from RUNMQSC.

The macro uses edit files as input and output for RUNMQSC. For example, the input file, MQCMD, may contain the command 'Display Queue (*)'.

So the TACL command that the macro uses will be look like:

RUNMQSC /IN MQCMD, OUT MQRES/ venus.queue.manager

This command results in an error and an empty MQRES file that is locked open by OSTTY.

Does anybody know if this is an issue that has been fixed in the latest fix pack 5.3.1.4?

BTW, using runmqsc works fine in OSS and we can redirect input / output to files, so the problem seems to be related to the use of a Guardian out file.

Thanks

bruce2359

Posted: Fri Nov 21, 2008 8:06 am Post subject:

Poobah

Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.

Quote:

This command results in an error

What kind of error?
_________________
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.

delta7

Posted: Fri Nov 21, 2008 8:37 am Post subject:

Newbie

Joined: 21 Nov 2008
Posts: 4

Hi,

Here's example output, the command is abending. No EMS events raised. the command was ran under userid super.super and $OSS is a physical disk:

$OSS TEMP 68> run $system.zwmqbin.runmqsc /in mqcmd, out mqres2/
$OSS TEMP 68..
ABENDED: $X29A
CPU time: 0:00:00.010
3: Premature process termination with fatal errors or diagnostics

$OSS TEMP 69> fup copy mqcmd
display queue (*)
1 RECORDS TRANSFERRED
$OSS TEMP 70> fi mqres2

$OSS.TEMP

CODE EOF LAST MODIFIED OWNER RWEP PExt SExt
MQRES2 O 101 0 21NOV2008 16:30 255,255 NUNU 14 28
$OSS TEMP 71> fup listopens mqres2

$OSS.TEMP.MQRES2
PID MODE USERID SD MYTERM PROGRAM FILE NAME
254,01,1181 R/W-S 255,255 15 $ZTN0.#PTYKX71 $SYSTEM.SYS00.OSSTTY

fjb_saper

Posted: Fri Nov 21, 2008 9:56 am Post subject:

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

runmqsc should be run by a user in the mqm group. Is super.super member of that group?
_________________
MQ & Broker admin

mqjeff

Posted: Fri Nov 21, 2008 10:05 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Unlike everyone else who's posted here, I'm going to admit that I know nothing very much at all about HP-NSK (and hope that the resident expert, Luisfer, will drop by this thread soon and correct us all)...

It seems like you still don't have good error output, though. Unless there's system documentation that tells you what $X29A abend code means?

There's some small chance that it's a MQ permissions error like fjb_saper suggests - that you don't have permissions to see the objects you're trying to and so runmqsc is throwing an error message. Is there any data at all in the mqres2 file, that you can see?

What happens if you don't redirect the output to a file, but to the stdout... I mean
run $system.zwmqbin.runmqsc /in mqcmd /
or whatever the proper syntax is?

Michael Dag

Posted: Fri Nov 21, 2008 11:47 am Post subject:

Jedi Knight

Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)

I know nothing of HP-NSK either so this is a guess... , you have gone from MQ 5.1 to MQ 5.3.1 , is this a migrated QueueManager or a new one?

What happens if you create a new Qmgr lets say SAMPLE or TEST001
and does the command work then?
_________________
Michael

MQSystems Facebook page

LouML

Posted: Mon Nov 24, 2008 8:53 am Post subject:

Partisan

Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY

delta7 wrote:

Have you tried to FUP GIVE the mqres2 file to mqm.manager? I'ts currently owned by super.super.

What happens when you try the following:

run $system.zwmqbin.runmqsc /in mqcmd, out s.#mq/

run $system.zwmqbin.runmqsc /in mqcmd/
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude

delta7

Posted: Tue Nov 25, 2008 5:30 am Post subject:

Newbie

Joined: 21 Nov 2008
Posts: 4

I have now got the RUNMQSC to work correctly with input and output files BUT only if I'm using mqm.manager.

The Guardian RUNMQSC object has network security so that other users can access it:

$SYSTEM.ZWMQBIN

CODE EOF LAST MODIFIED OWNER RWEP PExt SExt
RUNMQSC 800+ 80480 20NOV2008 11:33 251,255 NNNU 28 14000

When logged on as other users e.g. SUPER.SUPER, RUNMQSC works correctly as long as an output file is not used. e.g.

$OSS TEMP 4> run $system.zwmqbin.runmqsc /in mqcmd/
0791003, 5724-A39 (C) Copyright IBM Corp. 1993, 2007 All Rights Reserved.
Starting MQSC for queue manager venus.queue.manager.

MQSC > 1 : display queue (*)
AMQ8409: Display Queue details.
QUEUE(BLUE.QUEUE) TYPE(QLOCAL)
AMQ8409: Display Queue details.
QUEUE(ORANGE.QUEUE) TYPE(QLOCAL)

etc

Whenever an output file is specified, even if it is secured as available for all users and given to mqm.manager, the RUNMQSC will fail if the logged on user is not mqm.manager.

Still looking into the problem ... we suspect that this restiction is due to RUNMQSC in the OSS environment.

***

Regarding some of the questions raised in the replies ...

The $X29A was the process name of the process that abended (crashed). The abend is an abnormal end and is usually something like an arithmetic overflow, memory corruption etc.

When attempting to use to use RUNMQSC a non mqm.manager user with an output file, the file is just locked open and 0 bytes written to it ... we now have files locked open for several days with nothing written to them.

This is brand new installation of MQ 5.3.1; the earlier MQ 5.1 installation was on a different Tandem (HP NSK) node.

When trying to write to spooler location $s.#mq, RUNMQSC failed and the spooler entry was not created.

delta7

Posted: Wed Dec 03, 2008 7:55 am Post subject:

Newbie

Joined: 21 Nov 2008
Posts: 4

Hi,

A further update for anyone interested.

We have applied several patches so that our version of MQ is now:

$ mqver
Name: WebSphere MQ
Version: 531.4 FP5314
CMVC level: WMQ-5-3-1-4
BuildType: IKAP - (Production)

Using this version we can use the RUNMQSC utilty from Guardian with input / output files from users other than mqm.manager ... i.e. the functionality we had with MQ Series 5.1.

We have found what looks to be one bug though; when issuing a chstatus all command on a channel that hasn't been used we get a RUNMQSC reply of AMQ8420: Channel Status not found as we expect but then the RUNMQSC process abends and creates a saveabend file.

shield

Posted: Mon Mar 25, 2013 4:06 am Post subject:

Newbie

Joined: 25 Mar 2013
Posts: 4

Hi.

I'm starting MQ up via a TACL obey file containing several MQ commands to start:-

#OUTPUT = Start Queue Manager
strmqm /IN $ZHOME, TERM $ZHOME, OUT $ZHOME, NOWAIT/ QMGR_INSIDER
delay 10 seconds

#OUTPUT = Run Listener
runmqlsr/NOWAIT,IN $ZHOME, NAME $MQML,TERM $ZHOME,OUT $ZHOME/-t tcp -p 1414 -m Q

MGR_INSIDER
delay 10 seconds

#OUTPUT = Start Command Server
strmqcsv /IN $ZHOME, TERM $ZHOME, OUT $ZHOME, NOWAIT / QMGR_INSIDER
delay 10 seconds

#OUTPUT = Display Queue Manager status
dspmqcsv QMGR_INSIDER
delay 10 seconds

#OUTPUT = Display MQ version
dspmqver

All seems to work ok but occassionally the Command Server stops and I get a saveabend, which HP GNSC have analysed, finding that the TACL session has abended.

Originally, I didn't have $ZHOME specified in any of the MQ commands and since adding $ZHOME, I still get saveabends created, albeit only once a week.

Can you possibly explain how you're using term commands in your startup file?

Thanks

Dave

Vitor

Posted: Mon Mar 25, 2013 4:13 am Post subject:

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

shield wrote:

Can you possibly explain how you're using term commands in your startup file?

This thread's 5 years old & the OP has not posted since; I'd not hold your breath waiting for a response.

I'd also like to hope you're not using the same version as the OP and hence the software has changed a little. Is my hope justifed?
_________________
Honesty is the best policy.
Insanity is the best defence.

shield

Posted: Mon Mar 25, 2013 4:28 am Post subject:

Newbie

Joined: 25 Mar 2013
Posts: 4

Yep, still using version 5.3.1.4, although 5.3.1.9 is available but cannot see any references to saveabend creation within the release notes, albeit by upgrading it 'may' resolve this issue.

shield

Posted: Mon Mar 25, 2013 4:31 am Post subject:

Newbie

Joined: 25 Mar 2013
Posts: 4

PS. My main question was concerning the use of TACL 'run' term parameters and if this was ok to use, as HP GNSC suggested it might fix my saveabend problem but so far, it hasn't.

Remember, HP do not support MQ, hence my question to this forum and searching the IBM release notes.

LouML

Posted: Mon Mar 25, 2013 4:32 am Post subject:

Partisan

Joined: 10 Nov 2005
Posts: 305
Location: Jersey City, NJ / Bethpage, NY

Getting a message from siteadmin@mqseries.net this morning brought back many warm memories of my Tandem NonStop days and my reply of almost 5 years ago! Funny, the OP never directly answered my question.

Also, it's been almost six years since I've worked on Tandem.

Have you tried changing the TERM to a virtual terminal process, like $VHS or something? Usually, a TACL will abend if the terminal specified by TERM is gone when the process attempts to write to it. Was the value specified by TERM another TACL process that has been stopped?
_________________
Yeah, well, you know, that's just, like, your opinion, man. - The Dude

shield

Posted: Mon Mar 25, 2013 4:45 am Post subject:

Newbie

Joined: 25 Mar 2013
Posts: 4

The term value I've specified is the Tandem home terminal, i.e. where the Console directs its output, so it never shuts down. $ZHOME is always persistent.

I could try a virtual terminal process, such as $ZVHS. Originally, I didn't have a hard coded hometerm specified within my run params, so when I logged off my TACL session, the term name would have disappeared from the system.

i'll give it a go and see how it goes but bizarrely, the MQ Command Server continues to run with $ZHOME as the terminal name butonce a week the Command Server stops, with the communications process stopping, although $ZHOME continues to run.

HP GNSC have analysed the original saveabend showing the TACL session had abended but this was without the name $ZHOME process; however, it still abends with $ZHOME being named.

Thanks for your feedback.

Display posts from previous:

Goto page 1, 2 Next

Page 1 of 2

MQSeries.net Forum Index » General IBM MQ Support » RUNMQSC can't write output to Guardian file - MQ 5.3.1

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP