Re: RECEIVE ORDER ERROR

2009-05-04 Thread Skip Robinson
...@bama.ua Subject .edu Re: RECEIVE ORDER ERROR 04

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Edward Jaffe
Brian Peterson wrote: Yet another problem I never saw because I always use CONTENT(ALL) instead of CONTENT(RECOMMENDED) for RECEIVE ORDER. http://alabamamaps.ua.edu/cgi-bin/wa?A2=ind0904L=ibm-mainP=R14311 You too could see the light and choose to move to using CONTENT(ALL).. If I did

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Mark Zelden
On Tue, 28 Apr 2009 08:05:47 -0700, Edward Jaffe edja...@phoenixsoftware.com wrote: Brian Peterson wrote: Yet another problem I never saw because I always use CONTENT(ALL) instead of CONTENT(RECOMMENDED) for RECEIVE ORDER. http://alabamamaps.ua.edu/cgi-bin/wa?A2=ind0904L=ibm-mainamp;P=R14311

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Chase, John
-Original Message- From: IBM Mainframe Discussion List On Behalf Of Edward Jaffe Brian Peterson wrote: Yet another problem I never saw because I always use CONTENT(ALL) instead of CONTENT(RECOMMENDED) for RECEIVE ORDER.

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Edward Jaffe
Chase, John wrote: If I did that, wouldn't I have all of the PTFs that haven't yet gone through CST? Yes, but you can APPLY by SOURCEID(RSU*). Right now, I just RECEIVE ORDER CONTENT(RECOMMENDED), whatever comes back comes back, and I APPLY *all* of it with a canned job stream

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Richard Peurifoy
Edward Jaffe wrote: Chase, John wrote: If I did that, wouldn't I have all of the PTFs that haven't yet gone through CST? Yes, but you can APPLY by SOURCEID(RSU*). Right now, I just RECEIVE ORDER CONTENT(RECOMMENDED), whatever comes back comes back, and I APPLY *all* of it with a

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Edward Jaffe
Richard Peurifoy wrote: If you want to apply all RSU maintenance, you can specify RSU* on the APPLY. How does the RSU SOURCEID find its way to a PTF I previously RECEIVEd? Does SMP/E add missing SOURCEIDs automatically when I do RECEIVE ORDER? -- Edward E Jaffe Phoenix Software

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Eatherly, John D[EQ]
Hold data would add the SOURCEIDs after the PTF is received. Thanks John Eatherly How does the RSU SOURCEID find its way to a PTF I previously RECEIVEd? Does SMP/E add missing SOURCEIDs automatically when I do RECEIVE ORDER?

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Edward Jaffe
Eatherly, John D[EQ] wrote: Hold data would add the SOURCEIDs after the PTF is received. OK. In that case, the suggestion is that I use RECEIVE ORDER CONTENT(ALL) and use APPLY SOURCEID(RSU*) to ensure only recommended maintenance gets applied. All other received service waits in my PTS

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Richard Peurifoy
Edward Jaffe wrote: Richard Peurifoy wrote: If you want to apply all RSU maintenance, you can specify RSU* on the APPLY. How does the RSU SOURCEID find its way to a PTF I previously RECEIVEd? Does SMP/E add missing SOURCEIDs automatically when I do RECEIVE ORDER? I can't speak to

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Bob Rutledge
Ed, If you start at http://www-03.ibm.com/servers/eserver/zseries/zos/servicetst/ and sniff around and about, you'll eventually find most of the answers you're looking for. Bob Edward Jaffe wrote: Richard Peurifoy wrote: If you want to apply all RSU maintenance, you can specify RSU* on

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Mark Zelden
On Tue, 28 Apr 2009 13:11:43 -0700, Edward Jaffe edja...@phoenixsoftware.com wrote: Chase, John wrote: If I did that, wouldn't I have all of the PTFs that haven't yet gone through CST? Yes, but you can APPLY by SOURCEID(RSU*). Right now, I just RECEIVE ORDER CONTENT(RECOMMENDED), whatever

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Mark Zelden
On Tue, 28 Apr 2009 13:38:57 -0700, Edward Jaffe edja...@phoenixsoftware.com wrote: Richard Peurifoy wrote: If you want to apply all RSU maintenance, you can specify RSU* on the APPLY. How does the RSU SOURCEID find its way to a PTF I previously RECEIVEd? Does SMP/E add missing SOURCEIDs

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Edward Jaffe
Mark Zelden wrote: Not any extra work at all. It's just changing where the filter is. Currently you filter at the source by selecting CONTENT(RECOMMENDED). If you change to CONTENT(ALL) and change your APPLY JCL to SOURCEID(RSU*), you are applying the same service. The PRO is that you

