Keyboard Shortcuts
Likes
- H390-Vm
- Messages
Search
Re: Do I have a looping issue?
¿ªÔÆÌåÓýJoe, But isn¡¯t this VM/370 and classic MVS 3.8J? Dave ? From: [email protected] <[email protected]> On Behalf Of Joe Monk
Sent: 26 October 2022 11:39 To: [email protected] Subject: Re: [h390-vm] Do I have a looping issue? ? ISTM that this is normal for VM ... ? "Some?instructions are?valid?either?in the?370-XA mode?or in the System/370?mode,?but not in both modes.?If instruction?interception?is either?mandatory or conditional in?the?mode?in which the instruction?is valid,?then?it?is?undefined whether?instruction interception?is?recognized unconditionally or?an?operation exception?is?recognized in the invalid?mode. When?code?04?is?stored, guest?instruction?execution?is?suppressed, except for the?COMPARE AND?SWAP,?COMPARE?DOUBLE?AND?SWAP,?and?TEST?AND?SET?instructions?(which are completed)." page 11 Note that his code 4 is occurring on a compare_and_swap ... ? Joe ? ? ? On Tue, Oct 25, 2022 at 11:29 PM Fish Fish <david.b.trout@...> wrote:
|
Re: Do I have a looping issue?
toggle quoted message
Show quoted text
-----Original Message-----It does VM uses exceptions to manage privileged mode.... noand Hercules version 4.4.1.10647-SDL-gd0ccfbc9. I've recently noticedV:00FE3E30:R:00000000007E3E30:K:06=009BCD10 809BCF98 ... They *appear* to be legitimate errors, as in whatever you're running in/on yourThis is how VM manages privileged mode exceptions. Take a look at DMKPRV which handles the simulation of the "CS" instruction... Nope. If it was wouldn't the failing program in MVS abend. Dave |
Re: Do I have a looping issue?
¿ªÔÆÌåÓýNot relevant Dave ? From: [email protected] <[email protected]> On Behalf Of Joe Monk
Sent: 26 October 2022 11:39 To: [email protected] Subject: Re: [h390-vm] Do I have a looping issue? ? ISTM that this is normal for VM ... ? "Some?instructions are?valid?either?in the?370-XA mode?or in the System/370?mode,?but not in both modes.?If instruction?interception?is either?mandatory or conditional in?the?mode?in which the instruction?is valid,?then?it?is?undefined whether?instruction interception?is?recognized unconditionally or?an?operation exception?is?recognized in the invalid?mode. When?code?04?is?stored, guest?instruction?execution?is?suppressed, except for the?COMPARE AND?SWAP,?COMPARE?DOUBLE?AND?SWAP,?and?TEST?AND?SET?instructions?(which are completed)." page 11 Note that his code 4 is occurring on a compare_and_swap ... ? Joe ? ? ? On Tue, Oct 25, 2022 at 11:29 PM Fish Fish <david.b.trout@...> wrote:
|
Re: Do I have a looping issue?
ISTM that this is normal for VM ... "Some?instructions are?valid?either?in the?370-XA mode?or in the System/370?mode,?but not in both modes.?If instruction?interception?is either?mandatory or conditional in?the?mode?in which the instruction?is valid,?then?it?is?undefined whether?instruction interception?is?recognized unconditionally or?an?operation exception?is?recognized in the invalid?mode. When?code?04?is?stored, guest?instruction?execution?is?suppressed, except for the?COMPARE AND?SWAP,?COMPARE?DOUBLE?AND?SWAP,?and?TEST?AND?SET?instructions?(which are completed)." page 11 Note that his code 4 is occurring on a compare_and_swap ... Joe On Tue, Oct 25, 2022 at 11:29 PM Fish Fish <david.b.trout@...> wrote: Jim Snellen wrote: |
Re: Do I have a looping issue?
toggle quoted message
Show quoted text
-----Original Message-----I doubt it. IIRC, these messages come from the tailoring of the OS by Hercules, asOSTAILOR is *not* going to help in this situation. The defined default OSTAILOR I don't believe so I think this is VM's smoke and mirrors and its normal way of safely simulating priviledged mode .... So when you are running under VM. Exceptions and Exception Handling is the way VM/370 manages programs running in Virtual Supervisor state. So VM/CP NEVER NEVER NEVER dispatches to a VM in real Supervisor State, it only ever dispatches in Problem State. Then when the program running in the VM executes a privileged instruction it gains control and can then decide what to do. It may reflect the error back to the VM or simulate the instruction. (note:- the CP in HPO does dispatch in real supervisor state when PMA is available and MVS is running V=R) Dave |
Re: Do I have a looping issue?
Fish wrote:
Ren¨¦ Ferland wrote:(ACK!) I meant "Of course NOT!" Sorry. Typo.What would happen if OSTAILOR QUIET is coded? Would theOf course. BUT... Yes, you are correct that OSTAILOR QUIET would indeed *suppress* the message. The error message would indeed disappear if OSTAILOR QUIET was coded. I guess I was typing too fast. Sorry! But my previous point still stands: one should *never* use ostailor quiet! It only exists for extremely narrow case testing case purposes (just as the ostailor null exists for the same reason), but should *never* be used in normal Hercules use cases. Using it prevents you from seeing important program interrupt messages that are virtually *always* indicative of a program error somewhere. You should *only* use one of our pre-defined ostailor values for the guest you are running (or in the case of VM, a combination of values, as illustrated in my previous post). -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@... |
Re: Do I have a looping issue?
Ren¨¦ Ferland wrote:
What would happen if OSTAILOR QUIET is coded? Would theOf course. BUT... One should **NEVER** use OSTAILOR QUIET for that very reason! Doing so masks (hides) bona fide (legitimate) programming errors! You can manually disable the reporting of *any* program interrupt message less than X'40' via the "pgmtrace" command. Together, with OSTAILOR, the two commands allow you to customize Hercules's reporting of Program Interrupts however you want: HHC01603I * HHC01603I * HHC01603I * HHC01603I help pgmtrace HHC01603I HHC01602I Command Description HHC01602I ---------------- ------------------------------------------------------- HHC01602I pgmtrace *Trace program interrupts HHC01603I HHC01603I Format: "pgmtrace [-]intcode" where 'intcode' is any valid program HHC01603I interruption code in the range 0x01 to 0x40. Precede the interrupt HHC01603I code with a '-' to stop tracing of that particular program HHC01603I interruption. HHC01603I HHC01603I * HHC01603I * HHC01603I * HHC01603I * HHC01603I pgmtrace HHC02281I * = Tracing suppressed; otherwise tracing enabled HHC02281I 0000000000000001111111111111111222222222222222233333333333333334 HHC02281I 123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0 HHC02281I * * ** * * ** ** * * * * HHC01603I * HHC01603I * HHC01603I * HHC01603I ostailor HHC02203I OSTAILOR : z/OS HHC01603I * HHC01603I * HHC01603I * HHC01603I * HHC01603I help ostailor HHC01603I HHC01602I Command Description HHC01602I ---------------- ------------------------------------------------------- HHC01602I ostailor *Tailor trace information for specific OS HHC01603I HHC01603I Format: "ostailor [quiet|os/390|z/os|vm|vse|z/vse|linux|opensolaris|null]". HHC01603I Specifies the intended operating system. The effect is to reduce HHC01603I control panel message traffic by selectively suppressing program HHC01603I check trace messages which are considered normal in the specified HHC01603I environment. The option 'quiet' suppresses all exception messages, HHC01603I whereas 'null' suppresses none of them. The other options suppress HHC01603I some messages and not others depending on the specified o/s. Prefix HHC01603I values with '+' to combine them with existing values or '-' to exclude HHC01603I them. SEE ALSO the 'pgmtrace' command which allows you to further fine HHC01603I tune the tracing of program interrupt exceptions. HHC01603I HHC01603I * HHC01603I * HHC01603I * HHC01603I * HHC01603I ostailor vm HHC01603I * HHC01603I * HHC01603I * HHC01603I ostailor HHC02203I OSTAILOR : VM HHC01603I * HHC01603I * HHC01603I * HHC01603I pgmtrace HHC02281I * = Tracing suppressed; otherwise tracing enabled HHC02281I 0000000000000001111111111111111222222222222222233333333333333334 HHC02281I 123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0 HHC02281I ** ** * * * HHC01603I * HHC01603I * HHC01603I * HHC01603I * HHC01603I * HHC01603I ostailor vse HHC01603I * HHC01603I * HHC01603I * HHC01603I * HHC01603I pgmtrace HHC02281I * = Tracing suppressed; otherwise tracing enabled HHC02281I 0000000000000001111111111111111222222222222222233333333333333334 HHC02281I 123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0 HHC02281I ** * * ** ** * * HHC01603I * HHC01603I * HHC01603I * HHC01603I * HHC01603I ostailor vse+vm HHC02205E Invalid argument vse+vm: unknown OS tailor specification HHC00007I Previous message from function 'ostailor_cmd' at hsccmd.c(6685) HHC01603I * HHC01603I * HHC01603I * HHC01603I ostailor HHC02203I OSTAILOR : VSE HHC01603I ostailor +vm HHC01603I * HHC01603I * HHC01603I * HHC01603I ostailor HHC02203I OSTAILOR : VM+VSE HHC01603I * HHC01603I * HHC01603I * HHC01603I * HHC01603I pgmtrace HHC02281I * = Tracing suppressed; otherwise tracing enabled HHC02281I 0000000000000001111111111111111222222222222222233333333333333334 HHC02281I 123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0 HHC02281I ** ** * * ** ** * * HHC01603I * HHC01603I * HHC01603I * HHC01603I * HHC01603I pgmtrace -08 HHC01603I * HHC01603I * HHC01603I * HHC01603I pgmtrace HHC02281I * = Tracing suppressed; otherwise tracing enabled HHC02281I 0000000000000001111111111111111222222222222222233333333333333334 HHC02281I 123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0 HHC02281I ** * ** * * ** ** * * HHC01603I pgmtrace +08 HHC01603I pgmtrace HHC02281I * = Tracing suppressed; otherwise tracing enabled HHC02281I 0000000000000001111111111111111222222222222222233333333333333334 HHC02281I 123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0 HHC02281I ** ** * * ** ** * * HHC01603I * HHC01603I * HHC01603I * Hope that helps! -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@... |
Re: Do I have a looping issue?
On Tue, Oct 25, 2022 at 09:35 PM, Fish Fish wrote:
I disagree. (Well, maybe not HIM, but *something* *somewhere* in one of his guests is definitely doing something wrong!)Well, I am the one in error this time :-(? But to my defense, I am not a Hercules person! :-) OSTAILOR is *not* going to help in this situation. The defined default OSTAILOR values for each supported flavor of operating system will *never* mask a Protection Exception. A Protection Exception is an indication of a bona fide programming error somewhere.What would happen if OSTAILOR QUIET is coded? Would the error appear anyway? Just curious... Cheers, Rene FERLAND, Montreal |
Re: Do I have a looping issue?
Fish wrote:
Jim Snellen wrote:[...] [...]HHC02324I PSW=078D2000000383EC INST=BA661000 CS 6,6,0(1)compare_and_swapHHC02326I V:00FE3E30:R:00000000007E3E30:K:06=009BCD10 809BCF98 ...[...]HHC00801I Processor CP00: Protection exception code 0004 ilc 4 According to the PSW, the program is running in Problem StateAre you perhaps trying to run some type of CICS application or something? I personally have no experience whatsoever with running CICS, but the Key 8 issue tickled something in my ancient memory somewhere, so I did a few quick searches and found the following 21 year old post: * It mentions something about Key 8 and Key 9 and CICS. I don't understand any of it myself, but maybe it makes sense to you?? Just trying to help! -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@... |
Re: Do I have a looping issue?
Ren¨¦ Ferland wrote:
Jim Snellen wrote:I disagree. (Well, maybe not HIM, but *something* *somewhere* in one of his guests is definitely doing something wrong!)Am I doing something wrong to cause this?You are not doing anything wrong Jim. IIRC, these messages come from the tailoring of the OS byOSTAILOR is *not* going to help in this situation. The defined default OSTAILOR values for each supported flavor of operating system will *never* mask a Protection Exception. A Protection Exception is an indication of a bona fide programming error somewhere. Check your code. It's buggy. -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@... |
Re: Do I have a looping issue?
Jim Snellen wrote:
I am running VM/370 with DOS/VS as a guest machine andWhich should not make any difference. and Hercules version 4.4.1.10647-SDL-gd0ccfbc9. I've recently[...] HHC00801I Processor CP00: Protection exception code 0004 ilc 4[...] Am I doing something wrong to cause this? It looks likeThey *appear* to be legitimate errors, as in whatever you're running in/on your guest is not doing something correctly (i.e. something is malfunctioning, i.e. some piece of software you're running is buggy). According to the PSW, the program is running in Problem State with PSW Key 8 (the "8D" in your PSW), but the storage the 'CS' (Compare and Swap) instruction is trying to access is Key 0 (the '0' in "K:06"), which by my calculations would indeed cause a bona fide Protection Exception Program Interrupt. <shrug> Check your code. I suspect it's buggy. -- "Fish" (David B. Trout) Software Development Laboratories mail: fish@... |
Re: Do I have a looping issue?
On Tue, Oct 25, 2022 at 07:33 PM, Jim Snellen wrote:
Am I doing something wrong to cause this?You are not doing anything wrong Jim. IIRC, these messages come from the tailoring of the OS by Hercules, as specified by the OSTAILOR statement in the configuration file. Check the documentation of Hercules to set this parameter to an appropriate value for you.? Cheers, Rene FERLAND, Montreal |
Do I have a looping issue?
I am running VM/370 with DOS/VS as a guest machine and MVS 3.8J TK4- as a guest machine.? I use HercGUI and Hercules version 4.4.1.10647-SDL-gd0ccfbc9.? I've recently noticed that a recurring display occurs:
22:21:46.721 000060B8 HHC02324I PSW=078D2000000383EC INST=BA661000? ? ?CS? ? 6,6,0(1)? ? ? ? ? ? ? ?compare_and_swap
22:21:46.721 000060B8 HHC02326I V:00FE3E30:R:00000000007E3E30:K:06=009BCD10 809BCF98 00404040 40404040? .......q.
22:21:46.722 000060B8 HHC02269I GR00=00000001 GR01=00FE3E30 GR02=00FE3000 GR03=00FE3000
22:21:46.722 000060B8 HHC02269I GR04=009BC7B0 GR05=00000C5C GR06=009BCD10 GR07=00000C54
22:21:46.722 000060B8 HHC02269I GR08=00000001 GR09=00000003 GR10=009BDB58 GR11=009BDE48
22:21:46.722 000060B8 HHC02269I GR12=60038376 GR13=0009C978 GR14=40017C44 GR15=009BDB58
22:21:46.722 000060B8 HHC02271I CR00=81800CC0 CR01=0FFF9C00 CR02=FFFFFFFF CR03=00000000
22:21:46.722 000060B8 HHC02271I CR04=00000000 CR05=00000000 CR06=87FBAE10 CR07=00000000
22:21:46.722 000060B8 HHC02271I CR08=00000000 CR09=00000000 CR10=00000000 CR11=00000000
22:21:46.722 000060B8 HHC02271I CR12=00000000 CR13=00000000 CR14=EFC00000 CR15=00000000
22:21:47.221 000060B8 HHC00801I Processor CP00: Protection exception code 0004 ilc 4
22:21:47.221 000060B8 HHC02324I PSW=078D2000000383EC INST=BA661000? ? ?CS? ? 6,6,0(1)? ? ? ? ? ? ? ?compare_and_swap
22:21:47.221 000060B8 HHC02326I V:00FE3E30:R:00000000007E3E30:K:06=809BCD10 809BCF98 00404040 40404040? .......q.
22:21:47.221 000060B8 HHC02269I GR00=00000000 GR01=00FE3E30 GR02=00FE3000 GR03=00FE3000
22:21:47.221 000060B8 HHC02269I GR04=009BC7B0 GR05=00000C5C GR06=809BCD10 GR07=00000C54
22:21:47.221 000060B8 HHC02269I GR08=00000001 GR09=00000000 GR10=009BDB58 GR11=009BDDA8
22:21:47.221 000060B8 HHC02269I GR12=60038376 GR13=0009CA08 GR14=4001815A GR15=009BDB58
22:21:47.221 000060B8 HHC02271I CR00=81800CC0 CR01=0FFF9C00 CR02=FFFFFFFF CR03=00000000
22:21:47.221 000060B8 HHC02271I CR04=00000000 CR05=00000000 CR06=87FBAE10 CR07=00000000
22:21:47.221 000060B8 HHC02271I CR08=00000000 CR09=00000000 CR10=00000000 CR11=00000000
22:21:47.221 000060B8 HHC02271I CR12=00000000 CR13=00000000 CR14=EFC00000 CR15=00000000
22:21:47.223 000060B8 HHC00801I Processor CP00: Protection exception code 0004 ilc 4
22:21:47.223 000060B8 HHC02324I PSW=078D2000000383EC INST=BA661000? ? ?CS? ? 6,6,0(1)? ? ? ? ? ? ? ?compare_and_swap
22:21:47.223 000060B8 HHC02326I V:00FE3E30:R:00000000007E3E30:K:06=009BCD10 809BCF98 00404040 40404040? .......q.
22:21:47.223 000060B8 HHC02269I GR00=00000001 GR01=00FE3E30 GR02=00FE3000 GR03=00FE3000
22:21:47.223 000060B8 HHC02269I GR04=009BC7B0 GR05=00000C5C GR06=009BCD10 GR07=00000C54
22:21:47.223 000060B8 HHC02269I GR08=00000001 GR09=00000003 GR10=009BDB58 GR11=009BDE48
22:21:47.223 000060B8 HHC02269I GR12=60038376 GR13=0009C978 GR14=40017C44 GR15=009BDB58
22:21:47.223 000060B8 HHC02271I CR00=81800CC0 CR01=0FFF9C00 CR02=FFFFFFFF CR03=00000000
22:21:47.223 000060B8 HHC02271I CR04=00000000 CR05=00000000 CR06=87FBAE10 CR07=00000000
22:21:47.223 000060B8 HHC02271I CR08=00000000 CR09=00000000 CR10=00000000 CR11=00000000
22:21:47.223 000060B8 HHC02271I CR12=00000000 CR13=00000000 CR14=EFC00000 CR15=00000000
22:21:47.603 000060B8 HHC01603I stopall
I pressed the STOP button to capture the above. Am I doing something wrong to cause this?? It looks like these messages are going to the log file and there's a lot of these! |
Re: OSI was Re: [h390-vm] Three questions about VM/CE (Left, middle, and right field question)
On 25/10/2022 15:16, Harold Grovesteen wrote:
While being made in jest, this view fails to recognize the contributionIn a previous life I connected a Sun Solaris system to an IBM mainframe, using FTAM (OSI equivalent of FTP) over ISO CONS / X.25 PSDN. That was to retrieve SWIFT MT940 files from bank in Germany. At the same place we also used X.400 messaging to transact with EDI partners, for just-in-time fulfilment (this was at boo.com back in 1999). ISO networking was also implemented as DECnet Phase V a.k.a. DECnet/OSI. Systems with this could be configured with "dual towers" (stacks), supporting legacy Phase IV addressing and applications, plus Phase V complete with NSAPs etc. In previous previous lives I've used this with DEC X.500 Directory Server and MAILbus X.400 MTA. ICL also adopted ISO networking for mainframe and midrange, via ICL OSLAN. At the first place I worked we had ICL Series 39, ICL TeamServer UNIX and VAX/VMS systems all communicating via an ISO TP4 national network. While TCP/IP "beat" out the OSI Layer 3 and 4 network standards andAlso LDAP being a paired back version X.500/DAP, with functionality which pales in comparison with its forebear. X.509 certificates underpin things such as SSL/TLS and IPsec. And much ASN.1 to be found in the world of telecoms. Probably numerous other examples of OSI legacy. Andrew |
Re: Would anyone like ....
I fully understood your personal goals. However, the other side of the
toggle quoted message
Show quoted text
question, "anyone" in the title, did not include this alternative view that I felt deserved mentioning. That's all. Harold On Tue, 2022-10-25 at 08:31 -0500, Bertram Moshier wrote:
Hello Harold, |
OSI was Re: [h390-vm] Three questions about VM/CE (Left, middle, and right field question)
While being made in jest, this view fails to recognize the contribution
toggle quoted message
Show quoted text
to networking OSI has made and continues to make. "OSI" is really three things: - the Model, - the Standards, and - the Implementations. The Model came out in the early 80's and is just as valuable today as it was when it was developed for discussing networks of varying types. The standards were an outgrowth of the model. The implementation was the concrete realization of an OSI network based upon the standards. (And, as has been observed, IBM's _implementation_ did not succeed in the market place for a number of reasons. SNA itself being one of them.) While TCP/IP "beat" out the OSI Layer 3 and 4 network standards and obviated the need of the corresponding OSI compatible implementations, OSI standards still persist in today's networking. SNMP being one of the application protocols that continues today. X.3, another example, has migrated into Telent. IS-IS, the routing protocol (an application level protocol used between routers), came from the OSI world. _Because_ TCP/IP is limited to layers 3 and 4, when a network using TCP/IP needed to implement various applications, where did it go? Reinventing the wheel being a waste of time, OSI application layer standards and implementations were a ready source for these missing layers in TCP/IP. Swap out the OSI Layer 4 interface for a host's socket implementation and away you go. And then there are Layers 1 and 2. Ultimately, the "winner" in the world of networking has and is today determined by market forces, not technical superiority. The implementation that wins in the market place forces the winning standard. Not the other way around. Harold Grovesteen On Thu, 2022-10-20 at 10:56 -0700, Drew Derbyshire wrote:
This a family oriented group. |
Re: Would anyone like ....
Hello Harold, As the originator of this thread, my goal was two fold.? First, to provide a file level backup (and possibly restore) solution.? Second, it was to get back into VM again.? I stopped using VM, unfortunately in 1992 or so (other than as a G user). It is why I wrote the subject as "Would anyone like ..."? I thought maybe there was already an existing VM/CE solution.? From what I'm reading there isn't a VM/CE file level backup solution.? I even remember reading one person saying he'd like to use it on a live VM/ESA real iron system. I look forward to bringing it back to life for my own resurrection in the VM world.? At the time people liked the approach to ask me to present at Share and IBM wanted to buy the rights from OCF to it. I hope this reply answers some of your questions.? As for using Windows to backup our system, sure but its like doing a DDR backup and restore.? You lose all of the system changes since the last DDR or Windows backup.? It also wouldn't help the VM/ESA guy or help me come back to VM. Bertram Moshier On Tue, Oct 25, 2022, 07:41 Harold Grovesteen <h.grovsteen@...> wrote: I have watched this thread and continue to come away with "what is the |
Re: Would anyone like ....
I have watched this thread and continue to come away with "what is the
toggle quoted message
Show quoted text
objective of this discussion?" Is it about backing up your VM DASD or is it about resurrecting some past capability? I realize it could be both. But, no one has mentioned that in the Hercules world, backing up ones DASD can be done quite easily. Place all of your DASD host files in the same directory. Shut down VM. Compress and zip up all of the DASD images into an archive file. Recovery is the reverse, but attach your unzipped DASD volume(s) from which you want to recover files or minidisks to those already gened extra drives in VM and move what needs moving. The Hercules configuration file makes this connection. Be careful to preserve shadow files if you are using them. This may not work as desired so feel free to shoot it down. Just an approach I have not seen discussed. Recovery is ad hoc in most cases. So some augmentation with some VM data when the backup is made might help. But this boils down to level of effort. Let the host do the heavy lifting where it can. Some folks like to stay within the "VM walls". That is perfectly OK, but we are living in a different world with Hercules and can approach problems with Hercules and its host being part of the solution. Harold Grovesteen On Sun, 2022-10-23 at 08:54 -0500, Bertram Moshier wrote:
+Hi, |
On Sat, Oct 15, 2022 at 04:57 PM, Martin Scheffler wrote:
The ingredients for the ALL macro will follow (SET SELECT, SET DISPLAY ...).The first prototype of the ALL command (builtin, not a REXX macro) is here. SET SELECT and SET DISPLAY are operational and almost complete. SET SCOPE is implemented but now there is *much* legwork to do to make all existing commands obey the new situation created by SET SCOPE DISPLAY.? I will push my enhancements to GitHub after some more testing. Should I consider publishing binaries as alpha preview releases ? See screenshots: look for the numbers in the prefix area Highlighting of lines with selection level > 0 |
Re: Would anyone like ....
I like the idea that we are not limited to what was the physical size of the tapes. In an emulated world like Hercules, I would like to set the size of my backup file at just under what I can write to a real CD.
toggle quoted message
Show quoted text
Especially when it comes time to separate one user's files from all the rest and deliver it to that user to take away. I had to do that manually when one of our users moved from one university to another. Or separating one project from the rest for other to work on. /Tom Kern On 10/24/2022 4:50 PM, Fish Fish wrote:
Bertram Moshier wrote: |