I'm not familiar with any of the current customer base running this with TeraSAM. Do you have a link to provide some more info?

Are you getting a particular error w/ SDF? It's a pretty basic program, we're only associating data sets via records in the logical cluster.

Ex: You define the 1 track VSAM d/s. Then you define the 5, or however many segment (VSAM) data sets, suffixed with ".SEG001, .SEG002, ETC."

You run SDF -

If you now run an IDCAMS PRINT of the 1 track cluster with the dd card
//TS$OFF DD DUMMY, you should have about 120-240 records, and you should see the segment data set names in the listing.

You can't stump us James... You just can't

A few more pieces of info though - what's your z/OS level, version of TeraSAM, and last maint. applied?

let us know...

Dave Yates
EMC TSE3
Benevolent Host S/W & Mainframe Forum Moderator
"Il Moderatore Benevolo"

Ok, how do I attach output? I have the output you requested. I the output is of the base VSAM cluster, that is formatted for VSDM.

It looks like the VSDM process is over-writting the TS$SEGDF stuff. I want to send you the output from the IDCAMS/PRINT. I am going to lunch now, when I get back, I will bring up my Mainframe session as a MOD-5, so I can see all of the output, then screen scrape it to the message posting area.

attachments are tightly regulated. copy / paste it into the forums window.

Once you run TS$SDF, can you load the TeraSAM data set? If you have STATS on, you should see in the SYSMSGS what records were written & to which segments.

Dave, I can not get my terminal into MOD-5 mode, so I guess I can not send you the output that I want you to see. So, what is next?

Well, well, well James...

You just might have a vendor conflict here from what you explained on the phone. Let us know what data you get from the --OTHER-- vendor.

As I mentioned previously, you can use this knowledgebase entry - http://csgateway.emc.com/primus.asp?id=emc202064

along with output of:
IDCAMS DEFINE of logical cluster & segments
TS$SEGDF w/ //CLUSTER DD DSN=tsm.logical.cluster
IDCAMS PRINT of tsm.logical.cluster with //TS$OFF DD DUMMY.

That output will show the records TSM is using to direct I/O to the segments.

something like:
IDCAMS Print should look something like this:
KEY OF RECORD - 0007FFFFFF
000000 0007FFFF FFE2C3E3 E20A71D0 00400000 00E3C5E2 E3E3F14B E3E25BD1 D7D4C34B *.....SCTS..}. ...TESTT1.TS$JPMC.*
000020 D3C3F2F0 F4F84BE2 C5C7F0F1 40404040 40404040 40404040 40404040 40000000 *LC2048.SEG01 ...*
000040 00000000 000000A8 00000000 00000000 00000000 00000000 00000000 00000000 *................................*
000060 01000000 *.... *

IDCAMS SYSTEM SERVICES TIME: 12:13:08 10/29/08 PAGE 3
LISTING OF DATA SET -TESTT1.TS$JPMC.LC2048
KEY OF RECORD - 0008FFFFFF
000000 0008FFFF FF3215FF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF *................................*
000020 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF *................................*
000040 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF *................................*
000060 FFFFFFFF *.... *


Let us know what you find JB

Dave Yates
EMC TSE3
Benevolent Host S/W & Mainframe Forum Moderator
"Il Moderatore Benevolo"