Hi Francois,
FM> As he said "the letter X is reserved for file request
FM> capability,...." how can I make NLMAINT to accept the
FM> new flags X2C and X2S.
You would have to use the FLAGS or UFLAGS files to allow them to be included,
however the person that processes the segment you output must also be
configured to process those flags otherwise your segment will be rejected.
The only flags that YOU can "create" are U flags for the USER defined ones,
however please note that anyone above you in the nodelist generation chain
must also be configured to allow them to be processed. The only valid values
you can include in the non-U section are flags approved by your ZC/the IC.
Note: Flags you define in the UFLAGS file do not need the U prefx in that
file, that is automatically added in front of the FIRST User flag by NLMAINT
when it outputs a new nodelist segment.
FM> I saw in the nodelist that those flags are always put
FM> _before_ the ",U," flags.
That is because they are not USER flags and can only be approved for use by
your ZC, which means that if NLMAINT does not currently allow them to be
included, you need to define them in your FLAGS file.
FM> P.S. I would be interested about what flags I have to
FM> put in my FLAGS.TXT and UFLAGS.TXT files. I guess I
FM> made many mistakes, as I put in my flags.txt for example those flags :
FM> ALLFIX,FID2INT,FIDS,INTIREX,MI,SEAT,V34+ (one per line of course).
This would only work if your ZC had approved the use of these flags and anyone
in the nodelist generation chain above you had their segment compiler
configured in a similar manner.
FM> and in my UFLAGS.TXT I have :
FM> 3COMX2C,3COMX2S,EMA,EVY,FAX,IBN,IFC,IFT,ITN,IVM,IP,IMI,I
FM> E,ITX,IUC,IEM,PN,RDN,SDN,SDS,TTf,TUF,V90C,V90S,V110H,V110L,Z19,
Similar with these. For example, for Region 57 in Zone 3 I am not using a
FLAGS file, however my UFLAGS file is -
==================================================================
IBN
IFC
ITN
IVM
IP
IMI
ISE
ITX
IUC
IEM
==================================================================
and this seems to work fine.
I hope some of this helps...............pk.
--- Maximus/2 3.01
120
* Origin: Another Good Point About OS/2 (3:772/1.10)
|