|
If you use the "LIST" line command on a line other than an "F" spec that has a file name, it'll prompt you for the file name (the prompt also has a place for library name which allows you to pull in information from a file that is NOT in your library list...) -----Original Message----- From: Chris Proctor [mailto:cproctor@gartsports.com] Sent: Wednesday, November 07, 2001 9:56 AM To: 'code400-l@midrange.com' Subject: RE: LIST command? This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] That's pretty cool, David. I did everything to my fields.lx and profile.lx that was recommended to you yesterday and it works pretty slick! I'm glad you clarified what the list could be used for though, because it can take up quite a few pages of display with the files we have!! ha ha. Thanks for the tip, David! Man, I'm learning a lot from watching the emails on this list! My thanks to everyone. I'm really starting to like the product. Chris -----Original Message----- From: David Schopp [mailto:dschopp@imt.net] Sent: Wednesday, November 07, 2001 8:53 AM To: code400-l@midrange.com Subject: RE: LIST command? Chris - LIST is part of the Extras.Lx macro. You must have EXTRAS ON to use LIST. The way it works, is this: On an 'F' spec, key LIST in the SEU line - you know, the line numbers on the far left? Then press <ENTER>. You'll get a display-only list of fields associated with the file name. You can also do this by placing your cursor on the appropriate 'F' spec, then selecting menu Extras | Fields | Extract Fields. (Notice the "shortcut" of LIST?) Note that the library list is used to get the field list. Thus, if you've got two different file layouts, you'll want to make sure your library list is set up correctly. Also, if the file isn't found, the macro returns an error that you'll be able to view by selecting menu Windows | Macro Log. Once you've retrieved a list of fields, you can double-click on a field, then right-click and select Filter Selection to view everywhere that field is referenced. One other thing - it'll retrieve all record formats and fields. Thus, this works for display files and printer files as well as data files. Dave > -----Original Message----- > Hi all, > > I noticed a question yesterday regarding the LIST command. I > never saw an > answer to it, but it really sparked my interest. I never > knew it existed. > Being a developer, obviously having the ability to display > record layouts > while coding would be an awesome advantage. I looked up LIST > in the help > and found a little info on it, but I could get it to work. I > just copied > and example: > "CODESRV LIST *FIRST MYLIB/MYFILE RCDNAME(MYREC) FLDNAME(*)" > Changed the parms to be a valid file for me, but when I pressed enter > nothing happened. Can someone please explain a little more > to me how I can > use this? Thanks so much for the help! > _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.