开云体育

Hello, I'm seeing several issues.? I'm hoping to find solutions and learn at the same time. * I create a drive (file) using the dasdinit command, but dasdls isn't finding the VOLSER. * I'm trying to

[email protected]> wrote: [...] 1) If your system supports SATA (which was very normal by 2009, though probably 3 MB/s) then there are SSD drives that will plug in. SATA doesn't care about the drive

I'm playing with porting SQLite to VM/370 CE CMS. It may not be possible - I have to solve a few issues around truncating files and committing data to disk. Both of those are outside the normal realm

Brian_Westerman wrote: No need. It's no secret. My physical mailing address is on my Contact web page: * http://www.softdevlabs.com/about.html I appreciate the offer, but my system is an older used

Hi Fish, Send me your address (offline, not here) and the next time the hard drives and NVMe or SSD drives (if your motherboard can support NVMe) go on a good sale I'll have some shipped to you. Brian

Brian_Westerman wrote: Hmmm... Okay, I think I see your strategy now. Cool! Even with the limit of 8 shadow file sets, you still are able to keep a restorable shadow file set snapshot history of

Hi Fish, The reason I use DASDCOPY64 is because I am then left with an unchanged old BASE and shadow 1 that can be mix/matched with later maintenance to get to just the level of maintenance I want.?

Brian_Westerman wrote: [...] Quite true, BUT... That would *only* occur if you never merged any of your shadow file sets. But again, why would you do that? Not merge your shadow file sets once you

I also use shadow files, but unlike Fish, I do (occasionally) merge them.? I usually do this once per year.? I think that Fish doesn't have the same issue that arises when you apply maintenance to

[...] That should of course be: "merge my set #2 into my set #1".

Ross Patterson wrote: Exactly my question. "literally everything I've ever done" only applies if you only create a shadow file and then never create another one ever again. Which is fine I suppose.

Ross, I think you deserve a huge thank you for your tenacity in tracking down this problem. It was a really sticky one. Despit it being exonerated I still think the GCC log() could do with a clean-up.

I’m so glad you asked this question and I look forward to reading the responses. I’m not sure why I shouldn’t merge to the base files either, I have the original base files anyway if I need to

wrote: After weeks of diagnosis, the problem turned out to be a bad fix for Hercules Hyperion issue #382 <https://github.com/SDL-Hercules-390/hyperion/issues/382>. The result of the bad fix was

I'm considering merging my disks' shadow files into their base files. Why? Well, because ... I dunno, it seems like I don't need the ability to undo literally everything I've ever done on my VM/CE

Fish wrote: Fix committed to develop branch and will appear in next release. For those who want the fix now, you'll of course have to rebuild the develop branch of Hercules for yourself. Thanks again

Doug Wegscheid wrote: [...] Excellent point, Doug! I'm embarrassed I hadn't thought of that myself. As I said, I must be losing my edge. I'll look into it. It should hopefully be a simple change. Stay

Don't feel stupid, and don't stop asking questions. Part of the reason we are all here is to learn, from wherever we started. Some of these people can still run circles around the rest of us. Some of

I don’t consider any questions dumb. People ask them in order to understand how it’s done in VM, DOS, VS1… etc… Some people do real well by reading the manuals, however the manuals only tell

Can dasdls be changed to print the volser if there is a VOL1 record, but no DSCB 4? I don't understand why the lack of a DSCB 4 would prevent detection of the VOLSER?