Alejandro, please show us the output from your job. Also, you can run a LISTCAT L('ALEX') at the TSO READY prompt, and that will show you what datasets?already exist under that qualifier.
Hi again folks.
I'm sure I'm missing the elefant in the room here, but I'm failing to find information on NOT CATLGD 4 message (I do for code 2, instead of 4) and something very very weird is happening all of the sudden (Tk5).
The issue I'm facing is that, all of the sudden, my jobs to store some sample data under certain PDSs members do fail, after the new PDS to contain those members is apparently created, but definitely not cataloged.
The more puzzling thing I've found, after some trial an errors, is that the problem happens just for datasets being created under certain qualifier!
So, while my webserver access log records are stored under ALEX.WEBSITES.<Tmmddyy>.ACCLOG and firewall records under ALEX.IPBLK.<Tmmddyy>.FWLOG, all jobs for PDSs under ALEX.WESITES. do fail, while the others keep working as usual.
After trial and error, I end up discovered that if I simply change the upper qualification name ALEX.WEBSITES by anything else like ALEX.WEBINFO and resubmit the deck, it completes just fine.
So why a qualifier appears to render like no longer 'catalogeable' any datasets under it? why all of the sudden? Any clues about what that 4 code is telling me?
Cheers!
