|
midrange.com
Chris/Mark,
I also us the method Mark does of executing a macro. I have also gone a
step further and added a menu option to set my library list. I do that by
adding the following lines to my profile.lx file:
'set actionbar.~Library_Lists.~Starr macro mymacros/starr'
'set actionbar.~Library_Lists.~MRL macro mymacros/mrl'
'set actionbar.~Library_Lists.~Crew_Calling macro mymacros/crew'
I also noticed that my macro for changing the library list is different from
Mark's but I'm not sure of what the difference is. Mine is
say "Starr library list set"
codesrv exec OS400S "chglibl libl(starrobj starr starrsrc tstdata73)"
By the way, for anyone interested, their are a couple of Code/400
tutorial/labs available at
http://www-4.ibm.com/software/ad/wdt400/course_downloads.html The one at
the bottom of the page (course code 37LF) is where I learned about how to
create macros along with some other useful things.
Scott Mildenberger
> -----Original Message-----
> From: MWalter@hanoverwire.com [mailto:MWalter@hanoverwire.com]
> Sent: Tuesday, September 25, 2001 1:06 PM
> To: code400-l@midrange.com
> Subject: RE: Library lists confusion????????
>
>
>
> Chris,
>
> This is an example of a simple macro used to change the user
> library list:
>
> /*---------------------------------------------------------------*/
> /* keystroke record and playback macro. Save to macros directory */
> /* execute using 'macro macroFilename.' */
> /*---------------------------------------------------------------*/
> "check"
> "PRIMITIVE INSERTCHAR 'chglibl libl(qtemp hwoei amamod
> amfliba pclib mwlib
> qgpl)'"
> "lxi CMD RUN"
>
> I created this macro with the macro record function.
> You must save the file in the x:\WDT400\macros directory and
> must have an
> extension of .lx. (where x is the drive where WDT400 is installed)
>
> Then you get to the Command Shell (F9). Be sure your AS/400
> server is the
> active server, press Esc and the cursor goes to the command
> line at the
> bottom. Key in "macro fileName" and press Enter. The macro
> should execute
> in the command shell.
>
> BTW, I don't even use a STRCODE session. The only thing I loose is
> prompting for CL. I'm on V4R5M1 of CODE. OS/400 Version V4R5M0.
>
>
>
>
> Good Luck
>
> Mark
>
>
> Mark Walter
> Sr. Programmer/Analyst
> Hanover Wire Cloth a div of CCX, Inc.
> mwalter@hanoverwire.com
> http://www.hanoverwire.com
> 717.637.3795 Ext.3040
>
>
>
> Chris Proctor
> <cproctor@gartspor To:
> "'code400-l@midrange.com'" <code400-l@midrange.com>
> ts.com> cc:
> Sent by: Subject:
> RE: Library lists confusion????????
> code400-l-admin@mi
> drange.com
>
>
> 09/25/01 02:42 PM
> Please respond to
> code400-l
>
>
>
>
>
>
> 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 ]
> Hi Mark,
>
> How does that work? I've never created a macro to run with
> code/400. Could
> you either send me an example or direct me where I might find
> the info? If
> I
> can't do it with a project (which I'd really prefer, IBM
> (hint, hint)) then
> I guess I'll have to do something else. I just don't want to have to
> bounce
> back and forth between AS/400 session and code/400. It seems
> like such a
> waste of time. I'm trying to get everyone else here to start using the
> tools, but they won't if there's a bunch of bouncing around
> required to do
> something as simple as changing a libl!! Is it just me? I'm
> working on 5
> different projects at the same time and this is a pain. ha ha. OK, I
> promise
> no more complaining (until the next time! ha ha)
>
> Thanks!
>
> Chris
>
> -----Original Message-----
> From: MWalter@hanoverwire.com [mailto:MWalter@hanoverwire.com]
> Sent: Tuesday, September 25, 2001 12:39 PM
> To: code400-l@midrange.com
> Subject: RE: Library lists confusion????????
>
>
>
> Chris,
>
> I am setting my library lists from the command shell. I have
> macros that
> set the libl to which ever environment I need. That method
> works ok for me.
>
>
> Thanks,
>
> Mark
>
>
> Mark Walter
> Sr. Programmer/Analyst
> Hanover Wire Cloth a div of CCX, Inc.
> mwalter@hanoverwire.com
> http://www.hanoverwire.com
> 717.637.3795 Ext.3040
>
>
>
> Chris Proctor
> <cproctor@gartspor To:
> "'code400-l@midrange.com'" <code400-l@midrange.com>
> ts.com> cc:
> Sent by: Subject: RE: Library
> lists
> confusion????????
> code400-l-admin@mi
> drange.com
>
>
> 09/25/01 02:29 PM
> Please respond to
> code400-l
>
>
>
>
>
>
> 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 ]
> Thanks for the reply, Darren. That brings up the question
> then of why do we
> even have library lists parms in the comm console? If it all
> had to be done
> from the AS/400 session then why bother? From the discussion last week
> someone from IBM said that they tried what I was doing and it
> worked. I was
> under the impression that STRCODE was not needed. What do you think?
>
> Chris
>
> -----Original Message-----
> From: darren@dekko.com [mailto:darren@dekko.com]
> Sent: Tuesday, September 25, 2001 12:29 PM
> To: code400-l@midrange.com
> Subject: Re: Library lists confusion????????
>
>
>
> Chris,
>
> What it sounds like you'd like to do is have the library list
> assigned for
> each member, or at least per project. Didn't you have this
> same issue when
> using SEU, library lists were something you had to keep track
> of there too.
> I know some change management programs, like Turnover which works with
> CODE, can manage library lists by project, but there is
> nothing prepackaged
> in OS/400 or CODE which will do this that I'm aware of. You
> might be able
> to do it with defaults on multiple auto-start servers, but
> that would be a
> pain, if possible, too I'd think.
>
> For simplicity you might try using a session with STRCODE
> command running.
> Your library list will be whatever that sessions libl is. And you can
> EDTLIBL from code on that session easily enough.
> _____________________________
> Darren Strong
>
>
>
>
>
>
> Chris Proctor
> <cproctor@gartspor To:
> "CODE400-L (E-mail)"
> ts.com> <CODE400-L@midrange.com>
> Sent by: cc:
> code400-l-admin@mi Fax to:
> drange.com Subject:
> Library lists
> confusion????????
>
>
> 09/25/2001 01:02
> PM
> Please respond to
> code400-l
>
>
>
>
>
>
> 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 ]
> Hi all,
>
> I'm still having problems understanding how the library lists get set
> within
> code/400. There was a discussion a couple of weeks back where
> someone said
> I
> could create a bunch of host names in the hosts file (with the same IP
> address), then go into the communications console, create the
> servers and
> define their library lists. I assumed that then I could
> create CPOs for
> different projects (each using a different servers with the associated
> libls) and I would have no problem verifying and compiling.
> WRONG!!!! ha
> ha. I constantly get file not found errors. And what adds
> even more to the
> frustration is that it changes from day to day.
>
> Would someone PLEEEEASSE help me understand how the libls
> work with Code
> Project and CODE/400? For instance, does the libl defined for
> the project
> carry over to code/400 when a source member is selected? Do I
> have to be
> signed on to the AS/400? What the #@$*&&#*%& am I doing wrong?!!
>
> Can you detect the frustration? ;-)
>
> Thanks,
>
> Chris Proctor
> Manager of Systems Integration
> Gart Sports
> Denver
> _______________________________________________
> 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.
> _______________________________________________
> 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.
> _______________________________________________
> 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.
