Want to create a KSDS file using cobol program

ashish_setia · New User Joined: 19 Jan 2007 Posts: 3 Location: noida

Q- I want to create a KSDS file using cobol program , somewhat like this
Environment Division
Input-output section.
File-control
Select file1 assign to ddname.*
Access mode is random.
Organization is dynamic.
File status is fs1.

Corresponding JCL would be somewhat like this
//jobcard
//step1 exec pgm=idcam
//sysprint dd sysout=a
//sysin dd *
Define cluster(name (a.b.c?.
?..
/*
My question is what should I write in ddname ? in the statement select file1 assign to ddname*
Please help?

Warning: Title edited from cobol[/b]

muthuvel · Posted: Thu Jan 25, 2007 5:05 pm

Devzee · Posted: Sun Jan 28, 2007 12:04 pm

First create VSAM dataset
2nd In the program execution step just assign DD name which has the VSAM dataset

mmwife · Super Moderator Joined: 30 May 2003 Posts: 1592

Hi Ashish,

You wrote:

prav_06 · Posted: Mon Jan 29, 2007 2:52 pm

Hi All,
As per the requirement we can Create a VSAM file and access the same in a single step, there are parameters in JCL which would help us to create the vsam file like any other ordinary PS or PDS and uiset he same in the executing cobol program, please refer to special dd parameters like DATACLAS, RECORG. Using these parameters u can create a VSAM data set with out using the IDCAMS utility, I will try to post the JCL if possible.

Cheer's,

Thamilzan.

sumitchaturvedi_12 · New User Joined: 24 May 2005 Posts: 1 Location: bangalore

I have one VSAM file many records are there when I am moving the record structure of this file to a another group variable at the time of testing I want to see the value of the variables ,whether it has moved correctly or not. we can not use display and pick option. how would i do this?

Thanks & Regards
Sumit Chaturvedi

William Thompson · Posted: Mon Jan 29, 2007 3:21 pm

Devzee · Posted: Tue Jan 30, 2007 8:08 am

You can use expeditor and peek the variables.

dick scherrer · Posted: Tue Jan 30, 2007 8:43 am

Hello,

If you are not able to "display" the moved fields, you could write a new file with these fields as the record, then look at the file after the run completes. If they are not packed/binary fields, you could use SYSOUT for the file rather than a DSN. The test file would be removed after you are sure your moves work as needed.

If you don't want to add a file for this testing, you could do the move(s) in your code, force an abend (i.e. 0c7), then look in the dump for the moved data. I'd suggest putting an eye-cather before and after the fields you want to check.

Many sites do not allow "display" in production modules, but usually there is no problem having some display statements in a test program. Why can you not use display for your test?