Great video, as always. I had been struggling since last night trying to figure out the requisite parameters to Define Cluster. The ones you use finally gave me CC=0. Going now straight to other VSAM videos you've uploaded. Thanks so much.
I really appreciate that you've put together these videos! I am learning a lot. Your examples here demonstrate creating VSAM clusters outside of a user catalog (so I've learned). I believe that means the data sets are cataloged in the master catalog as a result. It would be cool to see you do a video on managing VSAM data sets that have been suballocated inside a user catalog. Also, the 'unique' parameter doesn't specify that the keys must be unique. That parameter is what you have to provide if you want IDCAMS to create a VSAM cluster separately from a user catalog. I think if you had just re-run your REPRO job a 2nd time without altering it, you would have gotten the key collision errors. I assume VSAM requires that keys be unique. At least, I have yet to find the documentation on how to say unique/not unique keys.
The Key in the Primary Index is ALWAYS unique. No need to specify. Also, you mention two keys when looking at the inputdata. What you probably mean is that the second 'keyfield' could be used as the key for an Alternate Index, AIX, which is another story. Lastly, the problem you run into, after changing the inputfile key Value, is beacuse the VSAM Cluster was already filled with records. Thats why you got error-message for ALL KEYS, and has nothing to do with 'VSAM transactions'. You need to Delete and Repro again to have the result you were expected with the only duplicate key.
Thank you for your VSAM video. Very well explained. Keep the video momentum coming. The Hercules community welcome your contribution to the our beloved dinosaur mainframe. Thanks again Moshix.
Hi Moshix This is frank from LA I just let you know that I am greatly appreciated for all of your video and I learn a lot from your video Please forgive me way I ask question about creat new video On VSAM. Thanks a lot
actually, only the first two bytes represent the key of the employee dataset. i fooled around a bit with several key collisions between existing records and a couple of variations of the EMPLOYE.INDD file, and records with new keys got inserted.
@paul harvey It can still process records sequentially and one does not need an ESDS for that, albeit that it is more efficient, but a KSDS can be read in a sequential fashion as well... I mean, What on earth is the point of creating a sequential VSAM file?
Great video, as always. I had been struggling since last night trying to figure out the requisite parameters to Define Cluster. The ones you use finally gave me CC=0.
Going now straight to other VSAM videos you've uploaded. Thanks so much.
Thanks for watching !
I really appreciate that you've put together these videos! I am learning a lot. Your examples here demonstrate creating VSAM clusters outside of a user catalog (so I've learned). I believe that means the data sets are cataloged in the master catalog as a result. It would be cool to see you do a video on managing VSAM data sets that have been suballocated inside a user catalog.
Also, the 'unique' parameter doesn't specify that the keys must be unique. That parameter is what you have to provide if you want IDCAMS to create a VSAM cluster separately from a user catalog. I think if you had just re-run your REPRO job a 2nd time without altering it, you would have gotten the key collision errors. I assume VSAM requires that keys be unique. At least, I have yet to find the documentation on how to say unique/not unique keys.
Thanks I was looking for this one
Looking forward to watch next one access
VSAM from Cobol program thanks for all your help.
The Key in the Primary Index is ALWAYS unique. No need to specify. Also, you mention two keys when looking at the inputdata. What you probably mean is that the second 'keyfield' could be used as the key for an Alternate Index, AIX, which is another story. Lastly, the problem you run into, after changing the inputfile key Value, is beacuse the VSAM Cluster was already filled with records. Thats why you got error-message for ALL KEYS, and has nothing to do with 'VSAM transactions'. You need to Delete and Repro again to have the result you were expected with the only duplicate key.
I'm a new Sysadim for Z/os. Excellent Video! Looking forward to the next one!
Thank you for your VSAM video. Very well explained. Keep the video momentum coming. The Hercules community welcome your contribution to the our beloved dinosaur mainframe. Thanks again Moshix.
Rocky Yap thank you very much for your kind words!
Outstandng! Followed along everything completely.
Cool !
Hi Moshix
This is frank from LA I just let you know that I am greatly appreciated for all of your video and I learn a lot from your video
Please forgive me way I ask question about creat new video
On VSAM.
Thanks a lot
You’re very welcome Frank !
I see there’s a redbook entitled “Everything You Wanted to Know About IDCAMS, but Were Afraid to Ask”.
Hahahaha
Oh, man - remember those cheesy Deltek instructional / training courses? They were goofy and dated even then.
Nice! Thank you!
If I wanted to create my own macros within vsam which assembler would you recommend standard assembler or Hassembler
actually, only the first two bytes represent the key of the employee dataset. i fooled around a bit with several key collisions between existing records and a couple of variations of the EMPLOYE.INDD file, and records with new keys got inserted.
yes, you're right, of course. thanks a lot for commenting!
Good Thanks
Found ‘sys2.cmdproc(Klingon)’...
For that matter, “Shutdown” is handy, too!
Report him immediately to the authorities !
Virtual Sequential Acces Method? LOL, You're mixing it up with ISAM (the love of your life) dude... ;-)
I do ?
@@moshixmainframechannel jup, I think you do bro...
Yes I realized it when Gerard wrote
I loved ISAM. Worked like a charm
@paul harvey It can still process records sequentially and one does not need an ESDS for that, albeit that it is more efficient, but a KSDS can be read in a sequential fashion as well... I mean, What on earth is the point of creating a sequential VSAM file?
I have a questions about a VSAM PROJECT
Ask and maybe we can answer