by steve-myers » Mon Sep 06, 2010 8:04 pm
There is a disconnect here, too.
Within a single job - and that's what an FTP server is in z/OS - the the translation of a relative generation in a generation data group to their corresponding fixed generation are fixed from the first appearance of the generation data group in JCL or dynamic allocation. In other words, the first time you allocate a new GDG(+1) in JCL, or in a z/OS FTP server, z/OS will assign the appropriate GnnnnV00, and that will stay fixed for the life of the job (or z/OS FTP server. A subsequent attempt the allocate a GDG(+1) will use the same GnnnnV00, and the allocation will fail because there is already a GnnnnV00 allocated. In TSO you would get message IKJ56871I DATA SET xxxxxx.TESTGDG NOT ALLOCATED, RELATIVE GENERATION NUMBER INCOMPATIBLE FOR SPECIFIED STATUS (assuming xxxxxx.TESTGDG is a proper GDG index). The disconnect here is that an FTP server in z/OS is a job; the PUT requests from clients are processed as a single job in z/OS, not as individual "jobs," even if the PUT requests are separated by many hours, or even days since normally the FTP server is run as a single job in z/OS, usually until the system as a whole is shut down in preparation for an IPL.
Hope this helps.