Aha... I see...

So mistery solved.

Thank you all!

开云体育

Also if you look up this:

IEF287I ALEX.WEBSITES.RE240123.ACESSLOG NOT CATLGD 4

IEF287I tells you the same thing, that the catalog is out of space

Dennis

开云体育

开云体育

Hi. Sure.

First, from the beggining of the output, JES lookus unhappy:

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!

?

?

I am pleased to announce the following ISPF (ISPF-like product from Wally Mclaughlin) add-on updates.? Below are highlights and links:

?

1. VSI (VSAM Information) add-on displays VSAM file information on one screen. VSI is a transformation of VI (CBT File #137) originally authored by Steve Kleeves as a ISPF/REXX solution by ‘scraping’ a LISTCAT report. VSI is rewritten using CLIST and ISPF services from ISPF 2.2 (Wally Mclaughlin’s ISPF-like product). This function will be used as a selection code from the DVTOC VTOC Entries screen. ?See post for more details, download link, and information on accessing a demo version from your 3270 emulator.
   
   
   
2. CPRT36 (Hardcopy Utility) add-on provides a simple and elementary batch (using IEBGENER) or foreground (using PRINTOFF) dataset printing function.? It ?enables the currently inactive option 3.6 on ISPF 2.2. ?See post for more details, download link, and information on accessing a demo version from your 3270 emulator.
   
   
   
3. DVTOC (Display VTOC Entries) add-on underwent maintenance to ensure all working-storage (GETMAIN storage) was initialized and utilized accordingly per ?RENT,REUS attributes.? Other modifications included capturing all DVTOC requests to ISPF log (via CLOGIT) , content updates to help / tutorials panels and adding two new selection codes to the DVTOC VTOC Entries dataset list (L – listcat ?and VI – VSAM information). ?See post for more details, download link, and information on accessing a demo version from your 3270 emulator.
   
   
   
4. DALCDS (Display Allocations) add-on underwent a minor modification to correct resetting of DD and DSN counters display on the status line of the results display screen and ensure proper use of working-storage (GETMAIN storage) per RENT,REUS attributes.? Help and tutorial content was updated accordingly. ?See post for more details, download link, and information on accessing a demo version from your 3270 emulator.
   
   
   
5. The ISPF 2.2 primary menu has an inactive option T (Tutorial) – Display Information about ISPF.? To fill this gap, using the ISPF 2.2 primary option menu as a tutorial guide, I created a ISPF Tutorial set assembled from ISPF 2.2 content (provided in Wally’s ISPF distribution) along with REVIEW content (from Greg Price’s Z/OS panels) resulting in a foundational ISPF tutorial!? Some of the options are shell panels.? This tutorial is a starting-point and will be incrementally augmented over time. ?See post for more details, download link, and information on accessing a demo version from your 3270 emulator.
   ?
   
   

?

?

?

The above add-ons include installation JCL requiring adjustments based on your MVS 3.8J system (e.g. TK3, TK4- or TK5).

?

For all add-ons, please review the readme.txt file and satisfy all pre-reqs before attempting to use.

?

?

While corresponding recently with Rob Prins, some of the above add-ons will be included in the upcoming release update of TK5.

?

As always, your feedback is welcomed.?

?

?

Enjoy!!!

Larry Belmontes

?

That was the problem, interesting thing though, once I mounted the volume on 38F, all the data was there, but ISPF wouldn't start with an error saying it couldn't access the libraries.? Take it back out of the equation and ISPF started at logon as usual, so I created a new 3380 volume, attached it to 38F, initialized it and ISPF stayed working.? In any event I was able to back up all the data (except the VSAM clusters which weren't important--only test data) and it's back in action.? Lesson learned.

I appreciate all the help and advice received here.? Thank you all.

--scott

Hi Scott,

Is it right, that this volume is on address 294?
294 is a unit address of a 3390.
You mentioned in your start-post, that your volume is a 3380.

That could be rhe reason of the IO-error.
If your volume is a 3380, mount the volume on 280, 281... 28F or on 381 - 38F.

Cheers,
Rob

On 22/01/2024 1:20 pm, Scott Johnson wrote:

Recently, when saving a member to a PDS I've been getting this message

SCOTT? ?,ISPFTSO ,294,DA,SYS00083,WRITE ,OVERFLOW INCOMP,0000000A000A02,BSAM

returning to REVEDIT, displays "I/O error", and another save operation works fine.? The 294 DASD is a 3380 volume that I've created with dasdinit, and seems to work just fine otherwise. This is the only place I've seen an error in regards to this volume.

Any ideas?? Yes, I'm backing up the entire dasd set 2 or thee times a day to not lose any work.

Thanks in advance,

Scott

Might the error occur once, and then not again until you compress the PDS?

I suspect a bad track in the allocated space of the PDS, and saving it again will commence writing to space after the location of the I/O error.

After a compress, saving data will eventually hit that spot again.

That message text comes from REVIEW's DCB SYNAD exit where SYNADAF ACSMETH=BSAM is coded, which is why it says BSAM and not BPAM.

IBM's doc for OVERFLOW INCOMP is:
Invalid track format, trying to write too much data on a track or the format of
the data on the track was not valid for the type of operation being performed.

I expect moving all the data sets on that volume to a new DASD volume would solve the problem, after which you could delete that volume image.

If you did not want to do all that, you could copy the PDS to a new PDS to save the data, and rename the PDSes so you can continue normal processing with the relocated copy.
You could abandon the old disk space by leaving the old (now renamed) data set there to prevent reuse of that space and so avoid future I/O errors, or you could try running somitcw's EOFDISK program to the old data set which deletes all the data from each track in the allocated space of the target DD, and hope that clears the error.

I expect others can make even better suggestions.

Cheers,
Greg

Scott Johnson wrote:

Recently, when saving a member to a PDS I've been getting
this message:

SCOTT ,ISPFTSO ,294,DA,SYS00083,WRITE ,OVERFLOW
INCOMP,0000000A000A02,BSAM

That's an MVS message, yes? Does anything also appear on the Hercules console when this error message? If yes, then it's a bona fide I/O error.

Second question: is it reproducible? Is there a sequence of actions that can trigger this error on demand? If yes, then I would suggest enabling CCW tracing on device 294, so we can the CCW chain that MVS is issuing. That would provide a clue as to what's going on.

May we see your Hercules log when this error occurs? Seeing your config file might also help.

Thanks.

--
"Fish" (David B. Trout)
Software Development Laboratories

mail: fish@...

Recently, when saving a member to a PDS I've been getting this message

SCOTT? ?,ISPFTSO ,294,DA,SYS00083,WRITE ,OVERFLOW INCOMP,0000000A000A02,BSAM

returning to REVEDIT, displays "I/O error", and another save operation works fine.? The 294 DASD is a 3380 volume that I've created with dasdinit, and seems to work just fine otherwise. This is the only place I've seen an error in regards to this volume.

Any ideas?? Yes, I'm backing up the entire dasd set 2 or thee times a day to not lose any work.

Thanks in advance,

Scott

John,

You may need to do a CLPA or at least an MLPA ...

Mark

On 20/01/2024 6:40 am, John James wrote:

Does anyone have any idea what a system FFF abend is?

I'd say it means that SVC 255 was not installed on this system.

Cheers,
Greg

Hello Mark, good to know that there's t least one kindred spirit out there.

So I followed the advice in the old Volker Bandke post that was contributed a few days ago, and re-ran the DBDGEN using macros from MVT instaed of MVS (DCB and 3 IHB macros). Then I re-tried the TESTLOAD COBOL program and specified a VSAM cluster with AMP instead of an ISAM file for the TESTDB DD statement.

Didn't get very far, only as far as the first DL/I ISRT call...

Does anyone have any idea what a system FFF abend is? I found only one brief mention anywhere online, and it talked about "contention". I'll keep looking for other information online, but all ideas accepted in the meantime!

Thanks, JJ

I am also interested in MVSDDT because of some debugging I needed to do the day before yesterday, but it seems it requires communication with a Java task and run a gui next to the 3270 so I lapsed into stacking TSO TEST commands in a Rexx (and temporarily moving stuff to z/OS 2.5 (the employer's) because I never did that in bRexx yet and I had a presentation in the morning).

Meanwhile I have located documentation of MVSDDT and I will give it a shot when time allows, because it looks brilliant and just what the doctor ordered. Will keep you abreast of developments.

best regards,

搁别苍é.