.psect topmem ,d,rw,gbl,ovr,rel .name utl .name err ; ; to use with RMSRES, use the following root and factor ; ; .root rm-rmsrot,utilty,error,topmem ;rm: .fctr a-b-c-d-e-f-errdvr-mem-sub ; ; to use without RMSRES, use the following root and factor .root rm,utilty,error,topmem rm: .fctr a-b-c-d-e-f-errdvr-mem-sub-rms a: .fctr k11pak b: .fctr k11dat c: .fctr k11rms d: .fctr k11m41 e: .fctr k11cmd f: .fctr k11lcl set: .fctr k11stt show: .fctr k11sho connec: .fctr k11con help: .fctr k11hlp server: .fctr k11ser utilty: .fctr utl-*(set,show,server,connec,help) errdvr: .fctr k11err error: .fctr err-*(er1,er2,er3,direrr,hl,copy,csisys) copy: .fctr k11cpy er1: .fctr k11er1 er2: .fctr k11er2 er3: .fctr k11er3 direrr: .fctr k11der sub: .fctr k11sub pk: .fctr k11pk hl: .fctr k11dfh ; The inclusion of CSI1,CSI2 and .PARSE is due to the fact that ; I use them to extract the filename.type from the RMS11 expanded ; filename string. This is because RMS always returns the complete ; name and does not have a place to store the filename.type anywhere ; It is quite sensible to put them in overlays. csi1: .fctr lb:[1,1]syslib.olb/lb:.csi1 csi2: .fctr lb:[1,1]syslib.olb/lb:.csi2 fparse: .fctr lb:[1,1]syslib.olb/lb:parse:parsdi:parsdv:parsfn-pars1 pars1: .fctr lb:[1,1]syslib.olb/lb:dirfnd:ascppn:ascr50:darith csisys: .fctr *(csi1,csi2,fparse) ; Get some memory please mem: .fctr lb:[1,1]VMLIB/lb:inidm:extsk ; to link with RMSRES, include the @lb:[1,1]RMSRLX ; ;@lb:[1,1]rmsrlx rms: .fctr lb:[1,1]rmslib/lb .end