Unsolved
This post is more than 5 years old
15 Posts
0
743
TERASAM and SIEMENS SMS software
Currently we are running V D26 of the SIEMENS hospital software INVISION and SIGNATURE. These folks have an access method on top of VSAM, that may be getting in the way of the TS$SEGDF utility. Is anyone running any of this software? We may have an issue with VSDM and TS$SEGDF. Thank you.
Davidy8s
154 Posts
0
October 16th, 2009 07:00
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"
jrtumb
15 Posts
0
October 16th, 2009 09:00
jrtumb
15 Posts
0
October 16th, 2009 09:00
Davidy8s
154 Posts
0
October 16th, 2009 09:00
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.
jrtumb
15 Posts
0
October 16th, 2009 11:00
Davidy8s
154 Posts
0
October 20th, 2009 13:00
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"