Humm, Humph...
My perspective is that you are essentially requesting a service from MVS/JES. To
paraphrase, that request is: "run this job". Rather than enhancing the trigger
monitor, I suggest abstracting the layer that is responsible for satisfying the
request into a program that you contr
Does anybody know how to resolve a BIP0014E errror. I am trying to remove
a message from my message set and I keep get this error. So, now I can not
delete my message set because it claims that the specific message is
checked out. Any insight is greatly appreciated.
Thank you. Arg!
Instructio
(See attached file: temp.txt)
Are you sure your setup is correct. Here is how we do it. Also you
mentioned a PEND at the end of the PROC are you sure you need this since
the proc is cataloged not instream.Please note the space between '//
and exec' we do not user the userdata field at al
Thanks Roger, Im gonna give this another shot tomorrow. I am probably
missing somethin really small and insignificant.
What I was able to get done now is that I have a member that works fine when
I manually sub it. I cut and paste its JobCard out and stuck it into MA12's
JobCard parameter.
MA12 n
Humm,
I think you misunderstood me. I meant that you stop using MA12 and write your
own trigger monitor program (C or PLI or COBOL). Your new trigger monitor
program would use the APPLCID and/or USERDATA as they wish.
But most companies don't want to have a custom written trigger monitor. Plus
The INTEGERSIGNED field (if memory serves me correctly) is
treated as a Zoned Decimal field. In other words, the low
order byte will have the high order 4 bits set to "C" for
positive and "D" for negative numbers (system preferred
signs). I can't remember if it accepts "A" and "F" for
positive and
I would love to do the simple one Rog.
If I put @TSMT00.MQ.CNTL(MQEX702V) in USERDATA, but what would I put in
APPLCID?
This assume MQEX702V can be submitted stand alone.
-Original Message-
From: Roger Lacroix [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 4:11 PM
To: [EMAIL
I believe there was a member of the NJ MQ User's Group who had written a TSO
method described below. I went to the site but did not see it.
On www.google.com a search brought up a TSO method (looks like PL1) on topic
at the following site:
http://www.mainframeweek.com/code/showcode.php/0014/mw14m
Hi,
Over the years, I have written a couple of trigger monitors to submit JCL (with
a JOB card) rather than a PROC.
It is really straight forward. You can make a simple one or a more robust
trigger monitor. The simple one would have the PDS(member) in the USERDATA
field. For the complex one, y
As you may already know, you don''t have to use MA12
for batch triggering. Instead, you can get CICS to
trigger the JCL. I think the latter is just easier set
up.
Just a thought
Ruzi
--- "Bullock, Rebecca (CSC)" <[EMAIL PROTECTED]> wrote:
> Peter, I don't use MA12 and we're not a JES3 shop,
> b
No, I never had it working. I mean, I had the job itself working A-OK when I
submitted SUB from inside the member. But someone told me I could not just
submit a JCL member like this from a process definition. I had to change it
to a proc, which are the changes I made below and the reason I posted t
Peter, I don't use MA12 and we're not a JES3 shop, but was it working before
you shut it down? Could it be that a different userid is now associated with
it, and that userid is causing it to fail in the SMF exit? I'd talk to the
SMF exit person and see what would trigger a failure and take it from
Peter -
Process name and content
EMAIL.SMTP.MSGS
USED TO PROCESS MAINFRAME EMAI
TO USERS IN
MVS
//*S010EXE EXEC PGM=MQMAIL
//EMAIL DD SYSOUT=(Q,SMTP)
//SYSOUT DD SYSOUT=*
//UTLITYF DD DUMMY
The trigger monitor is up and running. I can send the shutdown message to it
via CKTIEND and it shuts down as expected. So I start it back up and try to
drop a message into the triggered queue. The triggered queue name is
MQT1.LOCAL.QUEUE and the process definition is named MQT1.LOCAL.QUEUE as
well
I have MQ V5.2.1 with CSD6 and when I use WTS, I still can't see any MQ
objects.
"Crupi,
Anybody out there using JBOSS and WMQ?
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
That's correct. Signed decimal and packed fields do not survive data conversion. The
best practice is that a message should be all binary and not converted or all
character if it needs to be converted. Bottom line--all fields in the message should
be defined in display formats (PIC X or PIC 9...
Bobbee,
You passed the interview, but are you certified?
Regards,
John Dawson
-Original Message-
From: Robert Broderick [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 11:21 AM
To: [EMAIL PROTECTED]
Subject:Re: SOC 7 error while displaying S99 Fields in C
The s99 field implies that the data in the sending field is a valid numeric
field with the last byte containing a valid numeric sign.
If my assembler isn't t rusty. What happens behind the the curtain is
that the compiler generates instructions to convert the Zone Decimal field
to pack (which d
Someone correct me if I am wrong It has been in the
back of my mind that the S9 and COMP-3 fields have to
be changed ,before they are MQPUTed, to flat PIC 9 s
without the assumed sign and COMP-3, and that the
assumed sign to be coded as a one byte separate filed
-- for conversion purposes. No?
I will be out of the office starting August 12, 2003 and will not return
until August 28, 2003.
I am out of the office on vacation until 28th August I will respond to your
message when I return.
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Gu
What does the MQ message look like? Can you post a hex dump of the record???
bb
PS Keep the layout in the "REPLY"
From: Juni Per <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: SOC 7 error while displaying S99 Fields in COBOL (WMQI 2.1)
Da
Hi ,
I have the following COBOL copy book imported into WMQI(2.1 WinNT)
06 TESTVARIABLES. 07 TESTINPUT. 08 INTEGERNOSIGN PIC 99. 08 INTEGERSIGNED PIC S99. 08 DECIMALNOSIGN PIC 99V99. 08 DECIMALSIGNED PIC S99V99. 08 COMP3NOSIGN
the following is from Symantec. since we are using e-mail, I wanted to save
time and cycles by putting in the message rather than the URL. please
forgive me.
go to www.symantec.com for more...
- EARmerc -
P.S> I am posting this because someone on the CICS list just reported
receiving the virus. It
Title: CA Monitoring Agents for MQ
We are looking at the possibility of replacing our current MQ monitoring solution with Unicenter Management for MQSeries (on Windows 2000) and SysView E WebSphere MQ Option (on z/OS) feeding into a Unicenter console. The reasoning behind this move is to con
Yes, but use CSD 3 , or better
4, as there were a few APARs that when in that fixed problems I had.
You can issue the command:
mqsiimpxmlschema -f ,
where the config file contains the schema name etc. An example is:
#
# Parameters file for MQSI V2.1 XML
Schema importer
#
# Name of the message
Hi Enrico,
We had the same requirement (as well as a DR solution) ages ago and elected to go with
EMC SRDF hardware mirroring as anything else was just too complex and the solution
catered for our requirement. I'm sure you would have considered this option as well.
Hope this helps.
Margherita...
Title: WMQ & Microsoft Terminal Services...
You
need to be with MQ V5.2 CSD03 for WTS to be officially supported by
IBM.
Hope
this helps.
-Original Message-From: Antony Boggis
[mailto:[EMAIL PROTECTED]Sent: Wednesday, 27 August 2003 2:31
AMTo: [EMAIL PROTECTED]Subject: WMQ &
28 matches
Mail list logo
