Re: z/VM 5.3 FLIST
On Friday, 12/14/2007 at 01:27 EST, Schuh, Richard [EMAIL PROTECTED] wrote: 40x90 is not even an option offered by my emulator. What one do you use and what other exotic sizes does it support? IBM PCOMM, of course! :-) I get any size I want by editing the .ws file and manually filling in the height and width. The standard pull-down on the configuration GUI limits you to the 1980s. :-( I see that Seagull's Bluezone emulator includes a Custom option on the GUI that lets you fill in the dimensions of BOTH the primary and alternate screen sizes. (Though I shudder to think of how apps will respond to an alternate screen size of other than 24x80! It's not like they query the dimensions of anything) Bluezone supports a maximum configuration of 98x160. But that's ok -- I noticed last week XEDIT has a limit of 255 columns! Alan Altmark z/VM Development IBM Endicott
Re: z/VM 5.3 FLIST
On Saturday, 12/15/2007 at 10:25 EST, Phil Smith III [EMAIL PROTECTED] wrote: Do you know anyone in VM development? Yes, though they won't admit it. I have been ready for years to stop reformatting data to accomodate 80 columns. Back when we used Real 3270s, that was an issue. No longer. It is time to take a bold step forward into the 1990s. Nice idea, but unrealistic, since 24x80 is the alternate (should have been alternative) size by default. I've spent decades designing screens knowing that I have to fit in 24x80; would that I could do otherwise. But I've been to far too many customer sites where they have no idea how to configure their emulator and/or they're going through some VTAM that won't accommodate a weird size... I didn't mean to suggest that people shouldn't be free to limit themselves to a measly 24x80 or live with the restrictions imposed by some hidebound VTAM sysprogs, but that the programs should advantage themselves of the any additional real estate the Wise user has configured. Hmmm I wonder if the 3270 CREATE PARTITION outbound structured field will override the emulator configuration hmmm. bwahahahahaaa! Alan Altmark z/VM Development IBM Endicott
Re: z/VM 5.3 FLIST
IBM PCOMM, of course! :-) I get any size I want by editing the .ws file and manually filling in the height and width. The standard pull-down on the configuration GUI limits you to the 1980s. :-( Thanks, Alan! IIRC, sometime in the distant past IBM PComm's pull-down had the capability to permit fill-in-the-blank as well as the standard Models 2/3/4/5. Or maybe that was an OS/2 thing (talk about distant past!). I'll have to set up a separate .ws file for Model 5+ (133 across, 42 down)! Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. (Sent in plain-text, as requested.) Alan Altmark [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 12/17/2007 08:49 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: z/VM 5.3 FLIST On Friday, 12/14/2007 at 01:27 EST, Schuh, Richard [EMAIL PROTECTED] wrote: 40x90 is not even an option offered by my emulator. What one do you use and what other exotic sizes does it support? IBM PCOMM, of course! :-) I get any size I want by editing the .ws file and manually filling in the height and width. The standard pull-down on the configuration GUI limits you to the 1980s. :-( I see that Seagull's Bluezone emulator includes a Custom option on the GUI that lets you fill in the dimensions of BOTH the primary and alternate screen sizes. (Though I shudder to think of how apps will respond to an alternate screen size of other than 24x80! It's not like they query the dimensions of anything) Bluezone supports a maximum configuration of 98x160. But that's ok -- I noticed last week XEDIT has a limit of 255 columns! Alan Altmark z/VM Development IBM Endicott The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email.
Re: z/VM 5.3 FLIST
Imler, Steven J [EMAIL PROTECTED] wrote, re scaling large numbers to 45K etc.: This is exactly the philosophy that CA's V/Seg-Plus uses to display user/system spool file lists ... Just as an example where some users may be able to see this in action! To be fair (since I wrote that code), I should note that this was inspired by the format of QUERY RDR EXP, which does the same scaling. ...phsiii
Re: z/VM 5.3 FLIST
-Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Friday, December 14, 2007 01:18 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST On my z/VM 5.3 system I have 9 characters. But this issue with large disks threatens to get out of hand. Apparently the word isn't getting around that it is time to start scaling these large numbers on displays unless specifically asked for details. 99.999% of the time, I only care about the relative scale of file sizes. Knowing a file has 45K records is just as good as knowing it has 44,727 records. I'm just looking for the big ones to throw away. Naturally LISTFILE shouldn't do the scaling, but FILELIST and FLIST should. Sorting can still work by the unseen real number. If one does a Sort-by-Size operation, THEN the real number is shown and some non-size related field disappears. All assuming, of course, that my 90 column screen can't accomodate the whole thing. (FLIST reverts to 24x80 on my 40x90 screen.) This is exactly the philosophy that CA's V/Seg-Plus uses to display user/system spool file lists ... Just as an example where some users may be able to see this in action! JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED]
Re: z/VM 5.3 FLIST
Jim Bohnsack [EMAIL PROTECTED] wrote: I could retire if a had a dollar, or certainly a euro, for every time I heard the religious argument you have the full power of XEDIT. I still have managed to keep a copy of the full strength FULIST and there are very few times when I use filelist vs fulist. And then there was KFLIST (Kolinar FLIST), which had features like the /D command to delete a file *from the display* and /SV to sort *by return code from a previous command*. I used to use those all the time to build a file view, then issue FORALL cmd or FORREST cmd (the former is like EXECUTE *, the latter is like EXECUTE from the current line to the end -- very useful after you've done something like FORALL FCOMPARE / /nt fm followed by /SV). I find myself using both FLIST and FILELIST as a result; both have their place. EXECUTE * is the main reason FILELIST is sometimes attractive. And bemoaning, daily, the lack of similar functionality in Those Other Operating Systems (no, Windows Explorer is NOT equivalent!)... ...phsiii
Re: z/VM 5.3 FLIST
Given the amount of time that filelist has been available, wouldn't it be more prudent to be requesting the features you feel are lacking in filelist, rather than trying to keep an old sagging horse alive? Obviously, flist is still maintained, since it was changed in the current release. But it would seem that it is being changed without much regard for the user community. I agree that very few useful commands can be entered in seven characters. It doesn't even meet the file name size of eight. Actually, running flist here shows nine characters in the field. The statement was made that browse is required... Can the browse command not be used from filelist? I tried it, and it appears to work. My filelist doesn't have PF10 assigned to anything, and it's the vanilla filelist, so, why not put browse there? Or worst case, rearrange the keys to suit your needs, adding browse in the process? Or, change PF2 to browse, to match flist, and forgo the Refresh Pfkey? The other flist Pfkeys displayed were fairly (completely?) cryptic, and it's been way (waay) too long since I'd used it in any serious capacity. Seriously... It's time to let go of flist and move into the '80s. -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 12/13/07 3:48 PM, George Haddad [EMAIL PROTECTED] wrote: Once upon a time, there was FLIST, but no FILELIST. Some of us old-schoolers still prefer it. Rick Bourgeois wrote: That's very interesting, I've never used FLIST I've always used FILEL so I never saw the change. Rick Bourgeois Virtual Software Systems, Inc. 7715 Browns Bridge Rd Gainesville, GA 30506 [EMAIL PROTECTED] 770-781-3200
Re: z/VM 5.3 FLIST
On Dec 14, 2007 1:28 PM, Phil Smith III [EMAIL PROTECTED] wrote: And bemoaning, daily, the lack of similar functionality in Those Other Operating Systems (no, Windows Explorer is NOT equivalent!)... Oh dear... Just when I was going to offer a massive improvement for FLIST It removes the input area completely, and only offers you the option to position the cursor on the file and press Enter to do the right thing with the file. The right thing to do will be defined in some hard-to-change configuration files that change randomly each time you install new software (to ensure it works differently for each user). Rob (it's friday afternoon already)
Re: z/VM 5.3 FLIST
There are many appends about FLIST so I apologize if this has been suggested before. You can use the USE option of FLIST. This may give you the function you want. It is explained in the HELP file and in the CMS Commands and Utilities book. The book also shows an example of an FLISTS exec to use with the USE option. Colleen M Brown IBM z/VM and Related Products Development and Service
Re: z/VM 5.3 FLIST
On Fri, 14 Dec 2007 09:45:51 -0500, Colleen Brown [EMAIL PROTECTED] wrote: There are many appends about FLIST so I apologize if this has been suggested before. You can use the USE option of FLIST. This may give you the function you want. It is explained in the HELP file and in the CMS Commands and Utilities book. The book also shows an example of an FLISTS exec to use with the USE option. The USE option with the MENU option is great. I first used them back in 1985 to do the screen interface for the client side of a secured printout database. Brian Nielsen
Re: z/VM 5.3 FLIST
On: Fri, Dec 14, 2007 at 09:08:11AM -0600,Brian Nielsen Wrote: } As has been mentioned here before, KEDIT KEX are a wonderful versions of } XEDIT REXX. What may not have been mentioned is that it also is an I will second Brian's admiration of Kedit. For those who have Kedit and are not aware of the new release, be aware that 1.6 is out of beta and is available from thier web site. -- Rich Greenberg N Ft Myers, FL, USA richgr atsign panix.com + 1 239 543 1353 Eastern time. N6LRT I speak for myself my dogs only.VM'er since CP-67 Canines:Val, Red, Shasta Casey (RIP), Red Zero, Siberians Owner:Chinook-L Retired at the beach Asst Owner:Sibernet-L
Re: z/VM 5.3 FLIST
On Fri, 14 Dec 2007 07:28:21 -0500, Phil Smith III [EMAIL PROTECTED] software.com wrote: And bemoaning, daily, the lack of similar functionality in Those Other Operating Systems (no, Windows Explorer is NOT equivalent!)... soapbox As has been mentioned here before, KEDIT KEX are a wonderful versio ns of XEDIT REXX. What may not have been mentioned is that it also is an admirable stand-in for FILELIST/FLIST. It displays the list of files and directories right in an editable file (called dir.dir). There are a couple built-in features for working with files/directories in the list (such as KEDIT a file, navigating through the directory structure, sortin g by various attributes), and I've added a couple of my own (such as ERASE a file, RENAME a file, REFRESH the list, make the displayed directory the current directory). It supports long filenames and allows you to change the columns set aside for the names. With the ability to write KEX macro s you can also do things to lists of files. It's also easy to make it invoke your macros with key sequences or from on screen buttons. /soapbox Brian Nielsen
Re: z/VM 5.3 FLIST
Even better, make the random change with each use. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij Sent: Friday, December 14, 2007 6:37 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST On Dec 14, 2007 1:28 PM, Phil Smith III [EMAIL PROTECTED] wrote: And bemoaning, daily, the lack of similar functionality in Those Other Operating Systems (no, Windows Explorer is NOT equivalent!)... Oh dear... Just when I was going to offer a massive improvement for FLIST It removes the input area completely, and only offers you the option to position the cursor on the file and press Enter to do the right thing with the file. The right thing to do will be defined in some hard-to-change configuration files that change randomly each time you install new software (to ensure it works differently for each user). Rob (it's friday afternoon already)
Re: z/VM 5.3 FLIST
On Dec 14, 2007, at 12:18 PM, Alan Altmark wrote: I have been ready for years to stop reformatting data to accomodate 80 columns. Back when we used Real 3270s, that was an issue. No longer. It is time to take a bold step forward into the 1990s. That's enough outta you, heretic. 80 columns is the right width: long enough to be useful, short enough that you don't have to scan back and forth a lot to read a line. 132 columns is unpleasant. Adam
Re: z/VM 5.3 FLIST
I have been ready for years to stop reformatting data to accomodate 80 columns. Back when we used Real 3270s, that was an issue. No longer. It is time to take a bold step forward into the 1990s. He's a witch! Burn him! (in best Monty Python style...) -- db
Re: z/VM 5.3 FLIST
The USE and MENU options don't get around the problem of the tiny input area. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Colleen Brown Sent: December 14, 2007 09:46 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST There are many appends about FLIST so I apologize if this has been suggested before. You can use the USE option of FLIST. This may give you the function you want. It is explained in the HELP file and in the CMS Commands and Utilities book. The book also shows an example of an FLISTS exec to use with the USE option. Colleen M Brown IBM z/VM and Related Products Development and Service The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: z/VM 5.3 FLIST
On Friday, 12/14/2007 at 12:40 EST, [EMAIL PROTECTED] wrote: The USE and MENU options don?t get around the problem of the tiny input area. On my z/VM 5.3 system I have 9 characters. But this issue with large disks threatens to get out of hand. Apparently the word isn't getting around that it is time to start scaling these large numbers on displays unless specifically asked for details. 99.999% of the time, I only care about the relative scale of file sizes. Knowing a file has 45K records is just as good as knowing it has 44,727 records. I'm just looking for the big ones to throw away. Naturally LISTFILE shouldn't do the scaling, but FILELIST and FLIST should. Sorting can still work by the unseen real number. If one does a Sort-by-Size operation, THEN the real number is shown and some non-size related field disappears. All assuming, of course, that my 90 column screen can't accomodate the whole thing. (FLIST reverts to 24x80 on my 40x90 screen.) I have been ready for years to stop reformatting data to accomodate 80 columns. Back when we used Real 3270s, that was an issue. No longer. It is time to take a bold step forward into the 1990s. Alan Altmark z/VM Development IBM Endicott
Re: z/VM 5.3 FLIST
40x90 is not even an option offered by my emulator. What one do you use and what other exotic sizes does it support? Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Friday, December 14, 2007 10:18 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST On Friday, 12/14/2007 at 12:40 EST, [EMAIL PROTECTED] wrote: The USE and MENU options don?t get around the problem of the tiny input area. On my z/VM 5.3 system I have 9 characters. But this issue with large disks threatens to get out of hand. Apparently the word isn't getting around that it is time to start scaling these large numbers on displays unless specifically asked for details. 99.999% of the time, I only care about the relative scale of file sizes. Knowing a file has 45K records is just as good as knowing it has 44,727 records. I'm just looking for the big ones to throw away. Naturally LISTFILE shouldn't do the scaling, but FILELIST and FLIST should. Sorting can still work by the unseen real number. If one does a Sort-by-Size operation, THEN the real number is shown and some non-size related field disappears. All assuming, of course, that my 90 column screen can't accomodate the whole thing. (FLIST reverts to 24x80 on my 40x90 screen.) I have been ready for years to stop reformatting data to accomodate 80 columns. Back when we used Real 3270s, that was an issue. No longer. It is time to take a bold step forward into the 1990s. Alan Altmark z/VM Development IBM Endicott
Re: z/VM 5.3 FLIST
On the other hand, having had to read as many dumps as I once did, and having received too many files that were formatted for print, I am accustomed to 132 and find that it has none of the drawbacks that 80 byte widths present, i.e. too short to be of any use, too cramped for comments on program lines, etc. And scanning back and forth is no more of a problem than scanning up and down. :-) Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Adam Thornton Sent: Friday, December 14, 2007 10:45 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST On Dec 14, 2007, at 12:18 PM, Alan Altmark wrote: I have been ready for years to stop reformatting data to accomodate 80 columns. Back when we used Real 3270s, that was an issue. No longer. It is time to take a bold step forward into the 1990s. That's enough outta you, heretic. 80 columns is the right width: long enough to be useful, short enough that you don't have to scan back and forth a lot to read a line. 132 columns is unpleasant. Adam
Re: z/VM 5.3 FLIST
Peter, It's been going down steadily. On VM/ESA 2.4 it was 2 bytes. We skipped ahead to z/VM 4.4 and it went down to 16 bytes. I complained (ETR) and was told I could try the old VM/ESA FLIST module. It worked, but the users were okay with 16 characters. Now we are z/VM 5.2 and it is down to 9 characters. That was a little too small, so we copied the 4.4 FLIST onto 5.2 where it is working now. Going down to 7 sounds even worse. Personally, I'd switch to FILELIST if I could figure out how to make the PF keys work right (ie, the same as FLIST). I must have BROWSE! Ron On 12/13/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: We have recently moved to z/VM 5.3 from z/VM 3.1. We are getting lots of complaints about the FLIST command. The command entry area has changed from 20 bytes down to 7 bytes. Yes, I know about PF11, but you used to be able to enter quite a few commands within the 20 bytes. Does anybody know if/how to change it back? Peter
Re: z/VM 5.3 FLIST
Er, that was supposed to be 22 bytes not '2'. (who is this guys editor??) On 12/13/07, Ron Schmiedge [EMAIL PROTECTED] wrote: Peter, It's been going down steadily. On VM/ESA 2.4 it was 2 bytes. We skipped ahead to z/VM 4.4 and it went down to 16 bytes. I complained (ETR) and was told I could try the old VM/ESA FLIST module. It worked, but the users were okay with 16 characters. Now we are z/VM 5.2 and it is down to 9 characters. That was a little too small, so we copied the 4.4 FLIST onto 5.2 where it is working now. Going down to 7 sounds even worse. Personally, I'd switch to FILELIST if I could figure out how to make the PF keys work right (ie, the same as FLIST). I must have BROWSE! Ron On 12/13/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: We have recently moved to z/VM 5.3 from z/VM 3.1. We are getting lots of complaints about the FLIST command. The command entry area has changed from 20 bytes down to 7 bytes. Yes, I know about PF11, but you used to be able to enter quite a few commands within the 20 bytes. Does anybody know if/how to change it back? Peter
Re: z/VM 5.3 FLIST
It wouldn't be so bad if IBM was using the space for something useful, but it just seems to be empty 'wasted space'. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Ron Schmiedge Sent: December 13, 2007 16:06 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST Er, that was supposed to be 22 bytes not '2'. (who is this guys editor??) On 12/13/07, Ron Schmiedge [EMAIL PROTECTED] wrote: Peter, It's been going down steadily. On VM/ESA 2.4 it was 2 bytes. We skipped ahead to z/VM 4.4 and it went down to 16 bytes. I complained (ETR) and was told I could try the old VM/ESA FLIST module. It worked, but the users were okay with 16 characters. Now we are z/VM 5.2 and it is down to 9 characters. That was a little too small, so we copied the 4.4 FLIST onto 5.2 where it is working now. Going down to 7 sounds even worse. Personally, I'd switch to FILELIST if I could figure out how to make the PF keys work right (ie, the same as FLIST). I must have BROWSE! Ron On 12/13/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: We have recently moved to z/VM 5.3 from z/VM 3.1. We are getting lots of complaints about the FLIST command. The command entry area has changed from 20 bytes down to 7 bytes. Yes, I know about PF11, but you used to be able to enter quite a few commands within the 20 bytes. Does anybody know if/how to change it back? Peter The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: z/VM 5.3 FLIST
Didn't know there was something other than FILELIST. Started looking at FLIST. Would the PF11 key help? It looks like the PF11 key increases the input area to end of line. Paul -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 13, 2007 3:09 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST It wouldn't be so bad if IBM was using the space for something useful, but it just seems to be empty 'wasted space'. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Ron Schmiedge Sent: December 13, 2007 16:06 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST Er, that was supposed to be 22 bytes not '2'. (who is this guys editor??) On 12/13/07, Ron Schmiedge [EMAIL PROTECTED] wrote: Peter, It's been going down steadily. On VM/ESA 2.4 it was 2 bytes. We skipped ahead to z/VM 4.4 and it went down to 16 bytes. I complained (ETR) and was told I could try the old VM/ESA FLIST module. It worked, but the users were okay with 16 characters. Now we are z/VM 5.2 and it is down to 9 characters. That was a little too small, so we copied the 4.4 FLIST onto 5.2 where it is working now. Going down to 7 sounds even worse. Personally, I'd switch to FILELIST if I could figure out how to make the PF keys work right (ie, the same as FLIST). I must have BROWSE! Ron On 12/13/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: We have recently moved to z/VM 5.3 from z/VM 3.1. We are getting lots of complaints about the FLIST command. The command entry area has changed from 20 bytes down to 7 bytes. Yes, I know about PF11, but you used to be able to enter quite a few commands within the 20 bytes. Does anybody know if/how to change it back? Peter The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: z/VM 5.3 FLIST
Yes, I know about PF11, but there are a lot of 'little' commands that you can enter in the 20 bytes. It's just a little bit of productivity lost for no gain. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Feller, Paul Sent: December 13, 2007 16:36 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST Didn't know there was something other than FILELIST. Started looking at FLIST. Would the PF11 key help? It looks like the PF11 key increases the input area to end of line. Paul The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: z/VM 5.3 FLIST
That's very interesting, I've never used FLIST I've always used FILEL so I never saw the change. Rick Bourgeois Virtual Software Systems, Inc. 7715 Browns Bridge Rd Gainesville, GA 30506 [EMAIL PROTECTED] 770-781-3200
Re: z/VM 5.3 FLIST
Once upon a time, there was FLIST, but no FILELIST. Some of us old-schoolers still prefer it. Rick Bourgeois wrote: That's very interesting, I've never used FLIST I've always used FILEL so I never saw the change. Rick Bourgeois Virtual Software Systems, Inc. 7715 Browns Bridge Rd Gainesville, GA 30506 [EMAIL PROTECTED] 770-781-3200
Re: z/VM 5.3 FLIST
I also agree with you that there looks to be a lot of empty space on the screen. Moving a few fields to the right would increase the input area. Paul -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 13, 2007 3:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST Yes, I know about PF11, but there are a lot of 'little' commands that you can enter in the 20 bytes. It's just a little bit of productivity lost for no gain. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Feller, Paul Sent: December 13, 2007 16:36 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST Didn't know there was something other than FILELIST. Started looking at FLIST. Would the PF11 key help? It looks like the PF11 key increases the input area to end of line. Paul The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: z/VM 5.3 FLIST
FLIST used to be a part of CMS UTILITIES that was an extra charge feature until IBM decided to roll it into CMS. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Feller, Paul Sent: Thursday, December 13, 2007 3:56 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST I also agree with you that there looks to be a lot of empty space on the screen. Moving a few fields to the right would increase the input area. Paul -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 13, 2007 3:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST Yes, I know about PF11, but there are a lot of 'little' commands that you can enter in the 20 bytes. It's just a little bit of productivity lost for no gain. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Feller, Paul Sent: December 13, 2007 16:36 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST Didn't know there was something other than FILELIST. Started looking at FLIST. Would the PF11 key help? It looks like the PF11 key increases the input area to end of line. Paul The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: z/VM 5.3 FLIST
The great advantage of FILELIST is that you have the full power of XEDIT to manage the list. I switched from FULIST to FILELIST with FILELIST's second release of (VM/SP Rel 2?) when one no longer had to press PF10 to get the commands executed Do users of FLIST never miss something like ALL /this/ /that/ followed by for example EXECUTE * COPY / = = X (OLDD 2007/12/13, Feller, Paul [EMAIL PROTECTED]: I also agree with you that there looks to be a lot of empty space on the screen. Moving a few fields to the right would increase the input area. Paul -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 13, 2007 3:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST Yes, I know about PF11, but there are a lot of 'little' commands that you can enter in the 20 bytes. It's just a little bit of productivity lost for no gain. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Feller, Paul Sent: December 13, 2007 16:36 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST Didn't know there was something other than FILELIST. Started looking at FLIST. Would the PF11 key help? It looks like the PF11 key increases the input area to end of line. Paul -- Kris Buelens, IBM Belgium, VM customer support
Re: z/VM 5.3 FLIST
Nope, never :-) What I like about FLIST is I can easily set up the PF keys the way I want (see FLIST $PROFILE). We have used this to give users customized things they can do. Including removing the ability to edit the files (ever have a user edit a listing to change the numbers on a report, rather than correct the input data and rerun the program?). I like the REFRESH PF key in FILELIST, but having been an FLIST user since about 1979, its a hard thing to switch to. Since PF2 is BROWSE in FLIST, I waste a lot of time in FILELIST refreshing the screen Ron On 12/13/07, Kris Buelens [EMAIL PROTECTED] wrote: The great advantage of FILELIST is that you have the full power of XEDIT to manage the list. I switched from FULIST to FILELIST with FILELIST's second release of (VM/SP Rel 2?) when one no longer had to press PF10 to get the commands executed Do users of FLIST never miss something like ALL /this/ /that/ followed by for example EXECUTE * COPY / = = X (OLDD
Re: z/VM 5.3 FLIST
You can do the same for FILELIST by creating your own profile and specifying it via DEFAULTS. Mine first invokes PROFFLST and then changes what I want changed. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Ron Schmiedge Sent: Thursday, December 13, 2007 2:19 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST Nope, never :-) What I like about FLIST is I can easily set up the PF keys the way I want (see FLIST $PROFILE). We have used this to give users customized things they can do. Including removing the ability to edit the files (ever have a user edit a listing to change the numbers on a report, rather than correct the input data and rerun the program?). I like the REFRESH PF key in FILELIST, but having been an FLIST user since about 1979, its a hard thing to switch to. Since PF2 is BROWSE in FLIST, I waste a lot of time in FILELIST refreshing the screen Ron On 12/13/07, Kris Buelens [EMAIL PROTECTED] wrote: The great advantage of FILELIST is that you have the full power of XEDIT to manage the list. I switched from FULIST to FILELIST with FILELIST's second release of (VM/SP Rel 2?) when one no longer had to press PF10 to get the commands executed Do users of FLIST never miss something like ALL /this/ /that/ followed by for example EXECUTE * COPY / = = X (OLDD
Re: z/VM 5.3 FLIST
My favorite FLIST function is entering a bunch of commands and then hitting PF3 to exit FLIST and have the commands run.
Re: z/VM 5.3 FLIST
Create the 2 files shown below, then use FL instead of FILEIST. Feel fre e to change the names to suit your taste. FL EXEC --- /* */ arg data push 'set pf2 before macro execute cursor exec b' 'FILELIST' data B EXEC --- /* */ arg data 'browse' data Brian Nielsen On Thu, 13 Dec 2007 16:19:02 -0600, Ron Schmiedge [EMAIL PROTECTED] wrote: Nope, never :-) What I like about FLIST is I can easily set up the PF keys the way I want (see FLIST $PROFILE). We have used this to give users customized things they can do. Including removing the ability to edit the files (ever have a user edit a listing to change the numbers on a report, rather than correct the input data and rerun the program?). I like the REFRESH PF key in FILELIST, but having been an FLIST user since about 1979, its a hard thing to switch to. Since PF2 is BROWSE in FLIST, I waste a lot of time in FILELIST refreshing the screen Ron On 12/13/07, Kris Buelens [EMAIL PROTECTED] wrote: The great advantage of FILELIST is that you have the full power of XEDIT to manage the list. I switched from FULIST to FILELIST with FILELIST's second release of (VM/SP Rel 2?) when one no longer had to press PF10 to get the commands executed Do users of FLIST never miss something like ALL /this/ /that/ followed by for example EXECUTE * COPY / = = X (OLDD =
Re: z/VM 5.3 FLIST
Or just use this as your FILELIST profile: /* */ 'MACRO PROFFLST' 'set pf2 before macro execute cursor BROWSE' (The below was QAD and didn't need the B EXEC.) Brian Nielsen On Thu, 13 Dec 2007 16:37:29 -0600, Brian Nielsen [EMAIL PROTECTED] wrote: Create the 2 files shown below, then use FL instead of FILEIST. Feel free to change the names to suit your taste. FL EXEC --- /* */ arg data push 'set pf2 before macro execute cursor exec b' 'FILELIST' data B EXEC --- /* */ arg data 'browse' data Brian Nielsen On Thu, 13 Dec 2007 16:19:02 -0600, Ron Schmiedge [EMAIL PROTECTED] wrote: Nope, never :-) What I like about FLIST is I can easily set up the PF keys the way I want (see FLIST $PROFILE). We have used this to give users customized things they can do. Including removing the ability to edit the files (ever have a user edit a listing to change the numbers on a report, rather than correct the input data and rerun the program?). I like the REFRESH PF key in FILELIST, but having been an FLIST user since about 1979, its a hard thing to switch to. Since PF2 is BROWSE in FLIST, I waste a lot of time in FILELIST refreshing the screen Ron On 12/13/07, Kris Buelens [EMAIL PROTECTED] wrote: The great advantage of FILELIST is that you have the full power of XEDIT to manage the list. I switched from FULIST to FILELIST with FILELIST's second release of (VM/SP Rel 2?) when one no longer had to press PF10 to get the commands executed Do users of FLIST never miss something like ALL /this/ /that/ followed by for example EXECUTE * COPY / = = X (OLDD =
Re: z/VM 5.3 FLIST
Cool! Thanks Brian. I guess I would still need to pull PROFFLST SXEDIT apart and figure out how to change the description (still says REFRESH)... 'execute cursor browse' works too without a B exec. I use the synonym command to make BROWSE shorter when I have to type... On 12/13/07, Brian Nielsen [EMAIL PROTECTED] wrote: Create the 2 files shown below, then use FL instead of FILEIST. Feel fre e to change the names to suit your taste. FL EXEC --- /* */ arg data push 'set pf2 before macro execute cursor exec b' 'FILELIST' data B EXEC --- /* */ arg data 'browse' data Brian Nielsen On Thu, 13 Dec 2007 16:19:02 -0600, Ron Schmiedge [EMAIL PROTECTED] wrote: Nope, never :-) What I like about FLIST is I can easily set up the PF keys the way I want (see FLIST $PROFILE). We have used this to give users customized things they can do. Including removing the ability to edit the files (ever have a user edit a listing to change the numbers on a report, rather than correct the input data and rerun the program?). I like the REFRESH PF key in FILELIST, but having been an FLIST user since about 1979, its a hard thing to switch to. Since PF2 is BROWSE in FLIST, I waste a lot of time in FILELIST refreshing the screen Ron On 12/13/07, Kris Buelens [EMAIL PROTECTED] wrote: The great advantage of FILELIST is that you have the full power of XEDIT to manage the list. I switched from FULIST to FILELIST with FILELIST's second release of (VM/SP Rel 2?) when one no longer had to press PF10 to get the commands executed Do users of FLIST never miss something like ALL /this/ /that/ followed by for example EXECUTE * COPY / = = X (OLDD =
Re: z/VM 5.3 FLIST
You can use the following macro to set PF10 to BROWSE and even display it at the bottom of the screen. I used PF10 just because it was available. This macro is based on the example shown in the appendix of the CMS Command and Utilities Reference. /* MYFLIST XEDIT -- My FILELIST profile to add BROWSE on PF10 */ Parse Arg filelist_input 'MACRO PROFFLST' filelist_input /* Define PF key 10 to be BROWSE */ EXTRACT /RESERVED */ /* Get all reserved lines */ /* find the correct line to change by looking for 10= */ Do i = 1 To reserved.0 /* get each reserved line */ Parse Var reserved.i line color ext_high pss high text pf10_pos = POS(10=,text) /* find position of the change */ If pf10_pos = 0 Then Iterate /* change the line */ newtext = OVERLAY(BROWSE,text,pf10_pos+4,10) /* put new line on screen */ SET RESERVED line color ext_high pss high newtext Leave /* found desired line; leave loop */ End SET PF10 BEFORE MACRO EXECUTE CURSOR BROWSE /* set PF10 function */ Exit You can use this macro by doing FILELIST (PROFILE MYFLIST or you can SET DEFAULTS FILELIST PROFILE MYFLST. Doug Breneman z/VM Development IBM Endicott
Re: z/VM 5.3 FLIST
Thanks Doug. Must be Christmas! I don't want to sound ungrateful, but am I wrong in still thinking that entering this line in FLIST $PROFILE: *PFKEYS 10 BRW BROWSE the file on cursor line and then updating the last line to include '10 BRW' is a little simpler and easier? Ron On 12/13/07, Doug Breneman [EMAIL PROTECTED] wrote: You can use the following macro to set PF10 to BROWSE and even display it at the bottom of the screen. I used PF10 just because it was available. This macro is based on the example shown in the appendix of the CMS Command and Utilities Reference. /* MYFLIST XEDIT -- My FILELIST profile to add BROWSE on PF10 */ Parse Arg filelist_input 'MACRO PROFFLST' filelist_input /* Define PF key 10 to be BROWSE */ EXTRACT /RESERVED */ /* Get all reserved lines */ /* find the correct line to change by looking for 10= */ Do i = 1 To reserved.0 /* get each reserved line */ Parse Var reserved.i line color ext_high pss high text pf10_pos = POS(10=,text) /* find position of the change */ If pf10_pos = 0 Then Iterate /* change the line */ newtext = OVERLAY(BROWSE,text,pf10_pos+4,10) /* put new line on screen */ SET RESERVED line color ext_high pss high newtext Leave /* found desired line; leave loop */ End SET PF10 BEFORE MACRO EXECUTE CURSOR BROWSE /* set PF10 function */ Exit You can use this macro by doing FILELIST (PROFILE MYFLIST or you can SET DEFAULTS FILELIST PROFILE MYFLST. Doug Breneman z/VM Development IBM Endicott
Re: z/VM 5.3 FLIST
Hi Ron, You are correct; it is easy to update FLIST $PROFILE for a PF key. Someone on the list indicated that it would be useful if he could get a PF key for BROWSE in FILELIST. I appended to show how this could be done. I am not trying to convert anyone from FLIST to FILELIST. Both can get the job done. There are advantages to each. If you want fulldate, isodate, or shortdate, you can get it with FILELIST. If you want to move the command line to the top of the file, you can use CMDLINE TOP. FLIST can also do good things and the ease in changing the PF keys is just one of them. Doug Breneman z/VM Development IBM Endicott
Re: z/VM 5.3 FLIST
I could retire if a had a dollar, or certainly a euro, for every time I heard the religious argument you have the full power of XEDIT. I still have managed to keep a copy of the full strength FULIST and there are very few times when I use filelist vs fulist. Jim Kris Buelens wrote: The great advantage of FILELIST is that you have the full power of XEDIT to manage the list. I switched from FULIST to FILELIST with FILELIST's second release of (VM/SP Rel 2?) when one no longer had to press PF10 to get the commands executed Do users of FLIST never miss something like ALL /this/ /that/ followed by for example EXECUTE * COPY / = = X (OLDD 2007/12/13, Feller, Paul [EMAIL PROTECTED]: I also agree with you that there looks to be a lot of empty space on the screen. Moving a few fields to the right would increase the input area. Paul -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 13, 2007 3:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST Yes, I know about PF11, but there are a lot of 'little' commands that you can enter in the 20 bytes. It's just a little bit of productivity lost for no gain. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Feller, Paul Sent: December 13, 2007 16:36 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: z/VM 5.3 FLIST Didn't know there was something other than FILELIST. Started looking at FLIST. Would the PF11 key help? It looks like the PF11 key increases the input area to end of line. Paul -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
Re: z/VM 5.3 FLIST
On Thursday, 12/13/2007 at 05:55 EST, Doug Breneman/Endicott/[EMAIL PROTECTED]
wrote:
You can use the following macro to set PF10 to BROWSE and even display
it at
the bottom of the screen.
If I may, here's mine:
/* Get the displayed PF key settings */
'EXTRACT /RESERVED'
pfrow1_idx = find(reserved.1, '-5')
pfrow2_idx = find(reserved.1, '-4')
'EXTRACT /RESERVED *'
pfrow1 = reserved.pfrow1_idx
pfrow2 = reserved.pfrow2_idx
/* Now change F4 and F10 */
pfrow1 = overlay('Sort(Type)',pfrow1,index(pfrow1,'4=')+3)
pfrow2 = overlay('Browse',pfrow2,index(pfrow2,'10=')+4)
'COMMAND SET RESERVED' pfrow1
'COMMAND SET RESERVED' pfrow2
'COMMAND SET PF10 MACRO EXECUTE CURSOR BROWSE'
'COMMAND SET PF22 MACRO EXECUTE CURSOR BROWSE'
'COMMAND SET PF4 BEFORE STYPE'
'COMMAND SET PF16 BEFORE STYPE'
Alan Altmark
z/VM Development
IBM Endicott
