RE: Belt-and-suspenders on *SRVPGM

["Christen, Duane" <Duane.Christen@xxxxxxxxxx>]

James;

I should restate this: "this library is in no applications library list but the SERVICE binding directory is."

The SERVICE binding directory is available to all applications at compile time.

A binding directory is useless at run time.

Duane Christen
  


--

 	 	 	 	
 	 	Duane Christen
Senior Software Engineer
(319) 790-7162
Duane.Christen@xxxxxxxxxx
	 	
Visit PAETEC.COM	  	
 	 	

-----Original Message-----
From: Christen, Duane 
Sent: Thursday, December 17, 2009 2:05 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Belt-and-suspenders on *SRVPGM

James;

Can't have both but, if you hard code the library name in the CRTPGM or in the binding directory the service program will always be found (assuming that the SP still exists in the specified library) even if the library is not in the library list. We have a SERVICE library in which HTTPAPIR4 and many other non-application specific service programs reside, this library is in no applications library list but the SERVICE binding directory is. It has the library SERVICE hard coded for all entries. This works very well for us.

Duane Christen  


--

 	 	 	 	
 	 	Duane Christen
Senior Software Engineer
(319) 790-7162
Duane.Christen@xxxxxxxxxx
	 	
Visit PAETEC.COM	  	
 	 	

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Thursday, December 17, 2009 1:29 PM
To: Midrange Systems Technical Discussion
Subject: Belt-and-suspenders on *SRVPGM

Is there a way to bind to a service program, such that it will look for it BOTH in the *LIBL AND in a specific library?

We have a situation involving a trigger that recently started using a service program (HTTPAPIR4, if anybody's interested), and we've had issues with certain jobs not finding it because it was bound in *LIBL, and no library containing it was in the *LIBL. I've changed it, but I wouldn't mind a belt-and-suspenders approach here.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.