Re: SMS and sysplex

2005-10-15 Thread R.S.

Matthew Stitt wrote:

BTDT.

When you switch from Monoplex to Multiplex, you need to add the system names
and/or the sysplex name to the CDS and activate the changes BEFORE you bring
the second and succeeding systems up.

If you do not do this, the only way to get the new systems recognize is to
allocate a new COMMDS, then switch to it.  And you still have to add the
system names in first.


Matthew,
I just did it. I added system names and allocated new COMMDS.
However new COMMDS resides on another, empty volume - so I thought, the 
problem was with serialization (RESERVE).

I have to try to move the COMMDS back to original volume.

To ohter gentlemen, who responded me: Yes, all my disk devices are 
SHARED in HCD.


Thank you.

--
Radoslaw Skorupka
Lodz, Poland

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


SMS and sysplex

2005-10-12 Thread R.S.

I'm getting the following messages:

IGD604I ACCESS FAILED FOR DATA SET SYS1.SMS.COMMDS. 179
DIV RETURN CODE 0008 REASON CODE 001C
IEF196I IEF237I 1044 ALLOCATED TO SYS2
IGD020I SMS IS NOW ACTIVE

06 IGD070D SMS COMMUNICATION ERROR, REPLY 'U' TO RETRY, 'C' TO CANCEL,
 'S' TO SUSPEND, 'T' TO TERMINATE

The problem occurs on second (and each next) member of sysplex.
I've checked the messages and DIV macro reason codes, but still don't 
understand what's wrong with my configuration.

According to DIV codes suggestions I replied T, but got the same error.
z/OS 1.4

Any clue ?

--
Radoslaw Skorupka
Lodz, Poland

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: SMS and sysplex

2005-10-12 Thread Gil Peleg
Any chance the COMMDS was allocated with wrong SHAREOPTIONS parameter?
IIRC, It should be SHAREOPTIONS(3,3).
 Gil.
 On 10/12/05, R.S. [EMAIL PROTECTED] wrote:

 I'm getting the following messages:

 IGD604I ACCESS FAILED FOR DATA SET SYS1.SMS.COMMDS. 179
 DIV RETURN CODE 0008 REASON CODE 001C
 IEF196I IEF237I 1044 ALLOCATED TO SYS2
 IGD020I SMS IS NOW ACTIVE

 06 IGD070D SMS COMMUNICATION ERROR, REPLY 'U' TO RETRY, 'C' TO CANCEL,
 'S' TO SUSPEND, 'T' TO TERMINATE

 The problem occurs on second (and each next) member of sysplex.
 I've checked the messages and DIV macro reason codes, but still don't
 understand what's wrong with my configuration.
 According to DIV codes suggestions I replied T, but got the same error.
 z/OS 1.4

 Any clue ?

 --
 Radoslaw Skorupka
 Lodz, Poland


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: SMS and sysplex

2005-10-12 Thread Ed Finnell
 
In a message dated 10/12/2005 8:28:28 A.M. Central Standard Time,  
[EMAIL PROTECTED] writes:

*When*  are you getting these messages? What else is going on at the  time?




Maybe it got Defraggedvbg? Guess the real question is what's  changed since 
the last IPL?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: SMS and sysplex

2005-10-12 Thread Richards.Bob
I was wondering if he lost access to the volume the COMMDS resides on. Your 
point about what changed is also very valid. 

Your DEFRAG comment was appropriate based on your other thread. Made me 
smile, at least. :)

Bob Richards
Technologist
Enterprise Technology Infrastructure
SunTrust Banks, Inc.
(404) 575-2798 

 -Original Message-
From:   IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]  On Behalf Of 
Ed Finnell
Sent:   Wednesday, October 12, 2005 9:31 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject:Re: SMS and sysplex

 
In a message dated 10/12/2005 8:28:28 A.M. Central Standard Time,  
[EMAIL PROTECTED] writes:

*When*  are you getting these messages? What else is going on at the  time?




Maybe it got Defraggedvbg? Guess the real question is what's  changed since 
the last IPL?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html 
  
  
  
LEGAL DISCLAIMER 
The information transmitted is intended solely for the individual or entity to 
which it is addressed and may contain confidential and/or privileged material. 
Any review, retransmission, dissemination or other use of or taking action in 
reliance upon this information by persons or entities other than the intended 
recipient is prohibited. If you have received this email in error please 
contact the sender and delete the material from any computer. 
  
Seeing Beyond Money is a service mark of SunTrust Banks, Inc. 
[ST:XCL] 
 
 
 
 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: SMS and sysplex

2005-10-12 Thread Ed Finnell
 
In a message dated 10/12/2005 8:36:45 A.M. Central Standard Time,  
[EMAIL PROTECTED] writes:

Your  DEFRAG comment was appropriate based on your other thread. Made me 
smile, at  least. :)




Mostly stuff I've done! It'd be tough to DEFRAG an inuse dataset under  
normal circumstances, that's why the what's changed? In the olden days used  to 
get 
lots of calls after failed DATASwitch attempts for one reason or the  other. 
Guess I'd start with hardware
and go thru CONFIG and oper commands.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: SMS and sysplex

2005-10-12 Thread Martin Kline
 IGD604I ACCESS FAILED FOR DATA SET SYS1.SMS.COMMDS.
 DIV RETURN CODE 0008 REASON CODE 001C

IBM's recomendation is to Determine the meaning of the data-in-virtual
return and reason codes.