Re: RECEIVE ORDER ERROR

2009-04-28 Thread Chase, John
-Original Message- From: IBM Mainframe Discussion List On Behalf Of Mark Zelden On Tue, 28 Apr 2009 13:11:43 -0700, Edward Jaffe wrote: Chase, John wrote: If I did that, wouldn't I have all of the PTFs that haven't yet gone through CST? Yes, but you can APPLY by

Re: RECEIVE ORDER ERROR

2009-04-27 Thread Brian Peterson
Yet another problem I never saw because I always use CONTENT(ALL) instead of CONTENT(RECOMMENDED) for RECEIVE ORDER. http://alabamamaps.ua.edu/cgi-bin/wa?A2=ind0904L=ibm-mainP=R14311 You too could see the light and choose to move to using CONTENT(ALL).. Brian On Sat, 25 Apr 2009 22:00:52

Re: RECEIVE ORDER ERROR

2009-04-26 Thread Paul Gilmartin
On Sat, 25 Apr 2009 21:09:48 -0500, Field, Alan C. wrote: I've asked our developers to investigate what we can do to clear up this problem with the cancelled PTF that is co-req'd by the PTFs in SDM and DSS. HSM PTF's UA46642 UA46641 UA46640 were created and now closed COR, and these supercede

Re: RECEIVE ORDER ERROR

2009-04-26 Thread Field, Alan C.
Sent: Sunday, April 26, 2009 10:07 To: IBM-MAIN@bama.ua.edu Subject: Re: RECEIVE ORDER ERROR On Sat, 25 Apr 2009 21:09:48 -0500, Field, Alan C. wrote: I've asked our developers to investigate what we can do to clear up this problem with the cancelled PTF that is co-req'd by the PTFs in SDM and DSS

Re: RECEIVE ORDER ERROR

2009-04-26 Thread Paul Gilmartin
On Sun, 26 Apr 2009 15:08:35 -0500, Field, Alan C. wrote: Here's more of the explanation: Order B8456491 was Rejected at 06:50:56 04/23/2009/TEXT TEXTUA46439 (CO-REQ) --- Fix not found/TEXT /COER_REJ . From the above, the order failed as Co-Req UA46439 was not found. Looking at UA46439, it has

RECEIVE ORDER ERROR

2009-04-25 Thread Edward Jaffe
Been getting this all weekend trying RECEIVE ORDER with CONTENT(RECOMMENDED). Am I the only one? HTTP/1.1 500 Internal Server Error. Date: Sun, 26 Apr 2009 01:33:27 GMT. Server: IBM_HTTP_Server/6.0.2.33 Apache/2.0.47 (Unix). Content-Length: 797. Content-Type: text/xml; charset=utf-8.

Re: RECEIVE ORDER ERROR

2009-04-25 Thread Field, Alan C.
Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Edward Jaffe Sent: Saturday, April 25, 2009 21:01 To: IBM-MAIN@bama.ua.edu Subject: RECEIVE ORDER ERROR Been getting this all weekend trying RECEIVE ORDER with CONTENT(RECOMMENDED). Am I the only one? HTTP

Re: RECEIVE ORDER ERROR

2009-04-25 Thread Edward Jaffe
Field, Alan C. wrote: Ed, No. I opened a problem with IBM. The problem is caused by a DFHSM PTF. [snip] I downloaded these PTFS then my RECEIVEORDER worked. That did it! Thanks! -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA

Re: Receive Order Error

2006-11-03 Thread Dick Renneke
Thanks to everyone who responsed to our Receive Order problem. We added GLOBALTCPIPDATA, GLOBALIPNODES, and COMMONSEARCH for RESOLVER. It fixed the problem and our Receive Order ran fine. Also, we authorized the PING command by added it to AUTHCMD in IKJTSOxx. Dick Very helpful information

Re: Receive Order Error

2006-10-31 Thread Chris Mason
: bit.listserv.ibm-main To: IBM-MAIN@BAMA.UA.EDU Sent: Friday, 27 October, 2006 8:50 PM Subject: Re: Receive Order Error With the SYSTCPD DD statement, we got this response - READY PING INETSD01.BOULDER.IBM.COM CS V1R7: Pinging host INETSD01.BOULDER.IBM.COM (207.25.253.62) READY END Unable to open

Re: Receive Order Error

2006-10-31 Thread Chris Mason
which need to open raw sockets, such a program being PING needing to run protocol ICMP. Chris Mason - Original Message - From: Brian Peterson [EMAIL PROTECTED] Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@BAMA.UA.EDU Sent: Friday, 27 October, 2006 9:33 PM Subject: Re: Receive Order Error

