Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Inventory\s+client\s+file\s+Expiration\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Inventory\s+client\s+file\s+Expiration\s*$/: 4 ]

Total 4 documents matching your query.

1. Inventory client file Expiration (score: 1): Author: "Peter Hadikin (HDIP9235)" <HDIP9235 AT BCITVM.BCIT.BC DOT CA>; Date: Thu, 15 Dec 1994 10:51:13 PST; Our VM Adsm server performs Inventory client file expiration processing roughly every 75 to 100 minutes. During the time it is running it uses 35-45% of our CPU resources. It is impacting our on-line; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1994-12/msg00090.html (11,069 bytes)
2. Inventory client file Expiration (score: 1): Author: Jim Smith <spikes AT VNET.IBM DOT COM>; Date: Thu, 15 Dec 1994 12:15:29 PST; The ExpInterval option (dsmserv.opt) was added at V1 R1 L0.5 of the VM server. This controls the time (in hours) between the expiration processes. You can also set this value to 0 and manually kick-o; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1994-12/msg00091.html (10,506 bytes)
3. Inventory client file Expiration (score: 1): Author: "Joanne T. Nguyen" <jtn AT VNET.IBM DOT COM>; Date: Thu, 15 Dec 1994 12:13:07 PST; On the OS/2 ADSM server, you can specify in the DSMSERV.OPT: EXPINterval hours where hours is the number of hours between automatic inventory expiration runs. Minimum value is 0, no automatic expira; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1994-12/msg00092.html (11,109 bytes)
4. Re: Inventory client file Expiration (score: 1): Author: Bill Colwell <BColwell AT CCLINK.DRAPER DOT COM>; Date: Thu, 15 Dec 1994 21:19:04 GMT; The ADSM install should have put a file somewhere which documents all the enhancements to the mainframe servers since GA. On the MVS server it is member ANR1111 of 'SYS1.SAMPLIB'. I don't it is calle; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1994-12/msg00094.html (11,833 bytes)

Current List: 1 - 4
Page: [1]