HaHa.

In looking up the codes, the description says, Environment error. The
object cannot be accessed at this time. IBM's recommendation is to Retry
the request one or more times until the operation succeeds. That's all.

HaHaHa.

SO, does IBM expect the user to retry the request indefinitely? Shouldn't
the messages at least tell the user WHY the object is not available?


CONFIDENTIALITY NOTICE:  This electronic transmission (including any
accompanying attachments) is intended solely for its authorized
recipient(s), and may contain confidential and/or legally privileged
information.  If you are not an intended recipient, or responsible for
delivering some or all of this transmission to an intended recipient, be
aware that any review, copying, printing, distribution, use or disclosure of
the contents of this message is strictly prohibited.  If you have received
this electronic message in error, please contact us immediately by
electronic mail at [EMAIL PROTECTED] or notify us
immediately by telephone at 1-800-345-2021 or 816-531-5575 and destroy the
original and all copies of this transmission (including any attachments).
Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: SMS and sysplex

2005-10-12 Thread R.S.

Ed Finnell wrote:

 
In a message dated 10/12/2005 8:28:28 A.M. Central Standard Time,  
[EMAIL PROTECTED] writes:


*When*  are you getting these messages? What else is going on at the  time?




Maybe it got Defraggedvbg? Guess the real question is what's  changed since 
the last IPL?


NO, it is not defragged g BTW: SMS enqueues the dataset.
It is alocated with SHR(3 3).
NOTHING was changed since last IPL with one exception: it was monoplex 
configuration. Now, second (and third as well) member of sysplex was 
started. The problem occurs only on second and third sysplex member.


I just moved COMMDS to another volume, empty one. Problem disappeared.
As far as I understand, DIV has problems with serialization.
Still don't know what caused the problem. Placing every shared 
operational dataset on separate volume is not very wise circumvent.


--
Radoslaw Skorupka
Lodz, Poland

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: SMS and sysplex

2005-10-12 Thread Bruce Black

NO, it is not defragged g BTW: SMS enqueues the dataset.
It is alocated with SHR(3 3).
NOTHING was changed since last IPL with one exception: it was monoplex 
configuration. Now, second (and third as well) member of sysplex was 
started. The problem occurs only on second and third sysplex member. 



Is the disk it resides on defined as SHARED=YES in HCD?

--
Bruce A. Black
Senior Software Developer for FDR
Innovation Data Processing 973-890-7300
personal: [EMAIL PROTECTED]
sales info: [EMAIL PROTECTED]
tech support: [EMAIL PROTECTED]
web: www.innovationdp.fdr.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: SMS and sysplex

2005-10-12 Thread Randy Gross
Is it possible that the device is not genned (in HCD) as SHARED?

Randy

-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Behalf Of R.S.
Sent: Wednesday, October 12, 2005 10:02 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SMS and sysplex


Ed Finnell wrote:


 In a message dated 10/12/2005 8:28:28 A.M. Central Standard Time,
 [EMAIL PROTECTED] writes:

 *When*  are you getting these messages? What else is going on at the
time?




 Maybe it got Defraggedvbg? Guess the real question is what's  changed
since
 the last IPL?

NO, it is not defragged g BTW: SMS enqueues the dataset.
It is alocated with SHR(3 3).
NOTHING was changed since last IPL with one exception: it was monoplex
configuration. Now, second (and third as well) member of sysplex was
started. The problem occurs only on second and third sysplex member.

I just moved COMMDS to another volume, empty one. Problem disappeared.
As far as I understand, DIV has problems with serialization.
Still don't know what caused the problem. Placing every shared
operational dataset on separate volume is not very wise circumvent.

--
Radoslaw Skorupka
Lodz, Poland

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: SMS and sysplex

2005-10-12 Thread Vernooy, C.P. - SPLXM
Radoslaw,

a probably very obvious and totally superfluous question, but:
did you generate the shared devices in HCD as SHARED?

Kees.


R.S. [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]...
 Ed Finnell wrote:
 
   
  In a message dated 10/12/2005 8:28:28 A.M. Central Standard Time,  
  [EMAIL PROTECTED] writes:
  
  *When*  are you getting these messages? What else is going on at the  time?
  
  
  
  
  Maybe it got Defraggedvbg? Guess the real question is what's  changed 
  since 
  the last IPL?
 
 NO, it is not defragged g BTW: SMS enqueues the dataset.
 It is alocated with SHR(3 3).
 NOTHING was changed since last IPL with one exception: it was monoplex 
 configuration. Now, second (and third as well) member of sysplex was 
 started. The problem occurs only on second and third sysplex member.
 
 I just moved COMMDS to another volume, empty one. Problem disappeared.
 As far as I understand, DIV has problems with serialization.
 Still don't know what caused the problem. Placing every shared 
 operational dataset on separate volume is not very wise circumvent.
 
 -- 
 Radoslaw Skorupka
 Lodz, Poland
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
 Search the archives at http://bama.ua.edu/archives/ibm-main.html


**
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
**

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html


Re: SMS and sysplex

2005-10-12 Thread Matthew Stitt
BTDT.

When you switch from Monoplex to Multiplex, you need to add the system names
and/or the sysplex name to the CDS and activate the changes BEFORE you bring
the second and succeeding systems up.

If you do not do this, the only way to get the new systems recognize is to
allocate a new COMMDS, then switch to it.  And you still have to add the
system names in first.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html