Good catch Andy.
We went straight from 16 sp7 to 18 so we never fiddled with 17.
Charles (Chuck) Hardee
Senior Systems Engineer
Database Administration
Information Technology Services
Thermo Fisher Scientific
300 Industry Drive
Pittsburgh, PA 15275
Direct: 724-517-2633
FAX: 412-490-9230
Chuck.Hardee@ThermoFisher.com
From: CA IDMS (IUA EIUA) Global User Community [mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Thursday, May 09, 2013 10:33 AM
To:
mb.15281481.100988050@myca-email.ca.com
Subject: RE: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic allocation
Darn good find Andy, that appears it.
Operating System: OS
Solution No: 502
Confirmed Date: 12/01/2010
Updated Date: 02/14/2013
Component: CA IDMS/DB-IDMS
Release: 17.0
Fix: RO24483
Hyper: Yes
Distribution Code: AVAILABLE
Problem Description<https://support.ca.com/irj/portal/solncdndtls?aparno=RO24483&os=OS&docid=536934&actionID=5&fromKBResultsScreen=T#problemdescription>|
Solution Downloads <https://support.ca.com/irj/portal/solncdndtls?aparno=RO24483&os=OS&docid=536934&actionID=5&fromKBResultsScreen=T#solndownloads> |
Dependencies<https://support.ca.com/irj/portal/solncdndtls?aparno=RO24483&os=OS&docid=536934&actionID=5&fromKBResultsScreen=T#dependencies> |
Related Problems<https://support.ca.com/irj/portal/solncdndtls?aparno=RO24483&os=OS&docid=536934&actionID=5&fromKBResultsScreen=T#relatedproblems>
Problem Description
TITLE: Z/OS 1.12 DYNAMIC ALLOCATION CV FILES 3005 ERROR
***NOTE*** PE: YES CORRECTED BY: RO25822, RO33996
CA IDMS Central Version requests to open dynamically allocated CA
IDMS database files fail with OPEN error code 3005 on a z/OS 1.12
system. In addition, the use or non-use of Extended TIOT (XTIOT)
for dynamic allocation as specified in the NON_VSAM_XTIOT=YES/NO
statement in SYS1.PARMLIB(DEVSUPxx) has no effect on the dynamic
allocation of CA IDMS database files.
SYMPTOMS:
During CA IDMS Central Version startup, dynamically allocated
database files will not open and receive the following message:
IDMS DC200007 V5 T1 3005 Error Accessing Area - Not Available.
Also, database files allocated using JCL statements and then
de-allocated using a DCMT VARY FILE DEALLOCATE command will not
re-allocate dynamically using the DCMT VARY FILE ALLOCATE
command and fail with a 3005 error status.
IMPACT:
Any 17.0 CA IDMS Central Version using dynamic allocation of its
database files executing on a z/OS 1.12 system will receive 3005
OPEN errors for these files. These files will not be opened for
database access.
There is no impact for CA IDMS batch jobs using dynamic
allocation of database files executing on a z/OS 1.12 system.
The database files open normally and database access succeeds.
CIRCUMVENTION:
Provide JCL statements in the CA IDMS Central Version startup job
for all CA IDMS database files to prevent dynamic file allocation
from occurring. Do not re-allocate a database file using DCMT VARY
FILE ALLOCATE command which could result in dynamic file
allocation and 3005 open errors.
PRODUCTS AFFECTED:
CA IDMS Release 17.0
HYPER: YES PE: YES CORRECTED BY: RO25822, RO33996
DISTRIBUTION CODE: A
PROBLEM RESOLUTION: Apply the following PTF to the system.
Reload any resident modules, or re-IPL if necessary
From: CA IDMS (IUA EIUA) Global User Community [mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Thursday, May 09, 2013 10:19 AM
To:
mb.15281481.100987836@myca-email.ca.com
Subject: RE: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic allocation
RO24483 ?
Remember if you link your own startup module, other then IDMSDC, you will
need to relink.
Cheers, Andy
Andrew G. Daly
Senior GOS Systems DBA
Computer Sciences Corporation
GOS | 650.615.0707 (O) | 650.588.7994 (O2) | 650.740.7764 (C) |
adaly@csc.com<mailto:
adaly@csc.com>
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit
written agreement or government initiative expressly permitting the use of
e-mail for such purpose.
From: "CA IDMS (IUA EIUA) Global User Community"
<
CommunityAdmin@communities-mail.ca.com<mailto:
CommunityAdmin@communities-mail.ca.com>>
To: "
mb.15281481.100987442@myca-email.ca.com<mailto:
mb.15281481.100987442@myca-email.ca.com>"
<
mb.15281481.100987442@myca-email.ca.com<mailto:
mb.15281481.100987442@myca-email.ca.com>>
Date: 05/09/13 05:54 AM
Subject: RE: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic
allocation
Be aware I have only been here 37 days and prior support was not present
when I arrived.
I was surprised this feature was not in use, maybe I am learning why.
The other DSNs getting 3005 do not have JCL DD present, when I add the
DD?s the 3005 goes away.
Nothing is syslog. Also security confirms nothing inhibiting dynamic
allocation in STC profile.
N 0000000 SYSR 13129 07:40:47.05 STC04842 00000010 +IDMS DC200023 V50 T1
CV Change Tracking is not used
N 0000000 SYSR 13129 07:40:47.07 STC04842 00000010 +IDMS DC200185 V50 T1
All transactions recovered
N 0000000 SYSR 13129 07:40:47.10 STC04842 00000010 +IDMS DC200007 V50 T1
3005 Error Accessing Area - Not Available.
S EMPDEMO.ORG-DEMO-REGION
W 0000000 SYSR 13129 07:40:47.13 STC04842 00000010 @224 REPLY WITH REQUEST
TO IDMS V50
N 0000000 SYSR 13129 07:40:47.13 STC04230 00000210 SYSRS AUTLOG - CNM493I
INGMSG01 : 01880001 : OUTREP
N 0000000 SYSR 13129 07:40:47.13 STC04842 00000010 +IDMS DC201001 V50 T1
CA IDMS/DB: 50 Started
N 0000000 SYSR 13129 07:40:49.26 STC04842 00000010 +IDMS DC329012 V50 T1
Startup resynchronization initiated
N 0000000 SYSR 13129 07:40:49.27 STC04842 00000010 +IDMS DC200009 V50 T1
CA IDMS/DB Active 07:40:49 13.129
N 0000000 SYSR 13129 07:40:49.28 STC04842 00000010 +IDMS DC013003 V50 T0
OPENING SYSTEM RUN UNITS
Going back to EMPDEMO, in which DCMT DIS AREA nn FULL output is listed.
This supports:
1. EMPDEMO.EMPDEMO is present
2. DSNAME matches DMCL and JCL
This is the DD
//EMPDEMO DD DISP=SHR,DSN=SYS5.IDMS.TEST.EMPDEMO.EMPDEMO
With DD present I see:
, DIS AREA EMPDEMO.EMP-DEMO-REGION FULL
---------- Area ----------- Lock Lo-Page Hi-Page #Ret #Upd #Tret #Ntfy
EMPDEMO.EMP-DEMO-REGION Upd 77501 77550 0 0 0 0
Stamp: 2013-05-08-14.12.41.768126 Pg grp: 0 NoShare NoICVI NoPerm
-------- Data File -------- Mode Stat Pg-Size Fl-Type M-Cache S-Cache
DD-Name
EMPDEMO.EMPDEMO Upd 0 4276 non-VSAM No No EMPDEMO
Pre-fetch: Disabled (Buffer Cnt) Pages per Track 11 VOLSER: TLR301
DSname: (DMCL).. SYS5.IDMS.TEST.EMPDEMO.EMPDEMO DISP=SHR
DSname: (JCL)... SYS5.IDMS.TEST.EMPDEMO.EMPDEMO DISP=SHR
V50 ENTER NEXT TASK CODE: CA IDMS release 17.0 tape GJH01B node SYST0050
,
With DD commented I get
07.45.07 STC04844 +IDMS DC200185 V50 T1 All transactions recovered
07.45.07 STC04844 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. EMPDEMO.EMP-DEMO-REGION
07.45.07 STC04844 @226 REPLY WITH REQUEST TO IDMS V50
and I see
, DIS AREA EMPDEMO.EMP-DEMO-REGION FULL
---------- Area ----------- Lock Lo-Page Hi-Page #Ret #Upd #Tret #Ntfy
EMPDEMO.EMP-DEMO-REGION N/av 77501 77550 0 0 0 0
Stamp: 2013-05-08-14.12.41.768126 Pg grp: 0 NoShare NoICVI NoPerm
Stat: 3005 Pnd Lock:
-------- Data File -------- Mode Stat Pg-Size Fl-Type M-Cache S-Cache
DD-Name
EMPDEMO.EMPDEMO Err 3005 4276 non-VSAM No No EMPDEMO
Pre-fetch: Disabled (Buffer Cnt) UNALLOCATED
DSname: (DMCL).. SYS5.IDMS.TEST.EMPDEMO.EMPDEMO DISP=SHR
V50 ENTER NEXT TASK CODE: CA IDMS release 17.0 tape GJH01B node SYST0050
I these exits
X17STUB
X18STUB
USGX333E
I see these optional apars, with 12 & 318 I need to understand why
present, but appear not related to allocation.
OPTIONAL APARS
OPT00012 OPT00025 OPT00038 OPT00052 OPT00058 OPT00061 OPT00081 OPT00140
OPT00168 OPT00172 OPT00176 OPT00193 OPT00203 OPT00204 OPT00206 OPT00209
OPT00219 OPT00227 OPT00241 OPT00270 OPT00309 OPT00318
I will perform Chuck?s exercise shortly.
Rob
From: CA IDMS (IUA EIUA) Global User Community [
mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Wednesday, May 08, 2013 5:02 PM
To:
mb.15281481.100983690@myca-email.ca.com<mailto:
mb.15281481.100983690@myca-email.ca.com>
Subject: RE: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic allocation
Interesting, not at all what I was hoping to see or hear.
So, with the DDs present in the first startup you are getting 3005s on
other areas as well?
Do these areas have DDs in the JCL or are they relying on dynamic
allocation?
And the unlock says that the area wasn?t locked during the
shutdown/restart so that tells me that CV is closing the files properly.
But, and here?s why it?s perplexing, when you started with no DD and got
the 3005, then you shut down and restarted with no JCL changes (IE the DD
was still commented out), you didn?t get the 3005. If dynamic allocation
wasn?t working correctly then the last restart should have received the
3005 just like the startup prior. And since CV doesn?t appear to be
leaving the file locked across shutdowns it sound as if RHDCOMOC is
handling the open/close process correctly.
I?m about out of here for the day, but I?ll keep thinking about it and
when I get home I?ll check and see if you?ve made any progress or if
someone else has any ideas.
Right now, based on everything you?ve supplied, you should be good to go.
Something you could try is adding another page group with the EMPDEMO
database and in the DMCL do an override for start usage being retrieval as
opposed to update.
Give it new DDs and use the same DSNs. Alternatively, you could clone the
Datasets (while CV is down) and use the new DSNs in the new segment. Be
sure to specify a new page group.
Then cycle CV and see if the new segment?s files get 3005 errors.
Charles (Chuck) Hardee
Senior Systems Engineer
Database Administration
Information Technology Services
Thermo Fisher Scientific
300 Industry Drive
Pittsburgh, PA 15275
Direct: 724-517-2633
FAX: 412-490-9230
Chuck.Hardee@ThermoFisher.com<mailto:
Chuck.Hardee@ThermoFisher.com<mailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com>>
From: CA IDMS (IUA EIUA) Global User Community [
mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Wednesday, May 08, 2013 4:46 PM
To:
mb.15281481.100984001@myca-email.ca.com<<mailto:
mb.15281481.100984001@myca-email.ca.com%3c>
mailto:
mb.15281481.100984001@myca-email.ca.com>
Subject: RE: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic allocation
0) PRE TEST STATUS JCL DD PRESENT
15.35.36,STC04793, +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. DBX.USV-DATA-AREA
15.35.36 STC04793 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. DMA.XDM-DATA-AREA
15.35.36 STC04793 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. DMLO.USD-DATA-AREA
15.35.36 STC04793 @208 REPLY WITH REQUEST TO IDMS V50
1) Comment out the DD and cycle CV.
2) 3005 hits
3) 16.34.15 STC04797 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. DBX.USV-DATA-AREA
4) 16.34.15 STC04797 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. DMA.XDM-DATA-AREA
5) 16.34.15 STC04797 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. DMLO.USD-DATA-AREA
6) 16.34.15 STC04797 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. EMPDEMO.ORG-DEMO-REGION
7) 16.34.15 STC04797 @210 REPLY WITH REQUEST TO IDMS V50
2) If the restart gets the 3005 error, shutdown CV.
CV shutdown
3&4) Unlock the area,
DB002367 C1M353: Area EMPDEMO.ORG-DEMO-REGION was not locked.
5 &6) Start CV, leave the DD commented out.
16.38.54,STC04800, +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. DBX.USV-DATA-AREA
16.38.54 STC04800 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. DMA.XDM-DATA-AREA
16.38.54 STC04800 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. DMLO.USD-DATA-AREA
16.38.54 STC04800 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. EMPDEMO.ORG-DEMO-REGION
16.38.54 STC04800 @212 REPLY WITH REQUEST TO IDMS V50
7) shutdown CV and add DD back (3005 did not occur)
16.42.57,STC04802, +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. DBX.USV-DATA-AREA
16.42.57 STC04802 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. DMA.XDM-DATA-AREA
16.42.57 STC04802 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. DMLO.USD-DATA-AREA
16.42.57 STC04802 @214 REPLY WITH REQUEST TO IDMS V50
This shows UNLOCK was not needed.
From: CA IDMS (IUA EIUA) Global User Community [
mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Wednesday, May 08, 2013 4:26 PM
To:
mb.15281481.100983778@myca-email.ca.com<<mailto:
mb.15281481.100983778@myca-email.ca.com%3c>
mailto:
mb.15281481.100983778@myca-email.ca.com>
Subject: RE: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic allocation
Okay, let?s try something.
1) Comment out the DD and cycle CV.
2) If the restart gets the 3005 error, shutdown CV.
3) Unlock the area
4) Examine the output of the unlock and make sure the area WAS locked.
5) Start CV, leave the DD commented out.
6) Report if the CV complains about the area again with a 3005.
The idea here is to make sure that something else isn?t happening between
the first cycle with the DD commented out and the startup.
If CV, with the DD present, has the area in UPDATE mode and you shut down
CV, the area SHOULD be unlocked.
If something is happening between the subsequent startup, or if CV isn?t
unlocking the area on shutdown, then we have a different problem.
The second startup, with nothing being executed between the shutdown and
the startup, should tell us something.
C-
Charles (Chuck) Hardee
Senior Systems Engineer
Database Administration
Information Technology Services
Thermo Fisher Scientific
300 Industry Drive
Pittsburgh, PA 15275
Direct: 724-517-2633
FAX: 412-490-9230
Chuck.Hardee@ThermoFisher.com<mailto:
Chuck.Hardee@ThermoFisher.com<<mailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3c>
mailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com
>>
From: CA IDMS (IUA EIUA) Global User Community [
mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Wednesday, May 08, 2013 4:11 PM
To:
mb.15281481.100983503@myca-email.ca.com<<mailto:
mb.15281481.100983503@myca-email.ca.com%3c>
mailto:
mb.15281481.100983503@myca-email.ca.com<<mailto:
mb.15281481.100983503@myca-email.ca.com%3c>
mailto:
mb.15281481.100983503@myca-email.ca.com%3cmailto:
mb.15281481.100983503@myca-email.ca.com
>>
Subject: RE: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic allocation
I am very open to something missing
17.0 tape GJH01B
I mention defect because IDMS 17 fix 3005 ERROR ACCESSING VSAM BASED AREA
USING ZIIP,OS,IDMS,RO15224<
https://support.ca.com/irj/portal/solndtls?docid=507904&searchID=507904&aparno=RO15224&product=IDMS&os=OS&release=17.0&number=0000292&type=&actionID=5&pos=N/A
>
However VSAM not involved here.
To review using this FILE entry
CREATE
FILE EMPDEMO.ORGDEMO
*+ CREATED 2013-05-08-14.12.41.767764 BY UKLANRX
*+ LAST CRITICAL CHANGE 2013-05-08-14.12.41.771353
ASSIGN TO ORGDEMO
DSNAME 'SYS5.IDMS.TEST.EMPDEMO.ORGDEMO'
DISP SHR
NONVSAM
*+ FILE BLOCK SIZE 4276 CHARACTERS
*+ BLOCKS 1 THRU 25 MAP TO AREA ORG-DEMO-REGION PAGES 77751 THRU 77775
;
RUN A.
LOOK DMCL with DD present
EMPDEMO.ORGDEMO ORGDEMO BDAM No No DEFAULT_BUFFER
DSname: (DMCL) SYS5.IDMS.TEST.EMPDEMO.ORGDEMO
DSname: (JCL) SYS5.IDMS.TEST.EMPDEMO.ORGDEMO
RUN B.
So now I comment out JCL DD and cycle.
IDMS issues
IDMS DC200007 V50 T1 3005 Error Accessing Area - Not Available.
EMPDEMO.EMP-DEMO-REGION
LOOK DMCL with DD commented out
EMPDEMO.ORGDEMO ORGDEMO BDAM No No DEFAULT_BUFFER
DSname: (DMCL) SYS5.IDMS.TEST.EMPDEMO.ORGDEMO
It is here I must run an unlock to eliminate DC20007 with RUN C start up
RUN C.
I add DD statement back to JCL
LOOK DMCL with DD present
EMPDEMO.ORGDEMO ORGDEMO BDAM No No DEFAULT_BUFFER
DSname: (DMCL) SYS5.IDMS.TEST.EMPDEMO.ORGDEMO
DSname: (JCL) SYS5.IDMS.TEST.EMPDEMO.ORGDEMO
From: CA IDMS (IUA EIUA) Global User Community [
mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Wednesday, May 08, 2013 3:49 PM
To:
mb.15281481.100983223@myca-email.ca.com<<mailto:
mb.15281481.100983223@myca-email.ca.com%3c>
mailto:
mb.15281481.100983223@myca-email.ca.com<<mailto:
mb.15281481.100983223@myca-email.ca.com%3c>
mailto:
mb.15281481.100983223@myca-email.ca.com%3cmailto:
mb.15281481.100983223@myca-email.ca.com
>>
Subject: RE: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic allocation
Whoa, slow down there!
We run numerous CVs here with absolutely NO DDs in the JCL.
Our batch jobs run with NO DDs in their JCL streams.
There?s something missing here if you can unlock and execute, unless I?ve
misunderstood what you are saying.
First off, what release of IDMS are you working with?
I ask because the dynamic allocation capability of IDMS has been around
for a very long time and I find it hard to believe you have stumbled upon
a new problem.
That?s not to say that you haven?t, I just suspect that it isn?t a new
problem.
So, take a step back, what release and service pack if applicable?
Charles (Chuck) Hardee
Senior Systems Engineer
Database Administration
Information Technology Services
Thermo Fisher Scientific
300 Industry Drive
Pittsburgh, PA 15275
Direct: 724-517-2633
FAX: 412-490-9230
Chuck.Hardee@ThermoFisher.com<mailto:
Chuck.Hardee@ThermoFisher.com<<mailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3c>
mailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com
<
mailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com
>>>
From: CA IDMS (IUA EIUA) Global User Community [
mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Wednesday, May 08, 2013 3:42 PM
To:
mb.15281481.100963013@myca-email.ca.com<<mailto:
mb.15281481.100963013@myca-email.ca.com%3c>
mailto:
mb.15281481.100963013@myca-email.ca.com<<mailto:
mb.15281481.100963013@myca-email.ca.com%3c>
mailto:
mb.15281481.100963013@myca-email.ca.com%3cmailto:
mb.15281481.100963013@myca-email.ca.com
<
mailto:
mb.15281481.100963013@myca-email.ca.com%3cmailto:
mb.15281481.100963013@myca-email.ca.com%3cmailto:
mb.15281481.100963013@myca-email.ca.com%3cmailto:
mb.15281481.100963013@myca-email.ca.com
>>>
Subject: RE: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic allocation
That was a good thought Chuck, however doesn?t appear to be that
LOOK DMCL with DD commented out
EMPDEMO.ORGDEMO ORGDEMO BDAM No No DEFAULT_BUFFER
DSname: (DMCL) SYS5.IDMS.TEST.EMPDEMO.ORGDEMO
LOOK DMCL with DD present
EMPDEMO.ORGDEMO ORGDEMO BDAM No No DEFAULT_BUFFER
DSname: (DMCL) SYS5.IDMS.TEST.EMPDEMO.ORGDEMO
DSname: (JCL) SYS5.IDMS.TEST.EMPDEMO.ORGDEMO
This is starting to look like an IDMS defect as I must run an unlock to
get back to ?DD present? with data file in UPD mode.
From: CA IDMS (IUA EIUA) Global User Community [
mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Wednesday, May 08, 2013 3:29 PM
To:
mb.15281481.100982724@myca-email.ca.com<<mailto:
mb.15281481.100982724@myca-email.ca.com%3c>
mailto:
mb.15281481.100982724@myca-email.ca.com<<mailto:
mb.15281481.100982724@myca-email.ca.com%3c>
mailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com
<
mailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com
>>>
Subject: RE: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic allocation
Execute IDMSLOOK with the DMCL parameter and examine what the DMCL says is
associated with the file and area.
It?s possible that while the file has all the correct definitions in the
catalog, the DMCL does not.
If, for instance, someone had started the process of using dynamic
allocation but had not yet completed it and generated the DMCL, then the
DMCL would not yet know the file name to which to issue the correct
allocation.
Charles (Chuck) Hardee
Senior Systems Engineer
Database Administration
Information Technology Services
Thermo Fisher Scientific
300 Industry Drive
Pittsburgh, PA 15275
Direct: 724-517-2633
FAX: 412-490-9230
Chuck.Hardee@ThermoFisher.com<mailto:
Chuck.Hardee@ThermoFisher.com<<mailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3c>
mailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com
<
mailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com
<
mailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com%3cmailto:
Chuck.Hardee@ThermoFisher.com
>>>>
From: CA IDMS (IUA EIUA) Global User Community [
mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Wednesday, May 08, 2013 3:16 PM
To:
mb.15281481.100982689@myca-email.ca.com<<mailto:
mb.15281481.100982689@myca-email.ca.com%3c>
mailto:
mb.15281481.100982689@myca-email.ca.com<<mailto:
mb.15281481.100982689@myca-email.ca.com%3c>
mailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com
<
mailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com
<
mailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com
>>>>
Subject: RE: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic allocation
Hi Dick
Below is why I looked at removing ASSIGN TO, which is from ADMIN manual.
ASSIGN TO
Specifies an external file name. Every external file name in a DMCL
definition must be unique. If you do not specify an ASSIGN TO clause, you
must do one of two things:
? Specify the external file name in a file override clause in every DMCL
in which the segment is included
? Specify DSNAME or VM VIRTUAL ADDRESS parameter
Now in comparing your set up to one I have, we look alike.
CREATE
FILE EMPDEMO.ORGDEMO
*+ CREATED 2013-05-08-14.12.41.767764 BY UKLANRX
*+ LAST CRITICAL CHANGE 2013-05-08-14.12.41.771353
ASSIGN TO ORGDEMO
DSNAME 'SYS5.IDMS.TEST.EMPDEMO.ORGDEMO'
DISP SHR
NONVSAM
*+ FILE BLOCK SIZE 4276 CHARACTERS
*+ BLOCKS 1 THRU 25 MAP TO AREA ORG-DEMO-REGION PAGES 77751 THRU 77775
;
So based on above I should be able to comment out the below statement
//ORGDEMO DD DISP=SHR,DSN=SYS5.IDMS.TEST.EMPDEMO.ORGDEMO
Would you concur?
Sadly when I do comment and I cycle IDMS I get the below
15.09.26 STC04790 +IDMS DC200007 V50 T1 3005 Error Accessing Area - Not
Available. EMPDEMO.ORG-DEMO-REGION
I also tried with startup with PARM='MT=N,ZIIP=N' for grins and giggles
thinking it was related to 3005 ERROR ACCESSING VSAM BASED AREA USING
ZIIP,OS,IDMS,RO15224<
https://support.ca.com/irj/portal/solndtls?docid=507904&searchID=507904&aparno=RO15224&product=IDMS&os=OS&release=17.0&number=0000292&type=&actionID=5&pos=N/A
>
Rob
From: CA IDMS (IUA EIUA) Global User Community [
mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Wednesday, May 08, 2013 2:52 PM
To:
mb.15281481.100982613@myca-email.ca.com<<mailto:
mb.15281481.100982613@myca-email.ca.com%3c>
mailto:
mb.15281481.100982613@myca-email.ca.com<<mailto:
mb.15281481.100982613@myca-email.ca.com%3c>
mailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com
<
mailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com
<
mailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com
>>>>
Subject: RE: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic allocation
We haven?t used JCL DD statements for over 20 years.
Below is an example of one of our files, and the startup JCL has no DDs
for database files. Note that a JCL DD will override the default in the
DMCL. And the DD NAME is required for the override.
CREATE
FILE MMVSSEGM.MMVF-MMVN101A
*+ CREATED 1996-06-27-10.26.09.021714 BY DBAJDLB
*+ LAST UPDATED 1997-09-05-09.10.20.155474 BY DBAJDGB
*+ LAST CRITICAL CHANGE 1997-09-05-09.10.20.155474
ASSIGN TO MMVN101A
DSNAME 'PSAMV.CV11.MMVN101A'
DISP SHR
NONVSAM
*+ FILE BLOCK SIZE 6516 CHARACTERS
*+ BLOCKS 1 THRU 25000 MAP TO AREA MMVA-ACCD PAGES 1000001 THRU 1025000
*+ OVERRIDES FOR DMCL GLBLDMCL
*+ BUFFER MMVB-06516-A
*+ SHARED CACHE DEFAULT
*+ MEMORY CACHE NO
*+ OVERRIDES FOR DMCL TAPEDMCL
*+ BUFFER MMVB-DAT-6516-A
*+ SHARED CACHE DEFAULT
*+ MEMORY CACHE NO
;
Dick
Richard Pierce
richard.pierce@state.ma.us<mailto:
richard.pierce@state.ma.us<<mailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3c>
mailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us<<mailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3c>
mailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us
<
mailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us
<
mailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us
<
mailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:richard.pi!
erce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us<mailto:
erce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us%3cmailto:
richard.pierce@state.ma.us>
>>>>>>
Office (new) (857) 368-9898 Cell: (781) 983-0363
www.mass.gov/massdot<http://www.mass.gov/massdot<<http://www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3c>
http://www.mass.gov/massdot%3chttp:/www.mass.gov/massdot<<http://www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3c>
http://www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot
<
http://www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot
<
http://www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot
<
http://www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot%3chttp:/www.mass.gov/massdot
>>>>>>
From: CA IDMS (IUA EIUA) Global User Community [
mailto:
CommunityAdmin@communities-mail.ca.com]
Sent: Wednesday, May 08, 2013 2:46 PM
To:
mb.15281481.100982603@myca-email.ca.com<<mailto:
mb.15281481.100982603@myca-email.ca.com%3c>
mailto:
mb.15281481.100982603@myca-email.ca.com<<mailto:
mb.15281481.100982603@myca-email.ca.com%3c>
mailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com
<
mailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com
<
mailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com
<
mailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com
>>>>>
Subject: [DBA Issues - Open Forum] JCL DD vs IDMS dynamic allocation
Hi
JCL DD vs IDMS dynamic dsname allocation.
We have DSNAME in FILE statement. We also have JCL DD statements. hence
MVS allocate rather than IDMS allocate.
I wish to eliminate JCL DDs. Nicely FILE statement DSNAME is 100% match to
JCL DD dsname.
I believe I only need to remove the ASSIGN TO parm from the FILE statement
and create DMCL and comment out DD statement.
However that does not work and results in
+IDMS DC200007 V50 T1 3005 Error Accessing Area - Not Available.
EMPDEMO.EMP-DEMO-REGION
Admin manual supports my believe. Obviously I am missing a piece of the
pie.
Any ideas?
Rob
Posted by:rob.klan.1
--
CA Communities Message Boards
100985143
mb.15281481.100982603@myca-email.ca.com<<mailto:
mb.15281481.100982603@myca-email.ca.com%3c>
mailto:
mb.15281481.100982603@myca-email.ca.com<<mailto:
mb.15281481.100982603@myca-email.ca.com%3c>
mailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com
<
mailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com
<
mailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com
<
mailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com
<
mailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:mb!
.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com<mailto:
.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com%3cmailto:
mb.15281481.100982603@myca-email.ca.com>
>>>>>>
https://communities.ca.com
Posted by:richard.pierce1.1
--
CA Communities Message Boards
100985153
mb.15281481.100982613@myca-email.ca.com<<mailto:
mb.15281481.100982613@myca-email.ca.com%3c>
mailto:
mb.15281481.100982613@myca-email.ca.com<<mailto:
mb.15281481.100982613@myca-email.ca.com%3c>
mailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com
<
mailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com
<
mailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com
<
mailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com%3cmailto:
mb.15281481.100982613@myca-email.ca.com
>>>>>
https://communities.ca.com
Posted by:rob.klan.1
--
CA Communities Message Boards
100985229
mb.15281481.100982689@myca-email.ca.com<<mailto:
mb.15281481.100982689@myca-email.ca.com%3c>
mailto:
mb.15281481.100982689@myca-email.ca.com<<mailto:
mb.15281481.100982689@myca-email.ca.com%3c>
mailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com
<
mailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com
<
mailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com%3cmailto:
mb.15281481.100982689@myca-email.ca.com
>>>>
https://communities.ca.com
Posted by:chuckhardee
--
CA Communities Message Boards
100985264
mb.15281481.100982724@myca-email.ca.com<<mailto:
mb.15281481.100982724@myca-email.ca.com%3c>
mailto:
mb.15281481.100982724@myca-email.ca.com<<mailto:
mb.15281481.100982724@myca-email.ca.com%3c>
mailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com
<
mailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com
<
mailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com%3cmailto:
mb.15281481.100982724@myca-email.ca.com
>>>>
https://communities.ca.com
Posted by:rob.klan.1
--
CA Communities Message Boards
100965553
mb.15281481.100963013@myca-email.ca.com<<mailto:
mb.15281481.100963013@myca-email.ca.com%3c>
mailto:
mb.15281481.100963013@myca-email.ca.com<<mailto:
mb.15281481.100963013@myca-email.ca.com%3c>
mailto:
mb.15281481.100963013@myca-email.ca.com%3cmailto:
mb.15281481.100963013@myca-email.ca.com
<
mailto:
mb.15281481.100963013@myca-email.ca.com%3cmailto:
mb.15281481.100963013@myca-email.ca.com%3cmailto:
mb.15281481.100963013@myca-email.ca.com%3cmailto:
mb.15281481.100963013@myca-email.ca.com
>>>
https://communities.ca.com
Posted by:chuckhardee
--
CA Communities Message Boards
100985763
mb.15281481.100983223@myca-email.ca.com<<mailto:
mb.15281481.100983223@myca-email.ca.com%3c>
mailto:
mb.15281481.100983223@myca-email.ca.com<<mailto:
mb.15281481.100983223@myca-email.ca.com%3c>
mailto:
mb.15281481.100983223@myca-email.ca.com%3cmailto:
mb.15281481.100983223@myca-email.ca.com
<
mailto:
mb.15281481.100983223@myca-email.ca.com%3cmailto:
mb.15281481.100983223@myca-email.ca.com%3cmailto:
mb.15281481.100983223@myca-email.ca.com%3cmailto:
mb.15281481.100983223@myca-email.ca.com
>>>
https://communities.ca.com
Posted by:rob.klan.1
--
CA Communities Message Boards
100986043
mb.15281481.100983503@myca-email.ca.com<<mailto:
mb.15281481.100983503@myca-email.ca.com%3c>
mailto:
mb.15281481.100983503@myca-email.ca.com<<mailto:
mb.15281481.100983503@myca-email.ca.com%3c>
mailto:
mb.15281481.100983503@myca-email.ca.com%3cmailto:
mb.15281481.100983503@myca-email.ca.com
>>
https://communities.ca.com
Posted by:chuckhardee
--
CA Communities Message Boards
100986318
mb.15281481.100983778@myca-email.ca.com<<mailto:
mb.15281481.100983778@myca-email.ca.com%3c>
mailto:
mb.15281481.100983778@myca-email.ca.com<<mailto:
mb.15281481.100983778@myca-email.ca.com%3c>
mailto:
mb.15281481.100983778@myca-email.ca.com%3cmailto:
mb.15281481.100983778@myca-email.ca.com
>>
https://communities.ca.com
Posted by:rob.klan.1
--
CA Communities Message Boards
100986541
mb.15281481.100984001@myca-email.ca.com<<mailto:
mb.15281481.100984001@myca-email.ca.com%3c>
mailto:
mb.15281481.100984001@myca-email.ca.com>
https://communities.ca.com
Posted by:chuckhardee
--
CA Communities Message Boards
100986230
mb.15281481.100983690@myca-email.ca.com<<mailto:
mb.15281481.100983690@myca-email.ca.com%3c>
mailto:
mb.15281481.100983690@myca-email.ca.com>
https://communities.ca.com
Posted by:rob.klan.1
--
CA Communities Message Boards
100989982
mb.15281481.100987442@myca-email.ca.com<mailto:
mb.15281481.100987442@myca-email.ca.com>
https://communities.ca.com
Posted by:adaly
--
CA Communities Message Boards
100990376
mb.15281481.100987836@myca-email.ca.com<mailto:
mb.15281481.100987836@myca-email.ca.com>
https://communities.ca.com
Posted by:rob.klan.1
--
CA Communities Message Boards
100990590
mb.15281481.100988050@myca-email.ca.com
https://communities.ca.com