Black Box 4

home *** CD-ROM | disk | FTP | other *** search

/ Black Box 4 / BlackBox.cdr / bbs_opus / yms_200.arj / YMS_REF.DOC < prev next >

Wrap

Text File | 1991-07-29 | 121.3 KB | 3,539 lines

YY YY MM MM SSSSS YY YY MMM MMM SS YY YY MMMM MMMM SS YYYYYY MM MMMM MM SSSSS YY MM MM MM SS YY MM MM SS YY MM MM SSSSS Your Mail, Sir... v2.00 A state-of-the-art mail-checking utility for Opus-CBCS v1.1x Opus-CBCS v1.7x Maximus-CBCS v1.02 Released July 29th, 1991 Reference Guide (C) 1990,1991 by Angelo Besani, All rights reserved <[ AmnesiA ]> Gallarate, VA, Italy (2:331/101@FidoNet.Org) Documentation (C) 1990 by Alberto Morosi, All rights reserved Documentation (C) 1991 by Angelo Besani, All rights reserved <[ AmnesiA ]> Gallarate, VA, Italy (2:331/101@FidoNet.Org) ... open your soul to friends, ever ... TABLE OF CONTENTS ================= Page Section 1 - GENERAL INFORMATIONS............................3 1.1 HOW TO USE THIS DOCUMENTATION....................3 1.2 ACKNOWLEDGEMENTS.................................3 1.3 CREDITS..........................................3 1.4 SOFTWARE LICENSE.................................5 1.5 NO WARRANTY......................................5 1.6 HOW TO CONTACT THE AUTHOR........................5 Section 2 - CONTROL FILE ARGUMENTS..........................6 Section 3 - LANGUAGE FILE ARGUMENTS........................19 3.1 ESCAPE COMMANDS.................................19 3.2 OPUS/MAXIMUS EMBEDDED COMMANDS AND AVATAR COLOUR CODES TRANSLATE TABLES...................19 3.3 FORMAT SPECIFICATIONS FOR YMS_MAIL.F?? FILES....22 Section 4 - YMS LANGUAGE COMPILER..........................24 4.1 USAGE...........................................24 4.2 FATAL ERRORS....................................24 4.3 OTHER ERRORS....................................24 4.4 WARNING MESSAGES................................25 4.5 ERRORLEVELS.....................................26 Section 5 - YMS MAIL SEARCH MODULE.........................27 5.1 USAGE AND COMMAND LINE SWITCHES.................27 5.2 ERROR MESSAGES..................................29 5.3 WARNING MESSAGES................................29 5.4 LOGFILE MESSAGES................................29 5.5 ERRORLEVELS.....................................31 Section 6 - YMS ON-LINE SEARCH MODULE......................33 6.1 USAGE AND COMMAND LINE SWITCHES.................33 6.2 ERROR MESSAGES..................................34 6.3 WARNING MESSAGES................................35 6.4 LOGFILE MESSAGES................................35 6.5 ERRORLEVELS.....................................37 YMS v2.00 Reference Guide Page 1 Section 7 - THE MAIN PROGRAM...............................38 7.1 YMS COMPILE.....................................38 7.2 YMS UPDATE......................................38 7.3 YMS CTLCOMPILE..................................39 7.4 YMS AREAUPDATE..................................39 7.5 FATAL ERRORS....................................40 7.6 ERROR MESSAGES..................................41 7.7 WARNING MESSAGES................................42 7.8 LOGFILE MESSAGES................................45 7.9 ERRORLEVELS.....................................52 Section 8 - DISK STATUS ERRORS.............................56 Section 9 - YMS SUPPORT FILES..............................57 YMS v2.00 Reference Guide Page 2 Section 1 - GENERAL INFORMATIONS ================================ 1.1 HOW TO USE THIS DOCUMENTATION Writing these docs I took inspiration from the idea used by Alan Applegate in BinkleyTerm's manual. In the archive you have found two .DOC files, named YMS_USER.DOC and YMS_REF.DOC: the user's guide explains (or, well, tries to explain) how to correctly install YMS to fit your system; the reference guide provides a glossary of all the commands and statements involved in the operation of YMS, divided into sections and listed alphabetically. 1.2 ACKNOWLEDGEMENTS The following names are (C)opyrighted trademarks and/or result of the efforts of the people or companies named: A.V.A.T.A.R. - George A. Stanislav BinkleyTerm - Bit Bucket Software Co. DiskManager - Ontrack Computer Systems Inc. ECHOmail - Jeff Rush FidoNet - Tom Jennings & Fido Software FLAGS - Chris Irwin and Joaquim Homrighausen HST - US Robotics Inc. KramMail - Jaap Kramer Mailbase - Lincoln Dale Mailchek - Marc Ache` Matrix - Wynn Wagner III Maximus-CBCS - Scott Dudley MS-C Compiler 6.0 - Microsoft Corp. MS-DOS - " " MS-MASM 5.1 - " " MSGID - Jim Nutt Opus-CBCS - Wynn Wagner III, George A. Stanislav, Doug Boone PC-DOS - International Business Machines Corp. SpeedStore - Hexis Design V.32 - C.C.I.T.T. 1.3 CREDITS I guess we have to thank a very big lot of people, who have been, directly or indirectly, involved in inspiring, developing or testing the product: Tom Jennings for inventing FidoNet; Wynn Wagner for starting a new era in FidoNet, which began with Opus-CBCS v0.00; YMS v2.00 Reference Guide Page 3 George-Adam Stanislav for the further developement of the Opus project and the implementation of the AVT/0 standard; Vince Perriello for coordinating the last efforts made for Opus 1.10; Doug Boone, current Opus LCD, for the hours he spends for our fun; Tom Kashuba and Ulf Nilsson for the help they gave us during Opus Gamma ix and x cycle and for the Italian translation files; Marc Ache` (who is no longer in FidoNet, I guess...) for providing Mailchek for Opus 1.03, program that we used for a very long time; Lincoln Dale and Jaap Kramer for MailBase and KramMail, two other well-known mailcheckers; Microsoft Corporation for producing the C Compiler 6.0 and the Macro Assembler 5.1, without which power YMS wouldn't probably exist at all; The Beta-Team, for the precious help they gave us: Enrico Cima (2:331/201) for testing on his lightning-speed 386 with 320Megs ESDI disk; Luca Croci (2:331/108) for finding the time to read my DOCs (grrrrrrrr...RTFM!); Alberto Enna (2:335/12) for the hours he spent hacking his system's configuration trying to break some of YMS' features; Beppe Malinverni (2:331/104) for testing the product with DiskManager's large partitions; Alberto Pasquale (2:332/500) for his hints and suggestions that helped implementing LowLevel support for DOS 4.01; Bruno Grampa (2:331/105) for Maximus alpha testing and his precious advices; Vertigo (2:331/301) for Maximus and multiline testing; <[ AmnesiA ]> (2:331/101) for SpeedStore testing and for the tremendous AlphaTesting ;-). The Translators: Soren Ager (2:231/12) for DANSK; Peter Janssens (2:512/1) for DUTCH; Dieter Soltau (2:507/1) for DEUTSCH. Thank you very much indeed guys: we owe you much more than a beer! Without you YMS would have not been a real multilingual program! YMS v2.00 Reference Guide Page 4 1.4 SOFTWARE LICENSE YMS (Your Mail, Sir...) (C) 1990,1991 Angelo Besani, Gallarate, VA, Italy. ALL RIGHTS RESERVED. COMMERCIAL DISTRIBUTION AND/OR USE PROHIBITED WITHOUT WRITTEN PERMISSION OF THE AUTHOR. Non-Commercial distribution and/or use is permitted under the following terms: You may copy and distribute verbatim copies of YMS executables and complementary files, providing not to change them with any text or byte editor; provide unmodified copies of the documentation as provided with the program. You may charge a fee for transferring the copy, but no more than is necessary to cover your actual costs. Under no circumstances is YMS to be distributed on CD-rom's, PD-software libraries or anything similar. 1.5 NO WARRANTY Are you kidding? Keeping with the spirit of Opus-CBCS by WW3<tm>, YMS is provided completely free of charge, and therefore no warranty is also provided. Let's say that YMS is guaranteed for the space that will eat up on your disk. The entire risk as to quality and performance of YMS is with you. Should it cause any kind of damage to your hardware or software system configuration, you assume all the costs or the efforts to repair it. 1.6 HOW TO CONTACT THE AUTHOR You can easily contact me using FidoNet E-Mail. Please feel free to contact us for comments, impressions, hints or suggestions about the software and its documentation. Angelo Besani via Novara 12 I-21013 Gallarate VA ITALY (2:331/101@FidoNet.Org) Data phone # +39-331-772362 [HST/DS] YMS v2.00 Reference Guide Page 5 Section 2 - CONTROL FILE ARGUMENTS ================================== - Address <[zone:]net/node[@domain]> Your Network address. Do not specify any point, Zone is not mandatory and if not specified defaults to 1. If you want to operate in a DOMAIN-aware environment, you can specify a domain too. If you specify a domain, YMS works using 5D, so you will be able to use domain in MatrixForwards too. Example: ; Address 2:331/101@fidonet.org ; - AllUser <name> The name contained in the To: field of messages that have to be considered as BroadCast messages. Do not choose a very common name.... We use "**|ALL|**" instead of "All" so that we can create BroadCast messages just in case. On the contrary, if you have commented EnableToAll out, you will prefer to specify ; AllUser All ; so that every single message sent To: All will be shown as "BroadCast Message" to every user that searches his/her mail using YMS. Leaving AllUser commented out means that there will be NO BroadCast messages. If you like, you can have up to 16 AllUser lines. Example: ; AllUser **|ALL|** ; - AreaInclude <number[,...]> This statement specifies which areas YMS must process. You can specify every single area using "," as a separator, or define areas in a range using "-" as a separator. You can specify multiple AreaInclude lines, if you like. Valid area numbers are: For OPUS 1.1x: 0 to 254 For OPUS 1.7x: 0 to 2047 For MAXIMUS 1.02: 0 to 1295 Note for MAXIMUS users: since Maximus doesn't use area numbers but a 2-character 'name' (even these characters are normally digits), YMS assumes as area number the record each area is listed in the AREA.DAT file. So the first area in AREA.DAT is assumed to be area 0, the following one area 1 and so on. Examples: If you want to include areas 2, 5, 12, 13, 14, 15, 27 and 60 you can use ; AreaInclude 2,5,12,13,14,15,27,60 YMS v2.00 Reference Guide Page 6 ; but also ; AreaInclude 2,5,12-15,27,30 ; - BbsDirectory <Pathname> For OPUS 1.1x, the path where the SYSTEM??.DAT and USER.IDX files are stored. For OPUS 1.7x, the path where the SYSMSG.DAT, NUMBER.MDX and USER.DAT files are stored. For Maximus 1.02 the path where you have the AREA.DAT and USER.BBS files. If these files are in different paths or (Maximus only) have different names than AREA.DAT or USER.BBS, use SystemDirectory and UserlistDirectory. See below. This entry is MANDATORY and you must specify it even if it is your current DOS directory, unless you use both SystemDirectory and UserlistDirectory. Example: ; BbsDirectory D:\Opus\ ; - Bbs <bbs_type> The BBS software you are operating. Currently YMS supports OPUS 1.1x, OPUS 1.7x and MAXIMUS 1.02. Use Bbs Opus11x for OPUS 1.10 to OPUS 1.14, Bbs Opus17x for OPUS 1.70 and Bbs Max102 for Maximus 1.02. Example: ; Bbs Opus17x ; - DomainGate <domain> <address_of_domaingate> Since lots of people are still using domain-unaware mail processors, it is necessary that YMS takes care of domaingating. This means that YMS has to route a message destinated to another domain to a particular node of the current domain acting as a domain gate. With this statement you can define up to 16 domaingates. Example: ; DomainGate SIGNet 2:2/527 ; - EnableToAll <name> This is the list of the persons that are allowed to create messages marked as BroadCast. Typically they will be the SysOp and the Co-SysOps. If this option is commented out it will default to "any user". It means that every single user will generate BroadCast messages if they are addressed to the name specified in AllUser (see above). Example: ; EnableToAll Angelo Besani YMS v2.00 Reference Guide Page 7 ; - ExcludeMr <name> - ExcludeMrs <name> - ExcludeMiss <name> This function tells YMS not to include one ore more users in the message waiting base. There is no difference between the three arguments: they were implemented just for fun. You can specify multiple lines of this statement, followed by the user's name, placed as it is in your user file. Example: ; ExcludeMr Giampaolo Muraro ExcludeMrs Feliciana Antolini ExcludeMiss Mara Bruni ; - ForcedFwdAreaInclude Virtually (and sintactically) the same as MatrixFwdAreaInclude, but these areas cannot be excluded by the IEP (see below). This can be useful if one of your point/nodes wants to receive forward of messages in areas he is linked to. Example: ; ForcedFwdAreaInclude ; - IEPAreasBbs <filename> - IEPEchoCtl <filename> - IEPSysMsgDat (OPUS 1.70 only) Where you keep your echomail forward informations. Needed by YMS if you want to use the IEP. YMS can read ECHO.CTL format files (using IEPEchoCtl <filename>) or AREAS.BBS format files (using IEPAreasBbs <filename>) or internal OPUS 1.70 informations (using IEPSysMsgDat). You can obviously use more than one format at the same time. Example: ; IEPEchoCtl C:\Opus\Echo.Ctl ; - IEPNotFwdedMsgs <Option> Where <Option> can be either Show, Hide or Mark. This verb indicates how to handle messages which hasn't been forwarded because the IEP has excluded the area. You can have: Show: (default option). Show them when the user logs in. Hide: Simply don't show these message to the user. Mark: Mark these message as "received", as they have been really read by the user. Example: ; IEPNotFwdedMsgs Mark ; YMS v2.00 Reference Guide Page 8 - IncludeAlias Opus 1.70 only. Include aliases in the YMS userlist so you can show not only the mail waiting to the user's name, but to his/her alias too. See also TaskSearchShowAlias and TaskOnlineShowAlias below. Example: ; IncludeAlias ; - IncludeMr <name> - IncludeMrs <name> - IncludeMiss <name> Include <name> in the YMS message waiting base. There is no difference between the three arguments and you can specify multiple lines of this statement. You can obtain the same result adding <name> to your userlist file. When this cannot be done, since it's useless or for security reasons, you can use this verb. Example: ; IncludeMr Jaap Kramer ; - IncludeReceived. Tells YMS to include received messages in the message waiting base, when performing a COMPILE. Example: ; IncludeReceived ; - Log <PathName> YMS produces an Opus/Maximus-style logfile. The pathname stated here will generate the log of the COMPILE option, which must be run generally once a day, and, if you have a multitasker, in ONE TASK ONLY. Leaving it blank or commented will force YMS not to generate a COMPILE Logfile. Example: ; Log D:\Opus\Opus.Log ; - LogLevel <number> Selects between one of the 5 different Opus-like log levels. YMS uses the following symbols for convention and compatibility with Opus-CBCS: ! = Error Messages * = NetMail Forwarding Messages # = Trace Activity and Warning Messages + = Normal Operations : = Unimportant Messages The different LogLevels include the following symbols: LogLevel 1 = ! Loglevel 2 = ! * YMS v2.00 Reference Guide Page 9 Loglevel 3 = ! * # Loglevel 4 = ! * # + Loglevel 5 = ! * # + : If commented, LogLevel will default to 5. Example: ; LogLevel 3 ; - LowLevel. Enables lowlevel reading routines during COMPILE and UPDATE functions. This function is definitely VERY fast and absolutely NOT dangerous, as it does not perform any kind of write. It has been fully tested under DOS 3.20, 3.30, 3.31 and 4.01, SpeedStore and DiskManager with partitions of ANY size. In case that lowlevel would fail, YMS error detection logic would immediately switch to HIGH level and continue the COMPILE or UPDATE process, without hanging but simply issueing a warning message in the logfile. LowLevel will not work in a Local Area Network or on JOINed drives. Example: ; LowLevel ; - MatrixForward <[zone:]net/node[.point][@domain] name> You can have YMS forwarding to nodes or points local messages addressed to them, or you can have it remapping wrongly addressed netmail messages. YMS will forward messages for people listed here to the addresses specified, so that you can send to another address mail originally addressed to your node. This function is both Point and Zone aware and if YMS is working in 5D (see description of 'Address' above) you can specify a domain too. Examples: ; MatrixForward 2:331/101.3 Luigi Callegari MatrixForward 2:331/101.6 Paolo Zibetti MatrixForward 2:331/104 Beppe Malinverni MatrixForward 2:331/105 Bruno Grampa MatrixForward 2:331/109@fidonet.org Alberto Bassani ; - MatrixFwdAreaInclude The list of areas to be processed with the MatrixForward logic. They can be LOCAL or ECHO areas, and the NETMAIL area can be included too, if you want YMS to forward netmail messages to different addresses. The separators work in the same way as for AreaInclude. Note that (differently from YMS 1.00), these areas are valid ONLY for the MatrixForward lines (see below) which FOLLOW this MatrixFwdAreaInclude, and a new MatrixFwdAreaInclude cancels the YMS v2.00 Reference Guide Page 10 previous one. To cancel ALL areas, use MatrixFwdAreaInclude without listed areas, or MatrixFwdAreaInclude None. Example: ; MatrixFwdAreaInclude 1-74 ; - MatrixFwdPublic - MatrixFwdPrivate You can choose to forward only private messages, only public messages or both. The Netmail area is not affected by this logic: if the Matrix area is included in MatrixFwdAreaInclude the forwarding will work on ANY message, regardless of its public/private privilege. Netmail messages generated by this function of YMS will contain: FMPT/TOPT line (if necessary) INTL line (if necessary) MSGID line FLAGS/PID informations are stripped "Forwarded...." line Message Text In ECHOmail messages "* Origin" is changed to "MsgOrigin" to avoid letting any mail processor run into confusion; SEEN-BY and ^APATH are stripped. Example: ; ; MatrixFwdPublic MatrixFwdPrivate ; - NetMail <pathname> If you did not include the Matrix area using AreaInclude, but you have MatrixFwdAreaInclude and MatrixForward enabled, place your NetMail area path here, and YMS will work and forward messages via NetMail. Note that if you use this verb, YMS will consider your MATRIX area the area which has BOTH the MATRIX flag AND this path. Example: ; NetMail d:\opus\msg\fidomail\ ; - NoAnonAreas If not commented, YMS will ignore broadcast messages in Anonimous areas, preventing users not allowed to enter broadcast messages from using an ALIAS to write such messages. Example: ; NoAnonAreas ; - Notify "Name1" to "Name2" Note that the quotes and the 'to' keyword are MANDATORY. Show to "Name2" the mail waiting for "Name1". "Name2" MUST be in the YMS userlist, while "Name1" can be or can be not. YMS v2.00 Reference Guide Page 11 When searching for "Name2" mail, the messages to "Name1" will be also shown, but will have an attribute of ALIASED. See the description about YMS_MAIL files. Example: ; Notify "Sysop" to "Angelo Besani" ; - NoVideoWrap If not commented, YMS will truncate all log lines sent to the screen to 75 characters, ending them with '...'. Disk log lines will be left unchanged. Example: ; NoVideoWrap ; - PointNet <Net> Your Point Network, if you have any. It is necessary for the particular way YMS processes netmail messages and only if you include your matrix area for forwarding. Example: ; PointNet 21101 ; - RamDisk <pathname> The path used by YMS to store its temporary files. If you have a RamDisk, of course let it point there. If you do not have one, a normal DOS path will work. Example: ; RamDisk L:\ ; - RecordsPerUser <number> This defines the maximum number of messages that YMS can remember for each user. The maximum is 8000. Consider that increasing this number will have YMS eating up more memory and more disk space, so choose a number that fits your current users' needs. Exceeding this limit will generate a message in the logfile and the messages for that user, beginning from [n+1] will not be recorded in the base. No other problem occurs. Example: ; RecordsPerUser 128 ; - SentAsReceived. Tells YMS to consider Sent messages as they were already Received. Example: ; SentAsReceived ; YMS v2.00 Reference Guide Page 12 - SystemDirectory <Path/Filename> If you can't use BbsDirectory (see 'BbsDirectory' above), you must use SystemDirectory and UserListDirectory. For OPUS 1.1x: the path where the SYSTEM??.DAT files are stored. For OPUS 1.7x: the path where the SYSMGS.DAT and the NUMBER.MDX files are stored. For Maximus 1.02: the actual FILENAME (not the pathname only!!) for your area list. Example: ; SystemDirectory C:\MAX\MAXAREAS.DAT ; - Task <number> With this statement you tell YMS how to behave in each of you system's tasks. If you are not using different tasks, say here: ; Task 0 ; You can have up to 256 tasks (I guess they are enough!) This statement is in DECIMAL numbers. Example: ; Task 1 ; - TaskAllNotToEnabled If not commented, YMS will NOT show broadcast messages to people listed in the EnableToAll list. Example: ; TaskAllNotToEnabled ; - TaskLastUser <[drive:pathname\]filename.ext> Tells YMS which lastuser file to read for task one. If you are not using tasks, the file will be [drive:\path\]lastus00.dat or [drive:\path\]lastuser.bbs if you are using Maximus. Remember that if you have more than 9 tasks, you will have to use hexadecimal suffixes for your LASTUS??.DAT or .BBS file (i.e. Task 10 will have LASTUS0A.DAT, task 99 will have LASTUS63.DAT) If left commented out, it will default to [BbsDirectory\Lastus(task#).DAT] for OPUS systems or [BbsDirectory\Lastus(task#).BBS] for Maximus systems so there are good chances that YMS will look for the right lastuser file. Example: ; TaskLastUser D:\opus\lastus01.dat ; - TaskOnlineChangeSect OPUS 1.70 only. If the user has messages in a section he/she isn't in, let YMS_OS add the required section to the user's ones to allow him to read his/her message. If commented, the message isn't shown to the user. Example: YMS v2.00 Reference Guide Page 13 ; TaskOnlineChangeSect ; - TaskOnlineConflict <option> Same as TaskSearchConflict, but for YMS_OS. <Option> can be either Notify, or Wait or Ignore. See TaskSearchConflict (below) for more details. Example: ; TaskOnlineConflict Notify ; - TaskOnlineLog <filename> Same as TaskSearchLog, but for YMS_OS. See TaskSearchLog (below) for more details. Example: ; TaskOnlineLog D:\Opus\Opus.log ; - TaskOnlineLogLevel <number> Same as TaskSearchLogLevel, but for YMS_OS. See TaskSearchLogLevel (below) for more details. Example: ; TaskOnlineLogLevel 4 ; - TaskOnlineWaitTime <number> Same as TaskSearchWaitTime but for YMS_OS. See TaskSearchWaitTime (below) for more details. Example: ; TaskOnlineWaitTime 5 ; - TaskOutFile <[drive:\pathname\]filename> This is the file shown to the user after a mail search. It contains either the list of the messages, either other messages, if he has no mail waiting or if there is a serach conflict. You must, of course, specify different filenames for different tasks. No extension is required, and is specified will be ignored. It defaults to .BBS and cannot be changed (Opus/Maximus cannot display anything else than .BBS and .GBS files!) If commented, it will default to {BbsDirectory}Mail_{task#} (with extension .BBS). Example: ; TaskOutFile l:\Opus\mail ; - TaskSearchConflict <option> There may be YMS_MS.EXE (the mail-search module) accessing the base while another YMS function is being performed in another task YMS v2.00 Reference Guide Page 14 In this case, YMS can manage the conflict. <Option> can be: Notify: With this option you will see YMS notifying the conflict to the user. Ignore: The mail-search module will simply Ignore the conflict and read the message waiting base regardless of other tasks. Wait: The mail-search module will wait for the other task(s) to finish their UPDATE function before performing mail search. Example: ; TaskSearchConflict Notify ; - TaskSearchLog <[drive:pathname\]filename.ext> If you like, you can have YMS generating a Search Logfile too. The main reason why UpdateLog and SearchLog can be configured separately is because earlier versions of Opus (up to 1.12) did not allow writing to Opus' logfile from a ^OC embedded command. Opus 1.13 flushes the log each time writes to it, and therefore you can put everything in the same file, if you like. Leaving it blank will cause YMS to default to the log file specified for YMS COMPILE; if commented will force YMS not to generate a Search LogFile. Example: ; TaskSearchLog D:\Opus\Opus.Log ; - TaskSearchLogLevel <number> See TaskUpdateLogLevel. Example: ; TaskSearchLogLevel 5 ; - TaskSearchSectOnly For OPUS 1.70 only. If not commented, YMS_MS will search for mail ONLY in the section(s) the user is in. If commented, YMS_MS will search in all areas. Example: ; TaskSearchSectOnly ; - TaskSearchShowAlias Opus 1.70 only. If you did include users' aliases in the base (see IncludeAlias above), you can now selectively choose either to show to your users (by uncommenting this verb) or not. Example: ; TaskSearchShowAlias ; - TaskSearchWaitTime <number> If not commented, TaskUpdateWaitTime will specify how much time YMS v2.00 Reference Guide Page 15 YMS has to wait (in case of conflict) before taking the action specified with TaskSearchConflict. Example: ; TaskSearchWaitTime 5 ; - TaskShowReceived If you did include received messages in the base (see above) you can now selectively choose either to show them to your users or not, depending on the task number. In fact, this option has been concepted much more for use by SysOps than by users (i.e. you may want to see how many RECV messages you have there for you, but do not want the users to read several pages of message listings). Example: ; TaskShowReceived ; - TaskUpdateConflict <option> In multitasking environments it may happen that YMS is invoked at the same time in two different tasks. In this case, you can choose how to let it manage the conflict. <Option> can be: Exit: Exit will cause the UPDATE function to exit without doing anything. Wait: With this option you can tell YMS to wait for the other task(s) to finish their update function before starting UPDATE in the current task. Ignore: Useful in a single-task environment only. YMS will not use its "busy" flag. Example: ; TaskUpdateConflict Exit ; - TaskUpdateLog <[drive:pathname\]filename.ext> You cannot have YMS running in two different tasks and writing in the same LOGfile, in the same way as you cannot do it with Opus or Maximus. If you have an Opus/Maximus' logfile for Task 1, place it here; if you do not have multiple tasks, specify your sole logfile here. Leaving it blank will cause YMS to default to the log file specified for YMS COMPILE; if commented will force YMS not to generate an Update LogFile. Example: ; TaskUpdateLog D:\Opus\Opus.log ; - TaskUpdateLogLevel <number> You can specify a different LogLevel for each logfile you have. The LogLevels are the same specified for the Log function (see above). If commented, it will default to the value specified for LogLevel. Example: YMS v2.00 Reference Guide Page 16 ; TaskUpdateLogLevel 4 ; - TaskUpdateWaitTime <number> If not commented, TaskUpdateWaitTime will specify how much time YMS has to wait before taking the action specified with TaskUpdateConflict. WARNING: if TaskUpdateWaitTime rolls over (and you have specified either Ignore or Wait for TaskUpdateConflict) while the other task is not hung, and is performing an UPDATE too, you will have the two tasks conflicting and you will completely lose your message waiting base, requiring a new compile. Therefore, in these cases, please choose a reasonably high time. In my humble opinion, you can have one task with TaskUpdateConflict Wait and a high TaskUpdateWaitTime and all other tasks with Exit and no TaskUpdateWaitTime. In this way the Exit tasks will be faster, and the Wait task will avoid that, if the other task crashed running YMS and leaving YMS' "busy" flag high, UPDATE would no longer take place. Example: ; TaskUpdateWaitTime 120 ; - UserlistDirectory <Path/Filename> If you can't use BbsDirectory (see 'BbsDirectory' above), you must use UserlistDirectory and SystemDirectory. For OPUS 1.1x: the path where you have the USER.IDX file. For OPUS 1.7x: the path where you have the USER.DAT file. For Maximus 1.02: the actual FILENAME (not the pathname only!!) for you userlist. Example: ; UserlistDirectory C:\MAXUSER\USER.BBS ; - UseExternMailCheck OPUS 1.70 only. Don't include an area for message waiting if it hasn't the 'EXTERN MAILCHECK' flag in your OPUS control file. You can therefore decide which areas include for mail checking in OPUS control file (and not in YMS) by uncommenting UseExternMailCheck and selecting an 'AreaInclude 0-2047'. ; UseExternMailCheck ; - UseUTCTime Tells YMS to use UTC time when marking forwarded messages with its own kludge (and specify it adding UTC as a suffix). You must have the TZ environment set correctly to have this function work properly. Example: ; UseUTCTime YMS v2.00 Reference Guide Page 17 ; - YmsDirectory <Pathname> The directory used by YMS to store its support files. If left blank will default to the current directory. Example: ; YmsDirectory D:\Opus\Yms ; YMS v2.00 Reference Guide Page 18 Section 3 - LANGUAGE FILE ARGUMENTS =================================== 3.1 ESCAPE COMMANDS +--------------------------------------------------------------+ | Escape commands translated by YMS_LC.EXE: | +--------------------------------------------------------------+ | | | \\ A single BackSlash \ | | \# Space, ASCII 32, to better show it | | \' Single quote, ', ASCII 39 | | \" Double quotes, ", ASCII 34 | | \a Bell, Ctrl-G, ASCII 7 | | \b BackSpace, Ctrl-H, ASCII 8 | | \f FormFeed, ClearScreen, Ctrl-L, ASCII 12 | | \n LineFeed, Ctrl-J, ASCII 10 | | \r Carriage Return, Ctrl-M, Enter, ASCII 13 | | \t Tab, Ctrl-I, ASCII 9 | | \v Vertical Tab, Ctrl-K, ASCII 11 | | \d### Decimal number ###, 3 digits or up to the first | | non-digit character (\d012 or \d12\r) | | \x### Hexadecimal number ### (base 16) (as for \d###) | | \### Octal number ### (base 8) (as for \d and \x) | | | +--------------------------------------------------------------+ 3.2 OPUS/MAXIMUS EMBEDDED COMMANDS AND AVATAR COLOUR CODES TRANSLATE TABLES Avatar Colour Codes (for further showing of the OutFile by Opus/Maximus) can be inserted in the language font files "as they are" (I mean using the real ^V^A etc characters) but, as YMS compiler supports escape commands, I think it is better to use them, as they can be easily read. Knowing that the escape translations for ^V^A are: ASCII OCTAL DECIMAL HEXADECIMAL ^V^A \026\001 \d22\d001 \x016\x001 you can put any Avatar Colour Code you like in your language font files using the following translate tables. YMS v2.00 Reference Guide Page 19 \ BackGround | | | | | | M | | | \ | | | | | | a | Y | | \ | B | | G | | | g | e | W | \________ | l | B | r | C | | e | l | h | \ | a | l | e | y | R | n | l | i | \ | c | u | e | a | e | t | o | t | Foreground \| k | e | n | n | d | a | w | e | ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ | |\220 |\040 |\060 |\100 |\120 |\140 |\160 | Black | (1) |\d144|\d032|\d048|\d064|\d080|\d096|\d112| | |\x090|\x020|\x030|\x040|\x050|\x060|\x070| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\201 |\221 |\041 |\061 |\101 |\121 |\141 |\161 | Blue |\d129|\d145|\d033|\d049|\d065|\d081|\d097|\d113| |\x081|\x091|\x021|\x031|\x041|\x051|\x061|\x071| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\202 |\222 |\042 |\062 |\102 |\122 |\142 |\162 | Green |\d130|\d146|\d034|\d050|\d066|\d082|\d098|\d114| |\x082|\x092|\x022|\x032|\x042|\x052|\x062|\x072| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\203 |\223 |\043 |\063 |\103 |\123 |\143 |\163 | Cyan |\d131|\d147|\d035|\d051|\d067|\d083|\d099|\d115| |\x083|\x093|\x023|\x033|\x043|\x053|\x063|\x073| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\204 |\224 |\044 |\064 |\104 |\124 |\144 |\164 | Red |\d132|\d148|\d036|\d052|\d068|\d084|\d100|\d116| |\x084|\x094|\x024|\x034|\x044|\x054|\x064|\x074| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\205 |\225 |\045 |\065 |\105 |\125 |\145 |\165 | Magenta |\d133|\d149|\d037|\d053|\d069|\d085|\d101|\d117| |\x085|\x095|\x025|\x035|\x045|\x055|\x065|\x075| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\206 |\226 |\046 |\066 |\106 |\126 |\146 |\166 | Brown |\d134|\d150|\d038|\d054|\d070|\d086|\d102|\d118| |\x086|\x096|\x026|\x036|\x046|\x056|\x066|\x076| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\207 |\227 |\047 |\067 |\107 |\127 |\147 |\167 | White |\d135|\d151|\d039|\d055|\d071|\d087|\d103|\d119| |\x087|\x097|\x027|\x037|\x047|\x057|\x067|\x077| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ (1) Black on Black is not supported. YMS v2.00 Reference Guide Page 20 \ BackGround | | | | | | M | | | \ | | | | | | a | Y | | \ | B | | G | | | g | e | W | \________ | l | B | r | C | | e | l | h | \ | a | l | e | y | R | n | l | i | \ | c | u | e | a | e | t | o | t | Foreground \| k | e | n | n | d | a | w | e | ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\210 |\230 |\050 |\070 |\110 |\130 |\150 |\170 | Grey |\d136|\d152|\d040|\d056|\d072|\d088|\d104|\d120| |\x088|\x098|\x028|\x038|\x048|\x058|\x068|\x078| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\211 |\231 |\051 |\071 |\111 |\131 |\151 |\171 | Bright Blue |\d137|\d153|\d041|\d057|\d073|\d089|\d105|\d121| |\x089|\x099|\x029|\x039|\x049|\x059|\x069|\x079| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\212 |\232 |\052 |\072 |\112 |\132 |\152 |\172 | Bright Green |\d138|\d154|\d042|\d058|\d074|\d090|\d106|\d122| |\x08a|\x09a|\x02a|\x03a|\x04a|\x05a|\x06a|\x07a| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\213 |\233 |\053 |\073 |\113 |\133 |\153 |\173 | Bright Cyan |\d139|\d155|\d043|\d059|\d075|\d091|\d107|\d123| |\x08b|\x09b|\x02b|\x03b|\x04b|\x05b|\x06b|\x07b| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\214 |\234 |\054 |\074 |\114 |\134 |\154 |\174 | Bright Red |\d140|\d156|\d044|\d060|\d076|\d092|\d108|\d124| |\x08c|\x09c|\x02c|\x03c|\x04c|\x05c|\x06c|\x07c| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\215 |\235 |\055 |\075 |\115 |\135 |\155 |\175 | Bright Magenta |\d141|\d157|\d045|\d061|\d077|\d093|\d109|\d125| |\x08d|\x09d|\x02d|\x03d|\x04d|\x05d|\x06d|\x07d| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\216 |\236 |\056 |\076 |\116 |\136 |\156 |\176 | Yellow |\d142|\d158|\d046|\d062|\d078|\d094|\d110|\d126| |\x08e|\x09e|\x02e|\x03e|\x04e|\x05e|\x06e|\x07e| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ |\217 |\237 |\057 |\077 |\117 |\137 |\157 |\177 | Bright White |\d143|\d159|\d047|\d063|\d079|\d095|\d111|\d127| |\x08f|\x09f|\x02f|\x03f|\x04f|\x05f|\x06f|\x07f| ---------------+-----+-----+-----+-----+-----+-----+-----+-----+ YMS v2.00 Reference Guide Page 21 For Opus/Maxmimus Embedded Commands please refer to Opus/Maximus documentation, which provides a complete table. To translate them into escape commands you simply need to know how to correctly insert some characters: +-----------+-------------+-------------+-------------+ | Character | Octal | Decimal | Hexadecimal | +-----------+-------------+-------------+-------------+ | ^A | \001 | \d001 | \x001 | | ^B | \002 | \d002 | \x002 | | ^C | \003 | \d003 | \x003 | | ^D | \004 | \d004 | \x004 | | ^E | \005 | \d005 | \x005 | | ^F | \006 | \d006 | \x006 | | ^G | \007 | \d007 | \x007 | | ^H | \010 | \d008 | \x008 | | ^I | \011 | \d009 | \x009 | | ^J | \012 | \d010 | \x00a | | ^K | \013 | \d011 | \x00b | | ^L | \014 | \d012 | \x00c | | ^M | \015 | \d013 | \x00d | | ^N | \016 | \d014 | \x00e | | ^O | \017 | \d015 | \x00f | | ^P | \020 | \d016 | \x010 | | ^Q | \021 | \d017 | \x011 | | ^R | \022 | \d018 | \x012 | | ^S | \023 | \d019 | \x013 | | ^T | \024 | \d020 | \x014 | | ^U | \025 | \d021 | \x015 | | ^V | \026 | \d022 | \x016 | | ^W | \027 | \d023 | \x017 | | ^X | \030 | \d024 | \x018 | | ^Y | \031 | \d025 | \x019 | | ^Z | \032 | \d026 | \x01a | +-----------+-------------+-------------+-------------+ 3.3 FORMAT SPECIFICATIONS FOR YMS_MAIL.F?? FILES A format specification has the following form: %{-}{width}{.precision}type - : Left-justify the result within the given field width. The default (assumed, if no '-' is specified) is to right- justify. The {width} argument is a non-negative decimal integer controlling the minimum number of characters printed. If the number of characters in the output value is less than the specified width, blanks are added to the left or the right of the values (depending on whether the '-' flag is specified) until the minimum width is reached. if {width} is prefixed with a 0, zeros are used instead of blanks. The {width} never causes a value to be truncated. If the number of YMS v2.00 Reference Guide Page 22 characters in the output values is greater than the specified {width}, or {witdh} is not given, all characters of the value are printed. The {.precision} specification is a non-negative decimal integer preceded by a period (.), which specifies the number of characters to be printed. Unlike {width}, the {.precision} can cause truncation of the output value. If 'Type' is 'a' or 'm' the {.precision} specifies the minimum number of digits to be printed. If the number of digits in the argument is less than {.precision}, the output value is padded on the left with zeros, else the complete value is printed (no truncation occurs). Default is 1. If 'Type' is 'b', 'd', 'n', 'h', 'p', 'r', 't' or 'x' the {.precision} specifies the maximum number of characters to be printed. Characters in excess of {.precision} are not printed (i.e. are truncated). No other values than 'a', 'b', 'd', 'm', 'n', 'h', 'p', 'r', 't' and 'x' are allowed, and any change in the 'type' in YMS_MAIL.F?? files can lead to unpredictable behaviors. Examples: For Type = 'a' or 'm': Format specification | Value | Output ----------------------+---------+----------------------------- %a | 4 |4.......................... %a | 10 |10......................... %a | 157 |157........................ %2a | 6 | 6......................... %2a | 13 |13......................... %2a | 184 |184........................ %3a | 8 | 8........................ %3a | 18 | 18........................ %3a | 305 |305........................ %4a | 64 | 64....................... %-4a | 74 |74 ....................... %04a | 42 |0042....................... %04a | 112 |0112....................... For Type = 'b', 'd', 'n', 'h', 'p', 'r', 't' or 'x': Format specification | Value | Output ----------------------+---------+----------------------------- %d | Fred |Fred....................... %10d | Fred | Fred................. %-10d | Fred |Fred ................. %.4d | Fred |Fred....................... %.4d | Robert |Robe....................... %6.4d | Robert | Robe..................... YMS v2.00 Reference Guide Page 23 Section 4 - YMS LANGUAGE COMPILER ================================= 4.1 USAGE [drive:\pathname\]YMS_LC language#... [-d{fontfile_path}] [drive:\pathname\]YMS_LC * [-d{fontfile_path}] Where 'language#' is the language number. Issueing YMS_LC 1 <enter> from the DOS command line will let YMS_LC compile YMS_MAIL.F01 and generate YMS_MAIL.C01. Issueing YMS_LC 2 <enter> will let YMS_LC compile YMS_MAIL.F02 and generate YMS_MAIL.C02. And so on, up to language 12. You can even compile more than one language file. Issueing YMS_LC 1 2 4 <enter>, for example, will let YMS_LC compile YMS_MAIL.F01, YMS_MAIL.F02 and YMS_MAIL.F04 generating the corresponding compiled files. You can compile ALL your language files too issueing YMS_LC * <enter>. You can optionally specify as command line argument the path were YMS_LC must look for YMS_MAIL.F0? files, if they're not in the current directory, using -d{drive:\path}. 4.2 FATAL ERRORS Y1200: Can't open language file '.....' The language compiler was unable to access the specified language file for compilation. Y1201: Can't open compiled-language file '.....' The language compiler was unable to open the brand new compiled language file for writing it to disk. Y1202: No buffering The language compiler could not "malloc" memory to work. In this case there are chances that it will work the same, but it will be terribly slow. I guess that you will never see this message. Y1203: No fontfiles (in '.....') You issued YMS_LC * <enter> but YMS_LC couldn't find any language file to compile. 4.3 OTHER ERRORS Y2200: Syntax error '......' An error was encountered while compiling the control file. You will likely get this message if you'll uncomment a line which does not contain any valid command. Y2201: Error writing '.....' The language compiler could open the file but could not finish to write it (i.e. disk full). YMS v2.00 Reference Guide Page 24 Y2202: Invalid Item '....' The language compiler encountered item '....' which is not valid for compilation. Maybe you made a mistake when editing the language font file and left in something as "NSM" instead of "NMS". Y2203: Invalid ItemNumber (..) for item '.....' YMS_LC found an invalid itemnumber suffix. 'NMS', 'YMS', 'MLS' and 'HDR' can only have :000; 'TYP' can have :000, :001 or :002; the remaining ones can have :000 or :001. So, if you specify, let's say, MLS:001 instead of MLS:000 you will have this message returned. Y2204: Item '.........' missing All the items that are part of the OutFile are mandatory, and in the case you delete one of them from the font file, you will see this message. Y2205: Can't open '.......' YMS_LC couldn't access the file specified for an '#include'. Y2206: Can't #include with '.....' The #include directive can be used with 'HDR', 'NMS', 'YMS', 'MLS' and 'FTR' only. 4.4 WARNING MESSAGES Y4200: Hex constant too big (\x###) The escape hexadecimal constant specified was too big. Y4201: Dec constant too big (\d###) The decimal constant specified was too big. Y4202: Oct constant too big (\###) The octal constant specified was too big. Y4203: Single backslash When the language compiler encounters a single backslash it assumes that it is the prefix of an escape command. If the following character is not part of the escape command set the compiler will assume that you are trying to insert a single backslash in your file (for doing this you must in fact place a double backslash \\) and will advise you about it. Y4204: Redefinition of '.........' ignored. If YMS language compiler encounters the same valid argument twice, will ignore it the second time. Let's say that you place two FTR:000;0 in your YMS_MAIL.F?? file. YMS language compiler will process it the first time, but ignore it the second. Y4205: Line too long. Truncated at ... characters. 'PVT', 'RCD', 'BRD, 'NTF', 'ALS', 'TYP' and 'MSG000' must be shorter than 128 characters. YMS v2.00 Reference Guide Page 25 4.5 ERRORLEVELS 0 No errors occurred. Compilation successful. 1 Warning messages were issued to the user. 2 File Open Error occurred (YMS_MAIL.Fxx or YMS_MAIL.Cxx) 3 Warning and Error messages were issued to the user. 4 No language file has been compiled with YMS_LC *. 255 Command line error. YMS v2.00 Reference Guide Page 26 Section 5 - YMS MAIL SEARCH MODULE ================================== 5.1 USAGE AND COMMAND LINE SWITCHES Usage (task-based search): [drive:\pathname\]YMS_MS [-T{n}] [-O{n}] [-L{n}] [-S] [-B] [-C] [-A] [-Ddrive:\pathname\] Usage (immediate mail search): [drive:\pathname\]YMS_MS "user name" [-O{n}] [-L{n}] [-S] [-B] [-G] [-V{priv}] [-K{keys}] [-Ddrive:\pathname\] Command line switches: -T{n} Example: -T2 Purpose: Search mail using the parameters of Task number {n} Default: 0 (No multitasking) Range: 0 to 255 Notes: Not necessary if you are not using the multitasking options in YMS, but absolutely mandatory is you _are_ using them. Ignored with immediate mail search. -O{n} Example: -O1 Purpose: build OutFile/Show mail using data in options number {n} Default: 0 (HDR:000;0 FTR:000;0 etc, all with a ;0 suffix) Range: 0 to 9 Notes: Use of this switch is closely connected to the way you have configured your file arguments' options. You will probably use the default in the most frequent use and call the other options just in case. -L{n} Example: -L2 Purpose: build OutFile/Show mail using language {n} Default: 1 Range: 1 to 12 Notes: This switch is ignored with task-based mail search if BbsType is either OPUS11x or OPUS17x. In this case, the current user's language is used. -S Example: -S Purpose: Toggle the current TaskShowReceived status Notes: The default status for immediate mail search is not to show received messages. Use this switch if you want them shown. YMS v2.00 Reference Guide Page 27 -B Example: -B Purpose: Toggle the current TaskAllNotToEnabled status. Notes: The default status for immediate mail search is to show broadcast messages to people listed in the EnableToAll list. -C Example: -C Purpose: Toggle the current TaskSearchSectOnly status. Notes: Ignored if executing an immediate mail search. -A Example: -A Purpose: Toggle the current TaskShowAlias status. Notes: Ignored if executing an immediate mail search. -G Example: -G Purpose: Enables graphics options (HDR:000;0G, FTR:000;0G all with a G suffix). Notes: This switch is ignored with task-based mail search. YMS_MS will use graphics options if the user uses ANSI or AVATAR. -V{priv} Example: -VF Default: -Vn (Normal) Range: {priv} can be: t (twit), d (disgrace), l (limited), n (normal), w (worthy), p (privil), f (favored), e (extra), c (clerk), a (asstsysop), s (sysop). Purpose: the privilege to use in an immediate mail search. Notes: This switch is ignored with a task-based mail search. YMS_MS will use the user's privilege. -K{keys} Example: -K45 Default: Normally no keys, but all keys if privilege is Sysop Range: 1-8 if BbsType is Max102; A-Z, 0-5 if BbsType is OPUS11x or OPUS 17x. Purpose: the keys to use in an immediate mail search. Notes: This switch is ignored with a task-based mail search. YMS_MS will use the user's keys. -D[drive:\pathname\] Example: -DC:\Opus\Yms\ Purpose: Tell YMS_MS.EXE where the YMS files are stored (YMS directory). Default: Current directory (in most cases Opus/Maximus' root dir) Notes: Use this switch if you have placed the YMS files in a subdir different than the Opus/Maximus' dir (as I do). If you have installed YMS in the Opus/Maximus root directory you will probably never need to use this switch. YMS v2.00 Reference Guide Page 28 5.2 ERROR MESSAGES Y1100: Unrecognized option '.....' You entered something wrong on the command line, and YMS mail search module was unable to understand it. Y1101: Invalid Task Number (xx) The specified task number isn't in the valid range (0 thru 255). Y1102: Invalid Option (xx) You used a -O{n} switch with {n} not in the valid range (0 thru 9). Y1103: Invalid Language (xx) You used a -L{n} switch with {n} not in the valid range (1 thru 12). Y1104: Can't find task file '...' The mail search module is unable to find the necessary task file in the current directory or in the directory specified by the -D switch. This normally happens when you specify an incorrect task number. Y1105: Task file '....' is invalid The mail search module found the task file but realized it was invalid while loading it. 5.3 WARNING MESSAGES Y4100: '.....' Unknown privilege There is an invalid privilege after a -V switch. YMS_MS will keep the default privilege (Normal) Y4101: '.': Unknown key There is an invalid key after a -K switch. Note that YMS_MS doesn't generate a warning if the key is invalid for the bbs you are operating. 5.4 LOGFILE MESSAGES +-- Level v 4 Begin SEARCH, v2.00, Task=xx Begin of SEARCH phase 1 Blind search -no mail found- This message will be shown each time an error occurs, and will be shown together with another error message; "blind search" means that YMS_MS.EXE was aware that something went wrong, and assumed "No_Mail_Sir" was to be shown 3 Can't find language file #xx (....) YMS_MS can't find the compiled language file for language xx YMS v2.00 Reference Guide Page 29 1 Can't find lastuser file '....' YMS_MS cannot find the specified lastuser file 1 Can't find message base 'YMS_USER.DAT' YMS_MS can't find the message waiting base 1 Can't find parameter file 'YMS_PRM.DAT' YMS_MS can't find the global parameter file 1 Can't load language file #xx (....) YMS_MS can't load the compiled language file for language xx, probably due to a disk error or insufficient memory. Try to reduce the size of YMS_MAIL.Cxx file or to increase available memory 1 Can't read index! (Mem: ....) YMS_MS has not enough memory to load the user index. Try to increase available memory 1 Can't read lastuser file '....' YMS_MS can't read the specified lastuser file due to a disk I/O error or a corrupted file 4 End SEARCH End of SEARCH phase 1 Error creating TaskOutFile '....' An error occurred while creating the specified OutFile. This can be caused by an invalid filename or a disk full 1 Error reading data file '....' A disk I/O error occurred while reading YMS_USER.DAT. This error may happen also if it is corrupted 1 Error reading parameter file A disk I/O error occurred while reading YMS_PRM.DAT. This error may happen also if it is corrupted 1 Error writing TaskOutFile: disk full?? An error occurred while writing to the specified OutFile. This can be caused by an invalid filename or a disk full 1 Invalid format specifier YMS_MS encountered an invalid format specifier in the current language. This means that YMS_MS found a precent sign followed by something illegal (a '%' can be followed by one of 'a', 'b', 'd', 'm', 'n', 'h', 'p', 'r', 't', 'x' and '%') 1 Invalid PRM format. Expected xx, Found yy Incorrect PRM version. Use YMS COMPILE to recreate it 1 Invalid version for '....': found xx, expected yy Incorrect version for a compiled language file. Use YMS_LC to recreate it YMS v2.00 Reference Guide Page 30 5 Keyboard ESC You pressed ESC during and Update/Search conflict. 1 Not enough memory (Lastuser) Not enough memory to load the lastuser file. Try to increase available memory 1 Not enough memory (msg_wait) Not enough memory to load the message waiting user record. Try to increase available memory 1 Out of memory (YMSprintf) There is not enough memory to process a certain language file line. Try to increase available memory or to reduce the length of MSG000 lines 1 Parameter file '....' is invalid A disk I/O error occurred while reading the YMS_PRM.DAT file, or it is corrupted 3 Search/Update conflict. User notified User has been notified about a Search/Update conflict. 5 SysOp selected <option> You selected either <option1> or <option2> during an Update conflict 3 Trying language 1 YMS_MS has not found a compiled language file for the current user's language, so it will default to language 1 3 Update conflict: waiting. <option1> or <option2>? There is an Update conflict. If you are snooping you can choose either <option1> or <option2> to take place immediatly 3 User HAS xx msgs waiting The user has xx messages waiting 3 User has NO mail waiting Either the user has no mail waiting or his/her name isn't in the YMS user base 1 Wait time (## secs) elapsed The selected TaskSearchWaitTime is over 5.5 ERRORLEVELS 0 No errors occurred. Mail search successfully executed. 2 The mail search module was unable to find the task file YMS_PRM.D?? (maybe there was none or maybe you invoked YMS_MS.EXE from a subdir different than YmsDirectory, and therefore you YMS v2.00 Reference Guide Page 31 should have to use the -D command line switch). 3 The mail search module found the task file YMS_PRM.D?? but was unable to correctly read it, as the file was invalid. 4 The mail search module was unable to find the main parameter file YMS_PRM.DAT (see explanation between brackets for ErrorLevel 2). 5 The mail search module found the main parameter file YMS_PRM.DAT but was unable to correctly read it, as the file was invalid. 6 The mail search module was unable to find default language file YMS_MAIL.C01 (see explanation in brackets for ErrorLevel 2). 7 The path&filename specified in the .CTL file for generating the TaskOutFile was invalid, and the mail search module was unable to create any OutFile. 8 An error occurred when writing the TaskOutFile (i.e. diskfull). 9 The mail search module was able to correctly open the main parameter file YMS_PRM.DAT but was unable to complete the reading. 10 The YMS_PRM.DAT file read had an invalid version. 11 Invalid arguments were given on the command line. 12 The mail search module found an invalid format specifier in the current compiled language file 13 There is not enough memory to hold outfile data. Either increase the available memory or try to semplify (shorten) MSG000 items in the current language file. YMS v2.00 Reference Guide Page 32 Section 6 - THE ON-LINE SEARCH MODULE ===================================== 6.1 USAGE AND COMMAND LINE SWITCHES Usage: [drive:\pathname\]YMS_OS [-T{n}] [-K{key1}{key2}] [-P] [-B] [-N] [-1] [-C] [-A] [-Ddrive:\pathname\] Command line switches: -T{n} Example: -T2 Purpose: Search mail using the parameters of Task number {n} Default: 0 (No multitasking) Range: 0 to 255 Notes: Not necessary if you are not using the multitasking options in YMS, but absolutely mandatory is you _are_ using them. -K{key1}{key2} Example: -K45 Purpose: Select keys YMS_OS uses to return informations after an on-line search. YMS_OS will set {key1} only if the user hasn't mail waiting, {key2} only if the user has read all his/her mail during this session, both {key1} and {key2} if there is a TaskOnlineConflict (and you choose notify), and will clear both keys if it has successfully set user's lastread pointer and current area. Default: If you don't use -K at all, no key will be changed, else the default for {key1} is 4 for OPUS and 7 for Maximus, for {key2} is 5 for OPUS and 8 for Maximus. Range: A-Z, 0-5 for OPUS, 1-8 for Maximus. Notes: You can use the errorlevel returned by YMS_OS instead of the keys if your BBS supports it. -P Example: -P Purpose: Select personal mail only to be shown by YMS_OS. Notes: Normally YMS_OS shows all mail to the user. If one of '-P', '-B' and '-N' switch is present, then YMS_OS will show only selected mail. -B Example: -B Purpose: Select broadcast messages only to be shown by YMS_OS. Notes: Normally YMS_OS shows all mail to the user. If one of '-P', '-B' and '-N' switch is present, then YMS_OS will show only selected mail. -N Example: -N YMS v2.00 Reference Guide Page 33 Purpose: Select "Notify"ed messages only to be shown by YMS_OS. Notes: Normally YMS_OS shows all mail to the user. If one of '-P', '-B' and '-N' switch is present, then YMS_OS will show only selected mail. Beware private messages!! -1 Example: -1 Purpose: Change the lastread pointer to point to the message before the one to be shown, in order to use a "show next" command. Notes: Normally YMS_OS changes the lastread pointer to point to the message to be shown. This requires a "show current message" command. -C Example: -C Purpose: Toggles the current TaskAllowChangeSect status. -A Example: -A Purpose: Toggles the current TashOnlineShowAlias status. -D[drive:\pathname\] Example: -DC:\Opus\Yms\ Purpose: Tell YMS_OS.EXE where the YMS files are stored (YMS directory). Default: Current directory (in most cases Opus/Maximus' root dir) Notes: Use this switch if you have placed the YMS files in a subdir different than the Opus/Maximus' dir (as I do). If you have installed YMS in the Opus/Maximus root directory you will probably never need to use this switch. 6.2 ERROR MESSAGES Y1300: Unrecognized option '....' You entered something wrong on the command line, and YMS online search module was unable to understand it. Y1301: Invalid Task Number (xx) The specified task number isn't in the valid range (0 thru 255). Y1302: Can't find task file '...' The online search module is unable to find the necessary task file in the current directory or in the directory specified by the -D switch. This normally happens when you specify an incorrect task number. Y1303: Task file '....' is invalid The online search module found the task file but realized it was invalid while loading it. YMS v2.00 Reference Guide Page 34 6.3 WARNING MESSAGES Y4300: 'c': Unknown key. There is an invalid key after a -K switch. Note that YMS_MS doesn't generate a warning if the key is invalid for the bbs you are operating. 6.4 LOGFILE MESSAGES +-- Level v 4 Begin ON-LINE, v2.00, Task=xx Begin of ON-LINE phase 1 Can't create '....' Opus 1.7x only. YMS_OS wasn't able to create the LREAD.DAT file in the specified area 1 Can't create data file '....' YMS_OS wasn't able to create its temporary file _YMS_OS_.Txx 1 Can't delete data file '....'! YMS_OS wasn't able to delete a corrupted temporary file 1 Can't find '....' Maximus 1.02 only. YMS_OS wasn't able to locate the LASTREAD.BBS file in the specified area 1 Can't find lastuser file '%s' YMS_MS cannot find the specified lastuser file 1 Can't find message base 'YMS_USER.DAT' YMS_MS can't find the message waiting base 1 Can't find parameter file 'YMS_PRM.DAT' YMS_MS can't find the global parameter file 1 Can't read '....' A disk error occurred while reading the specified LastRead file. Maximus 1.02 and Opus 1.7x only 1 Can't read index! (Mem: ....) YMS_MS has not enough memory to load the user index. Try to increase available memory 1 Can't update '....' A disk error occurred while updating the specified LastRead file. Maximus 1.02 and Opus 1.7x only 1 Can't update data file '....' YMS_OS temporary file cannot be updated 1 Data file '....' is corrupted or invalid YMS_OS temporary file (_YMS_OS_.Txx) is corrupted or invalid. YMS v2.00 Reference Guide Page 35 This may happen if a file (not the one made by YMS) with the same name exists in the Ramdisk path 4 End ON-LINE End of ON-LINE phase 1 Error reading data file '....' A disk error occurred while reading YMS_OS temporary file 1 Error reading parameter file A disk I/O error occurred while reading YMS_PRM.DAT. This error may happen also if it is corrupted 1 Invalid PRM format. Expected xx, Found yy Incorrect PRM version. Use YMS COMPILE to recreate it 5 Keyboard ESC You pressed ESC during and Update/Online conflict. 1 Not enough memory (....) There is not enough free memory for YMS_OS to run properly. Try increase available ram 3 Online/Update conflict. User notified. User has been notified about an Online/Update conflict. 1 Parameter file '....' is invalid A disk I/O error occurred while reading the YMS_PRM.DAT file, or it is corrupted 4 Searching mail... There is a different user online than last execution of YMS_OS, so YMS_OS has to search his/her mail 4 Setting lastread to msg xx, area yy YMS_OS found a message for the user who is online, and set his/her lastuser/lastread to show it 5 SysOp selected <option> You selected either <option1> or <option2> during an update conflict 3 Update conflict: waiting. <option1> or <option2>? There is an Update conflict. If you are snooping you can choose either <option1> or <option2> to take place immediatly 4 User has NO mail waiting Either the user has no mail waiting or his/her name isn't in the YMS user base 4 User has no more messages waiting He/She has already read all his/her own mail during this call 1 Wait time (## secs) elapsed The selected TaskOnlineWaitTime is over YMS v2.00 Reference Guide Page 36 6.5 ERRORLEVELS 0 Everything worked as expected and the user has mail waiting. 1 The user has already read all his/her own mail. 2 The user hasn't mail waiting. 3 There was a TaskOnlineConflict to notify to the user. 11 Invalid arguments were given on the command line. 12 The online search module was unable to find the task file YMS_PRM.D?? (maybe there was none or maybe you invoked YMS_OS.EXE from a subdir different than YmsDirectory, and therefore you should have to use the -D command line switch). 13 The online search module found the task file YMS_PRM.D?? but was unable to correctly read it, as the file was invalid. 14 The online search module wasn't able to find the specified LASTUSER file. 15 The online search module wasn't able to load the lastuser file, due to insufficient memory. 16 The online search module found the lastuser file invalid. YMS v2.00 Reference Guide Page 37 Section 7 - THE MAIN PROGRAM ============================ Usage: [drive:\pathname\]YMS [COMPILE | UPDATE | CTLCOMPILE | AREAUPDATE] [switches] 7.1 YMS COMPILE Syntax: [drive:\pathname\]YMS COMPILE [drive:\pathname\ctlfile.ext] The only argument accepted by YMS COMPILE is the name of the control file. If not specified, it will default to YMS.CTL in the current directory. I currently see no need to use a filename different than YMS.CTL as it already contains all the necessary informations, including multi-task environments. 7.2 YMS UPDATE Syntax: [drive:\path\]YMS UPDATE [-T{n}] [-L] [-N] [-f/-F{echotoss.log}] [-E] [-Ddrive:\pathname\] -T{n} Example: -T1 Purpose: Specify the task number in which you are performing UPDATE. Default: -T0 Range: 0 to 255 -L Example: -L Purpose: Perform update in LOCAL areas only. No other areas will be affected by UPDATE. Can be used in conjunction with '- N', '-f/F' and '-E'. Notes: Normally YMS updates all the areas. If one of '-L', '-N', '-f/F', '-E' switch is present, YMS will update only the selected areas. -N Example: -N Purpose: Perform update in the MATRIX (NetMail) area only. No other areas will be affected by UPDATE. It can be used in conjunction with '-L', '-f/F', '-E'. Notes: Normally YMS updates all the areas. If one of '-L', '-N', '-f/F', '-E' switch is present, YMS will update only the selected areas. -f[drive:\pathname\filename.ext] Example: -fC:\Opus\EchoToss.Log Purpose: Perform UPDATE in the areas which tagname is listed in the specified file. It can be used in conjunction with YMS v2.00 Reference Guide Page 38 '-L', '-N', '-E'. Notes: Normally YMS updates all the areas. If one of '-L', '-N', '-f/F', '-E' switch is present, YMS will update only the selected areas. -F[drive:\pathname\filename.ext] Example: -FC:\Opus\EchoToss.Log Purpose: Ditto, as -f except that it deletes the specified file after processing it. -E Example: -E Purpose: Perform UPDATE in all echomail area. It can be used in conjunction with '-L', '-N-, '-f/F'. Notes: Normally YMS updates all the areas. If one of '-L', '-N', '-f/F', '-E' switch is present, YMS will update only the selected areas. -D[drive:\pathname\] Example: -DC:\Opus\Yms Purpose: Tell YMS where to find its support files (YMS directory). Default: Current directory (generally Opus/Maximus' root dir). 7.3 YMS CTLCOMPILE Syntax: [drive:\pathname\]YMS CTLCOMPILE [drive:\pathname\ctlfile.ext] It will cause YMS to re-compile the control file and build again its own support files. All the changes you made will immediately have effect, but consider that some, as MatrixForward are not retroactive (will begin to work with the messages that will be processed starting from NOW, but not with the messages already processes by YMS) and some others may be ignored until the next full COMPILE (i.e. RecordsPerUser). The path and filename of the control file may be specified as the second command line argument. As YMS COMPILE, it will default to use YMS.CTL in the current directory. 7.4 YMS AREAUPDATE Syntax: [drive:\pathname\]YMS AREAUPDATE [-Ddrive:\pathname\] YMS AREAUPDATE will scan your SYSTEM??.DAT or AREA.DAT or SYSMSG.DAT files and check for new privileges and locks and it will see if there are new areas, if any area has been deleted and if areas have been switched. New privileges and locks will be respected when showing mail to users with YMS_MS.EXE or YMS_OS.EXE; new areas, if any, will not be included until the next full COMPILE; deleted areas will be disabled from the message waiting base and switched areas will be correctly renumbered. YMS v2.00 Reference Guide Page 39 If BbsType is OPUS11x, AREAUPDATE will scan all SYSTEM??.DAT until it reaches the 255th, looking for every single one, even if there are "holes" in between. Otherwise, if you want AREAUPDATE to stop after the first "hole" in the SYSTEM??.DAT sequence, simply hit any key just after the program has started. You can specify, using the switch -D, the directory where YMS support files are stored (YmsDirectory); otherwise it will default to the current directory. 7.5 FATAL ERRORS Y1000: Invalid option '.........' YMS was invoked using a wrong option (not COMPILE nor UPDATE nor CTLCOMPILE nor AREAUPDATE) Y1001: Yms does not work with DOS x.yy YMS requires DOS 3.0 or higher to work. Y1002: Can't open file '.....' YMS was unable to find/open its control file '.....' (Default: YMS.CTL). Y1003: Not enough memory (......) There was not enough memory for YMS to hold the informations necessary to perform the requested function. Y1004: Can't find parameter '....' YMS was unable to find parameter file YMS_PRM.DAT. Y1005: Parameter file '....' is invalid. YMS found its parameter file (YMS_PRM.DAT) corrupted. Y1006: Can't find old parameter '...........' YMS could not find the old YMS_PRM.DAT (CTLCOMPILE only). Y1007: Old parameter file '....' is invalid. The old YMS_PRM.DAT file is invalid (CTLCOMPILE only). Y1008: Can't update '....' YMS CTLCOMPILE or YMS AREAUPDATE was unable to re-write the file YMS_PRM.DAT with the new informations. Y1009: Error writing Task data An error occurred writing task files YMS_PRM.D?? (CTLCOMPILE only). Y1010: Invalid PRM format, expected x, found y YMS loaded an old version of YMS_PRM.DAT file. A full COMPILE is required. Y1011: Keyboard break YMS received a control-c or control-break from keyboard. YMS v2.00 Reference Guide Page 40 Y1012: Can't write temp file '....' YMS AREAUPDATE is unable to write to a temporary file needed for area processing, due to (probably) a disk full. Y1013: Unrecognized option '....' You entered something wrong on the command line, and YMS mail search module was unable to understand it. Y1014: Can't find task file '....' YMS could not find the required task file YMS_PRM.D??. Y1015: Task file '....' is invalid YMS found the task file, but could not process it, as it is invalid. Y1016: Can't change BBS. Use YMS COMPILE. You tried to change BbsType with YMS CTLCOMPILE. A full compile is required ti change BbsType. 7.6 ERROR MESSAGES Y2000: syntax error '........' User made a syntax error on the command line. Y2001: cannot make sense of '.....' YMS encountered an unknown combination of control file arguments (i.e. it will be issued if you entered TaskUpdateConflict Sleep instead of Wait or Exit). Y2002: Unable to find directory '.....' YMS was unable to find the specified directory (maybe the directory does not exist). Y2003: Invalid NetWork Address Your system's address, as specified in the control file, is not in the format ZONE:NET/NODE or NET/NODE or has an invalid domain syntax (a missing '@', for example). Y2004: Invalid filename '.....' Somewhere in the control file an invalid DOS filename was specified (i.e. Log D:\Opus\Log:file.log.1) (!!). Y2005: Invalid RecordsPerUser value (xx) The RecordsPerUser value was <= 0 (less than or equal to zero). Y2006: No Message areas included No message areas where specified using AreaInclude. Technically impossible to perform a COMPILE. Y2007: Not enough memory for 'Task xx' data YMS was unable to allocate memory to hold the informations for a task (file YMS_PRM.D??). YMS v2.00 Reference Guide Page 41 Y2008: Invalid PointNet The PointNet specified in the control file was not in the range between 1 and 65534. Y2009: Missing Network Address The Address was not specified in the control file. Y2010: Invalid Domain You specified an invalid domain (i.e., without a leading '@') within the Address statement. Y2011: Invalid Domain Gate There is probably a syntax error on e DomainGate line. Y2012: Not enough memory There is insufficient memory to process the control file. Try to increase available memory. Y2013: '....' missing. The BbsDirectory (or the corresponding SystemDirectory and UserlistDirectory) is missing. 7.7 WARNING MESSAGES Y4000: Maximum EnableToAll exceeded The list of EnableToAll names in the control file exceeded the limit of 16. Y4001: Maximum AllUser exceeded The list of AllUser names in the control file exceeded the limit of 16. Y4002: Invalid MatrixForward entry A MatrixForward entry in the control file was not in an acceptable format (i.e. the name was missing or the address was misspelled). Y4003: Max Matrix forward entries exceeded The MatrixForward list exceeded the limit. Y4004: Area xx included more than once YMS found the same area number more than once in the AreaInclude list. It will be processed only once. Y4005: Invalid Task number (xx->yy) A Task statement specified in the control file was less than 0 or more than 255. YMS will convert the number xx to yy (mod 256) and continue program execution. Y4006: Duplicated Task statement YMS found the same Task number twice. The entries listed under the two same 'Task n' are merged. Y4007: Flag 'IncludeReceived' can't be changed The flag IncludeReceived has been correctly modified but won't YMS v2.00 Reference Guide Page 42 have effect until the next full compile (CTLCOMPILE only). Y4008: Flags 'MatrixFwdPublic/Private' changed. Not retroactive One or both of the MatrixFwd flags were changed. They have correctly been compiled but will have effect starting from NOW (and not on messages that have already been processed by YMS). (CTLCOMPILE only). Y4009: Flag 'SentAsReceived' changed. Not retroactive Ditto, as for Y4008. Y4010: AreaInclude xx requires a full compile AreaInclude list was changed. New areas will not be included until the next full compile. Y4011: MatrixFwdAreaInclude xx requires a full compile Ditto, as for Y4010. Y4012: EnableToAll list changed. Not retroactive Ditto, as for Y4008. Y4013: AllUser list changed. Not retroactive Ditto, as for Y4008. Y4014: MatrixFwd list changed. Not retroactive Ditto, as for Y4009. Y4015: RecordsPerUser can't be changed Ditto, as for Y4008. Y4016: No Task Statement No Task statements were found. WARNING: COMPILE has been executed but there are very good chances that YMS will not work. Y4017: '....': forward with no areas You have a MatrixForward without selected areas. Can be caused by a syntaz error or by a MatrixForward located BEFORE the first MatrixFwdAreaInclude or the first ForcedFwdAreaInclude. Y4018: IEPNotFwdedMsgs behaviour changed. Not retroactive Ditto, as for Y4008. Y4019: '....': redefinition ignored The control file statement '....' has been found more than once in the control file being COMPILED or CTLCOMPILED. This doesn't apply for statements which can be really used more than once (AreaInclude or IEPAreasBbs, for example). Y4020: MatrixForward redefinition for '....' The name '....' has been used more than once within a MatrixForward statement. YMS can forward to one address at a time only, so you can't use the same name to forward to more than ONE address. YMS v2.00 Reference Guide Page 43 Y4021: Temp file error on '....' There is an I/O error on the temporary file YMS uses to handle ExcludeMr/Miss/Mrs and IncludeMr/Miss/Mrs. This is generally a disk full, since YMS creates this file on the path specified by Ramdisk which can be small. To solve this problem either reduce the number of Exclude/Include you use, increase your ramdisk or move the Ramdisk statement AFTER the first Exclude/Include in you control file. By doing so, YMS will create its temporary file in the startup directory instead of using the ramdisk. Y4022: '....' not In/Excluded Normally a consequence of warning Y4021. Due to an I/O error, Include/Exclude statements will no longer work. Y4023: Maximum DomainGate exceeded The list of DomainGates in the control file exceeded the limit of 16. Y4024: Ignoring DomainGates in 4D mode DomainGate statements cannot be used if you aren't operating in a 5D environment (i.e. you are not using an Address in the form of zone:net/node@domain). Y4025: Useless DomainGate You specified a DomainGate for your current domain, as stated with the Address statement. Y4026: Insufficient memory. Ignored There isn't enough memory to hold another Task data. Y4027: No Task defined. 'Task 0' assumed YMS found a Task-related statement without having before defined to what task it should refer. Y4028: Invalid Notify entry There is probably a syntax error within a Notify statement (such a missing 'to' or missing quotes). Y4029: Maximum Notify exceeded The list of Notify in the control file exceeded the limit of 32. Y4030: No Bbs defined. 'Opus 1.1x' assumed The Bbs statement is missing from the control file. YMS assumes you are operating OPUS 1.1x. Y4031: Area number (....) too high. Ignored YMS encountered in an AreaInclude statement an area number too high for the bbs you specified. OPUS 1.1x requires an area number between 0 and 254, Maximus 1.02 between 0 and 1295, OPUS 1.7x between 0 and 2047. Y4032: Read error on temp file '_YMS_AU_.TMP'. Area disabled During a YMS AREAUPDATE an I/O error occurred. YMS cannot read the recorded information for one area, so to avoid problems decided to disable it. A full COMPILE is required to re-include YMS v2.00 Reference Guide Page 44 that area. Y4033: '....' without Opus 1.7x. Ignored Some control file statements have meaning only if you are operating OPUS 1.7x. If you haven't Bbs Opus17x they are ignored. Y4034: Notify list changed. Not retroactive Ditto, as for Y4008. Y4035: 'TaskUpdateConflict Ignore' and multitasking TaskUpdateConflict Ignore is recommended only if you are operating a single-line/single-task BBS. Its use in multi-line/multitasking environments is dangerous. Y4036: Change in 'UseExternMailCheck'. Run AREAUPADTE If you change 'UseExternMailCheck' YMS CTLCOMPILE isn't able to exclude/include areas based on the 'EXTERN MAILCHECK' flag in your OPUS control file. You must run YMS AREAUPDATE (or do a full compile) which will take care of them. 7.8 LOGFILE MESSAGES (ALL FUNCTIONS) +-- Level v 4 ## new/changed messages, ## processed Statistics on processed messages 2 #xx: yy -> zz [jjjj] Information about the messages forwarded 5 '....': fwd excluded from area xx The IEP has excluded this forward according to the informations obtained from an ECHOmail information file 4 'Echotoss.Log' deleted YMS response after a YMS UPDATE made using the -F switch 4 Area xx (yy msgs) compiled Informational messages after having compiled a message area. If you keep having '(0 msgs)' in all areas and you have Lowlevel enabled, it means that LowLevel doesn't work on your system and that YMS detection logic failed to notice this. Unless you have really 0 msgs in all areas!! 3 Area xx does not exist. Excluded. You 'AreaInclude'd an area which does not exists 3 Area xx hasn't a message path. Excluded. Area xx exists, but it hasn't a message path. Probably this area exists as a file area only 3 Area xx is the MATRIX. Compiling later The MATRIX area is always compiled last too keep trace of forwarded messages YMS v2.00 Reference Guide Page 45 1 Area xx isn't of *.MSG type. Excluded. Maximus only. You included a non *.MSG type area. YMS can handle only *.MSG message bases 3 Area xx/Area yy: Skipping dupe 'zzzz' Area xx and area yy has the same message path, so area yy will be excluded. 1 B+Tree error Opus 1.7x only. It indicates an index error on file NUMBER.MDX 4 Begin COMPILE, v2.00 Start of COMPILE phase 4 Begin UPDATE, v2.00, Task=xx Begin of UPDATE phase 1 Can't Change to Directory '....'. No forwards made. The forward routine wasn't able to enter the 'NetMail' directory 1 Can't Change to Directory '....' This may happen if there is an invalid path in area informations (SYSTEMxx.DAT, AREA.DAT or SYSMSG.DAT) 1 Can't delete 'Echotoss.Log'!! Probably it is marked read only or it has been deleted (in multitasking environments) in an another task 1 Can't find data file '....' YMS UPDATE isn't able to find the message waiting base, YMS_USER.DAT 1 Can't find Yms_Rec.Dat YMS cannot find its history file for a specified area. If this happens, YMS will automatically exclude that area from any following operation. A full compile is required to reinclude the area after having removed the problem (generally a disk full condition). 3 Can't open '....' for area xx. Excluded. YMS cannot find/open SYSTEMxx.DAT for area xx 3 Can't open '....' YMS cannot find/open the specified file 1 Can't read msg #xx Without lowlevel only. YMS found the message in the directory but couldn't load it. It may happen in multitasking systems if the message has been deleted during YMS processing 1 Can't read user index. (Mem: xx) YMS UPDATE has not enough memory to load the user index. Try to increase available memory (30/40K or so) YMS v2.00 Reference Guide Page 46 1 Can't read Userlist file '....'. Aborting. YMS couldn't open the userlist file. This can be caused by an error in setting UserlistDirectory or BbsDirectory 1 Cannot update '....' YMS cannot mark that msgs as 'received' probably due to a disk I/O error 2 Copy buffer size: xx bytes The buffer YMS uses to forward messages is xx bytes long. If the message to forward is smaller, everything is ok; if it is greater, YMS will find (and strip) ^A lines only in the first half or in the first xx bytes of the message, whichever is less, and will find (and strip/modify) Origin, SEEN-BYs and ^APATH lines only in the second half or the last xx bytes of the message, whichever is less 3 Ctl file '%s' compiled with %d Warning Error(s) YMS COMPILE will put this informational message in the log file. It can be useful to see if there are problems in your control files when compiled unattended 1 CTRL-C: Executing cleanup before exiting YMS response to a CTRL-C or CTRL-Break during a YMS UPDATE 1 Disk I/O error. Status xxxx A disk error has occurred during a lowlevel disk read of the boot sector. See section 8 of the Reference Manual to understand what 'Status' means 1 Dos error (##) on IOCTL, disk x: This should indicate a DOS problem. Actually, I think that this error will never occur 4 End COMPILE End of COMPILE phase 4 End UPDATE End of UPDATE phase 1 Error creating userdat file '....' This error generally indicates a disk full condition: there isn't enough disk space to hold the YMS_USER.DAT file. 1 Error occurred in area xx A generic error happened while processing area xx. This error message generally follows a specific description of the problem occurred 3 Error occurred: excluding area xx A generic error happened while processing area xx. This error message generally follows a specific description of the problem occurred. Due to this error, this area is excluded YMS v2.00 Reference Guide Page 47 1 Error opening '....' An error occurred opening file '....' 1 Error opening '....' YMS cannot create the forwarded message, probably due to a disk full 1 Error opening 'YMS_PRM.DAT'. Aborting YMS cannot open its YMS_PRM.DAT file. Since all the relevant informations are in this file, YMS is aborted 1 Error reading '....'. No forwards made. A disk I/O error occurred while reading YMS_PRM.DAT. 1 Error reading '....'. Skipping YMS cannot find the message it has to forward. This error may happen in multitasking environments if the message has been deleted suring YMS processing 1 Error reading '....' A disk I/O error occurred while reading the specified file 3 Error reading informations for area xx. Excluded. An error (normally a disk error or a corrupted file) occurred while reading informations for area xx. Due to this problem, area xx has been excluded 1 Error reading prm file.. A disk I/O error occurred while reading YMS_PRM.DAT. 1 Error reading Userlist I/O error reading the userlist file. Can normally happen if it is corrupted 1 Error updating 'path\Yms_Rec.Dat'. Disk full?? YMS isn't able to update its history file. This generally indicates a disk full condition 1 Error updating Yms_Rec.Dat after forward YMS isn't able to update its history file after a forward. This generally indicates a disk full condition 1 Error writing '%s' An error occurred while writing to file '....'. Generally this means a disk full condition 1 Error writing '....'. Disk full? YMS cannot write the forwarded message, proably due to a disk full 1 Error writing data file Disk I/O error on YMS_USER.DAT 1 Error writing index file A disk I/O error occurred while writing to YMS_USER.DAT YMS v2.00 Reference Guide Page 48 1 Error writing Task data Disk I/O error (probably a disk full) while writing a YMS_PRM.D?? file 1 Error writing to prm file.. disk full? YMS couldn't update its YMS_PRM.DAT file probably to a disk full 1 Error writing userdat file.. Disk Full?? This error generally indicates a disk full condition: there isn't enough disk space to hold the YMS_USER.DAT file. The size of this file can be computed as follow: let x be the number of users loaded and y be the RecordPerUser value, then Size of YMS_USER.DAT = 4 * x * (y + 1) 1 Error: Can't find parameter file '....' YMS UPDATE isn't able to find its YMS_PRM.DAT file 1 Error: Can't load parameter file '....' YMS UPDATE isn't able to load its YMS_PRM.DAT file 1 Error: Can't update parameter file YMS could't update status informations in its YMS_PRM.DAT file probably due to an I/O error. 3 Excluded ## user(s) of ## Number of actually excluded users 1 File '....' not found. You used the -f/Fechotoss.log switch, but YMS isn't able to locate the specified file 2 Forwarding from area .... YMS is reading from area .... the messages to forward 1 Internal malloc error. This error should not occur 1 Invalid PRM format. Expected xx, Found yy Incorrect PRM version. Use YMS COMPILE to recreate it 5 Keyboard ESC You pressed ESC during and Update conflict. 1 LowLevel: error reading FAT xx, sector yyyy, status zzzz A disk error has occurred during a lowlevel disk read of a sector belonging to a FAT. If this occurs, YMS will try to use the second copy of the FAT. See section 8 of the Reference Manual to understand what 'Status' means 1 LowLevel: FCB error Due to this (quite unlikely) error, YMS will switch to high level YMS v2.00 Reference Guide Page 49 1 LowLevel: Read error. Sector xxxx, status yyyy A disk error has occurred during a lowlevel disk read. See section 8 of the Reference Manual to understand what 'Status' means 1 Msg #xx is invalid. Skipping. This indicates a zero length message or a message with an invalid header. This error may happen in multitasking environments if the message is being created during YMS processing 2 Msg fwded to zz at #xx The message has been successfully forwarded 1 Msg number conflict (xx) This error can happen in multitasking environments. It indicates that message xx has been created in an another task during YMS processing 2 Msg routed to ....Gate at z:n/t@d The message has been routed to a Zone o Domain Gate 3 Msg2All limit exceeded: msg ## Message ## is the 33rd broadcast message YMS has found. YMS has an internal limit of 32 broadcast messages 3 New messages in area xx (path) YMS has noticed that the number of messages in area xx is now greater than the last execution of YMS. 3 No messages in directory '....' The area YMS is compiling has no messages in it 1 No Task statement in ctl file There are no Task-related statements in the control file 1 Not enough memory (....) YMS has not enough memory in its default data segment. There's nothing you can do, but this error shouldn't never happen 1 Not enough memory to process 'echotoss.log' YMS UPDATE has not enough memory to process the echotoss.log file. Use -E instead of -f/-F 1 Not enough memory. Forwarding only There is not enough memory to hold the message waiting base. Try to increase available memory and/or reduce RecordPerUser 1 Null-body msg '....' This message has an empty text 3 Partial userlist loaded (## users of ##) This can happen if you have too many users. YMS will load only the first ## users. This limit is somewhere around 5300 users, probably more, but I think that if you have more than 4800 YMS v2.00 Reference Guide Page 50 users you cannot use LowLevel 3 Processing '....' An ECHOmail information file (AREAS.BBS or ECHO.CTL or SYSMSG.DAT) is going to be processed during a YMS COMPILE 3 Processing ALL EchoMail areas Due to the previous error ALL ECHOmail areas are updated 4 Processing dir '....' YMS is compiling directory '....' 4 Reading area informations YMS COMPILE is reading either the SYSTEMxx.DAT files, or the AREA.DAT or SYSMSG.DAT file to collect area informations 4 Reading UserList YMS is reading your userlist 3 RecordsPerUser limit exceeded: msg ## Message ## has exceeded the selected RecordPerUser value 1 Sector size too large!! YMS hasn't enough memory in its data segment to load two disk sectors. This can happen on disk with large sector size (4K, 8K) or with more than 4800/4900 users. 1 Sector size too small on x: for LowLevel YMS requires a sector size of at least 256 bytes for LowLevel. Smaller sector sizes can be handled in HighLevel only 1 Skipping all EchoMail areas Due to the previous error no ECHOmail area is updated 5 SysOp selected <option> You selected either <option1> or <option2> during an update conflict 3 Sysop's CTRL-C A CTRL-C has been received during an update phase 3 Too many entries in 'echotoss.log' Echotoss.log has more than 256 different tags listed (internal YMS limit) 1 Too many msgs to forward in one session YMS cannot forward more than 128 messages in one session. Consider that messages which have to be marked received due to 'IEPNoFwdedMsgs Mark' are considered in this count too. YMS will anyway remember that some messages hasn't been forwarded and will forward them the next time 3 Tot records ##, in RAM ##, swaps ## Virtual memory statistics. Note that it can be tot records greater than records in RAM and swaps zero. This means that YMS v2.00 Reference Guide Page 51 unused records have been written to disk and never re-read 3 Update conflict: exiting There's an update conflict and you selected the 'exit' option 3 Update conflict: waiting. <option1> or <option2>? There is an Update conflict. If you are snooping you can choose either <option1> or <option2> to take place immediatly 5 Updated areas xx xx xx xx xx .... The areas YMS UPDATE has processed 3 User '....' not in userlist There's an ExcludeMr/Miss/Mrs but the following name isn't in the userlist loaded 4 Userlist (## users) loaded and sorted The ## users already counts Included and Excluded names 1 VM error. Should not occur The Virtual Memory handler couldn't find a record to swap to disk. Due to the way it chooses such records, this error should never occur 1 Wait time (## secs) elapsed The selected Task......WaitTime is over 3 Yms message base (xx bytes) saved YMS has written to disk the message waiting base. 1 [path]\Yms_Rec.Dat is invalid. The size of the Yms_Rec.Dat file differs from the one YMS expects from internal data read from its YMS_PRM.DAT file. The area is automatically excluded. 7.9 ERRORLEVELS (ALL FUNCTIONS) Glossary: C = Compile L = CtlCompile A = AreaUpdate U = Update Here you will find ALL the errorlevels returned by YMS, which will in case be useful for debugging. However, the exit codes that you should know are: 0 - No errors occurred. 1 - No errors occurred; NetMail messages were generated due to one ore more messages forwarded. 2 -> 39 Error conditions. YMS v2.00 Reference Guide Page 52 YMS.EXE Error Conditions in Detail: 2 CL There is an error in the control file 3 C YMS was unable to open YMS_PRM.DAT for writing. 4 C YMS was unable to find and load USER.IDX file. 5 CA YMS was unable to update informations contained in YMS_PRM.DAT. 7 C YMS was unable to create YMS_USER.IDX file. 8 C An error occurred writing YMS_USER.IDX file. 9 C YMS was unable to create YMS_USER.DAT file. 10 C An error occurred writing YMS_USER.DAT file. 11 C An error occurred writing YMS_USER.D?? file (task file). 12 CLAU YMS was invoked with an error on the command line. 13 U YMS was unable to find YMS_PRM.D?? file. 14 U YMS found the YMS_PRM.D?? file, but is invalid. 15 AU YMS was unable to find YMS_PRM.DAT file. 16 AU YMS was unable to load YMS_PRM.DAT, because it is invalid. 17 U YMS was unable to allocate memory to hold message history files (YMS_REC.DAT). 18 U YMS has no memory load its index to access YMS_USER.DAT file. 19 U YMS was unable to open YMS_USER.IDX file. 20 U YMS was unable to read YMS_USER.IDX file. YMS v2.00 Reference Guide Page 53 21 U YMS was unable to open YMS_USER.DAT file. 22 U YMS was unable to update informations in YMS_PRM.DAT. 23 U YMS was unable to update informations in YMS_USER.DAT. 24 L YMS has no memory to load old YMS_PRM.DAT. 25 L YMS could not find old YMS_PRM.DAT file. 26 L YMS found the old YMS_PRM.DAT file but could not load it, as it is invalid. 27 L YMS issued error messages performing CtlCompile. 28 L YMS issued warning messages performing CtlCompile. 29 CL YMS has no memory to process the control file. 30 A YMS has no memory to load all SYSTEM??.DAT files to perform AreaUpdate. 31 C YMS has no memory to process all paths to avoid duplicate areas. 32 LAU YMS loaded an invalid version of YMS_PRM.DAT. 33 LA YMS received a control-c or control-break from keyboard. 34 CA An incorrect entry has been encountered in your Maximus area definition file. 35 CA Index error in OPUS 1.7x area database. 36 CA An incorrect entry has been encountered in your OPUS 1.7x area definition file. 37 A Unrecoverable I/O error in YMS AREAUPDATE temporary file. YMS v2.00 Reference Guide Page 54 38 A There is not enough available memory to hold area informations. Try giving YMS more free memory. 39 L You changed the BBS you specified in the control file and run YMS CTLCOMPILE YMS v2.00 Reference Guide Page 55 Section 8 - DISK STATUS ERRORS ============================== The status of the different disk errors is made by 4 hexadecimal digits (0-9,A-f): XXYY XX values may be: 80 Attachment failed to respond; 40 Seek operation failure 20 Controller failure 10 Data error - Bad CRC 08 Direct memory access (DMA) failure 04 Requested sector not found 03 Write-protect fault (should not occur...) 02 Bad address mark 01 Bad command YY values may be: 00 Write-protect error (should not occur...) 01 Unknown unit 02 Drive not ready 03 unknown command 04 Data error- Bad CRC 05 Bad request structure length 06 Seek error 07 Unknown media type 08 Sector not found 09 printer out of paper (should not occur...) 0A write fault (should not occur...) 0B Read fault 0C General failure Therefore, for example, status 0408 means "Sector not found". YMS v2.00 Reference Guide Page 56 Section 9 - YMS SUPPORT FILES ============================= Name: YMS.CTL (another can by used with a cmdline switch). Location: Where you want. Default: YmsDirectory What it is: YMS control file, where all the configuration informations are stored for COMPILE. Name: YMS_USER.DAT Location: YmsDirectory What it is: Message waiting base. Name: YMS_PRM.DAT Location: YmsDirectory What it is: Main parameter file, contains informations for COMPILE and parametersof common usage in multitasking environments. Name: YMS_PRM.D?? (One per single Task specified) Location: YmsDirectory What it is: Task parameter file. Name: _YMS_OS_.T?? (One per single Task specified) Location: RamDisk What it is: YMS_OS temporary file, used to hold user informations between different executions of YMS_OS Name: YMS_MAIL.F?? (One per single language. Lang 1 mandatory). Location: Where you want. Useful to keep them in the YmsDirectory. Name: YMS_MAIL.C?? (As many as YMS_MAIL.F?? files) Location: YmsDirectory What it is: Compiled language files, for direct use by the mail search module. Name: YMS_REC.DAT Location: One per single message area What it is: Area history file, for direct use by YMS UPDATE. YMS v2.00 Reference Guide Page 57