|
Using the *PRINT approach can, as you found, work for specific cases and for extended periods of time. But be aware that *PRINT output can change based upon the National Language Version (NLV) you're using, can change due to a PTF or release upgrade where information content may have changed (add/remove), and the like. When a program is accessing system level information, formal program interfaces (such as APIs and outfiles) should be used so as to maximize the likelihood that the program won't need to be maintained as the system it's running on changes. Bruce "James W. Kilgore" <email@James-W-Kil To: midrange-l@midrange.com gore.com> cc: Sent by: Subject: Re: Retrieve Job Schedule Entry values midrange-l-admin@m idrange.com 09/04/2002 09:59 AM Please respond to midrange-l We did it the old fashioned way: WRKJOBSCDE to *PRINT then CPYSPLF to a data base file. Works OK for our purposes. Al Barsa wrote: > > The TAA Tool CVTJOBSCDE will do what you want. > > Al > > Al Barsa, Jr. > Barsa Consulting Group, LLC > > 400>390 > > 914-251-1234 > 914-251-9406 fax > > http://www.barsaconsulting.com > http://www.taatool.com > > Dan Rasch > <drasch@mail.win.o To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> > rg> cc: > Sent by: Subject: Retrieve Job Schedule Entry values > midrange-l-admin@m > idrange.com > > 09/03/2002 12:01 > PM > Please respond to > midrange-l > > It there a method (short of parsing a panel) to retrieve the job schedule > entry values (specifically the) into variable(s)? > > Dan Rasch - because if the human species concentrated on the really > important things in life, there would be a shortage of fishing poles! > IBM Certified twice....... but still a couple PTFs away from Nirvana. > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-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.