Re: Receive Order Error

2006-10-31 Thread Chris Mason
doesn't work. That helps resolve (sic) the issues here. Chris Mason - Original Message - From: Gibbons, Mark [EMAIL PROTECTED] Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@BAMA.UA.EDU Sent: Monday, 30 October, 2006 8:22 PM Subject: Re: Receive Order Error As far as I can tell. Internet

Re: Receive Order Error

2006-10-31 Thread Chris Mason
Message - From: Brian Peterson [EMAIL PROTECTED] Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@BAMA.UA.EDU Sent: Monday, 30 October, 2006 9:31 PM Subject: Re: Receive Order Error Mark, you're absolutely right. I've been looking at the books and they can set up a global search order using

Re: Receive Order Error

2006-10-30 Thread Gibbons, Mark
be very happy if I was wrong however. We don't have our tcpd data in the standard search order. Mark Date:Fri, 27 Oct 2006 15:33:02 -0500 From:=?iso-8859-1?Q?Brian_Peterson?= [EMAIL PROTECTED] Subject: Re: Receive Order Error OK - This result shows that the SYSTCPD DD statement

Re: Receive Order Error

2006-10-30 Thread Brian Peterson
Order Error OK - This result shows that the SYSTCPD DD statement is required for your RECEIVE job, and should fix your problem where RECEIVE is unable to resolve the inetsd01.boulder.ibm.com address - the unknown host error. 0:04 -0500, Dick Renneke wrote: With the SYSTCPD DD statement, we got

Re: Receive Order Error

2006-10-30 Thread Patrick O'Keefe
On Mon, 30 Oct 2006 11:22:10 -0800, Gibbons, Mark [EMAIL PROTECTED] wrote: ... The only method I've found that works is to have the data be found in the standard tcp search order. I'm not sure what the standard search order is (tcp config reference lookup a while back) but it will find:

Re: Receive Order Error

2006-10-30 Thread Brian Peterson
for client and orderserver. I'd be very happy if I was wrong however. We don't have our tcpd data in the standard search order. Mark Date:Fri, 27 Oct 2006 15:33:02 -0500 From:Brian Peterson Subject: Re: Receive Order Error OK - This result shows that the SYSTCPD DD statement is required

Re: Receive Order Error

2006-10-27 Thread Dick Renneke
The other message that we see are - CY1178 ftpStart: client operating in IPv4 only mode CZ0251 ftpOpen: entered SC0432 initConnection: entered SC0508 initConnection: Calling getaddrinfo() with inetsd01.boulder.ibm.com SC0517 initConnection: getaddrinfo() resptr 0 rc 1/EDC9501I The name does not

Re: Receive Order Error

2006-10-27 Thread Brian Peterson
Aha - that's the problem. Make sure that batch jobs such as your SMP/E RECEIVE command job include a valid DNS hierarchy. As is often the case, there's a bunch of different ways to specify this, but one way, which I use on my system, is to code a SYSTCPD DD statement, pointing to a parameter

Re: Receive Order Error

2006-10-27 Thread Dick Renneke
We added the SYSTCPD DD statement to the SMPE job but got the same messages. SC0508 initConnection: Calling getaddrinfo() with inetsd01.boulder.ibm.com SC0517 initConnection: getaddrinfo() resptr 0 rc 1/EDC9501I The name does not re solve for the supplied parameters. (errno2=0x112B) Unknown

Re: Receive Order Error

2006-10-27 Thread Brian Peterson
Simplify. Makes problem determination easier. What happened when you ran the PING test? Brian On Fri, 27 Oct 2006 10:44:44 -0500, Dick Renneke [EMAIL PROTECTED] wrote: We added the SYSTCPD DD statement to the SMPE job but got the same messages. SC0508 initConnection: Calling getaddrinfo()

Re: Receive Order Error

2006-10-27 Thread Dick Renneke
] .EDU Subject Re: Receive Order Error 10/27/2006 01:21

Re: Receive Order Error

2006-10-27 Thread Brian Peterson
OK - This result shows that the SYSTCPD DD statement is required for your RECEIVE job, and should fix your problem where RECEIVE is unable to resolve the inetsd01.boulder.ibm.com address - the unknown host error. So, if you add SYSTCPD to your RECEIVE job, you should expect to get some result

Re: Receive Order Error

2006-10-26 Thread Brian Peterson
Well, for dumbsorry about my previous reply. I ran debug=yes myself, and discovered that... CY1170 ftpStart: socket() failed on AF_INET6 - EDC8114I Address family not supported. (errno2=0x11B3005A) ...is a normal message. Your real error must have come later. From my debug=yes run,