|
1 Introduction 2 Ground Rules Building a File System 3 File Systems 4 File Content Data Structure 5 Allocation Cluster Manager 6 Exceptions and Emancipation 7 Base Classes, Testing, and More 8 File Meta Data 9 Native File Class 10 Our File System 11 Allocation Table 12 File System Support Code 13 Initializing the File System 14 Contiguous Files 15 Rebuilding the File System 16 Native File System Support Methods 17 Lookups, Wildcards, and Unicode, Oh My 18 Finishing the File System Class The Init Program 19 Hardware Abstraction and UOS Architecture 20 Init Command Mode 21 Using Our File System 22 Hardware and Device Lists 23 Fun with Stores: Partitions 24 Fun with Stores: RAID 25 Fun with Stores: RAM Disks 26 Init wrap-up The Executive 27 Overview of The Executive 28 Starting the Kernel 29 The Kernel 30 Making a Store Bootable 31 The MMC 32 The HMC 33 Loading the components 34 Using the File Processor 35 Symbols and the SSC 36 The File Processor and Device Management 37 The File Processor and File System Management 38 Finishing Executive Startup Users and Security 39 Introduction to Users and Security 40 More Fun With Stores: File Heaps 41 File Heaps, part 2 42 SysUAF 43 TUser 44 SysUAF API Terminal I/O 45 Shells and UCL 46 UOS API, the Application Side 47 UOS API, the Executive Side 48 I/O Devices 49 Streams 50 Terminal Output Filters 51 The TTerminal Class 52 Handles 53 Putting it All Together 54 Getting Terminal Input 55 QIO 56 Cooking Terminal Input 57 Putting it all together, part 2 58 Quotas and I/O UCL 59 UCL Basics 60 Symbol Substitution 61 Command execution 62 Command execution, part 2 63 Command Abbreviation 64 ASTs 65 Expressions, Part 1 66 Expressions, Part 2: Support code 67 Expressions, part 3: Parsing 68 SYS_GETJPIW and SYS_TRNLNM 69 Expressions, part 4: Evaluation UCL Lexical Functions 70 PROCESS_SCAN 71 PROCESS_SCAN, Part 2 72 TProcess updates 73 Unicode revisted 74 Lexical functions: F$CONTEXT 75 Lexical functions: F$PID 76 Lexical Functions: F$CUNITS 77 Lexical Functions: F$CVSI and F$CVUI 78 UOS Date and Time Formatting 79 Lexical Functions: F$CVTIME 80 LIB_CVTIME 81 Date/Time Contexts 82 SYS_GETTIM, LIB_Get_Timestamp, SYS_ASCTIM, and LIB_SYS_ASCTIM 83 Lexical Functions: F$DELTA_TIME 84 Lexical functions: F$DEVICE 85 SYS_DEVICE_SCAN 86 Lexical functions: F$DIRECTORY 87 Lexical functions: F$EDIT and F$ELEMENT 88 Lexical functions: F$ENVIRONMENT 89 SYS_GETUAI 90 Lexical functions: F$EXTRACT and F$IDENTIFIER 91 LIB_FAO and LIB_FAOL 92 LIB_FAO and LIB_FAOL, part 2 93 Lexical functions: F$FAO 94 File Processing Structures 95 Lexical functions: F$FILE_ATTRIBUTES 96 SYS_DISPLAY 97 Lexical functions: F$GETDVI 98 Parse_GetDVI 99 GetDVI 100 GetDVI, part 2 101 GetDVI, part 3 102 Lexical functions: F$GETJPI 103 GETJPI 104 Lexical functions: F$GETSYI 105 GETSYI 106 Lexical functions: F$INTEGER, F$LENGTH, F$LOCATE, and F$MATCH_WILD 107 Lexical function: F$PARSE 108 FILESCAN 109 SYS_PARSE 110 Lexical Functions: F$MODE, F$PRIVILEGE, and F$PROCESS 111 File Lookup Service 112 Lexical Functions: F$SEARCH 113 SYS_SEARCH 114 F$SETPRV and SYS_SETPRV 115 Lexical Functions: F$STRING, F$TIME, and F$TYPE 116 More on symbols 117 Lexical Functions: F$TRNLNM 118 SYS_TRNLNM, Part 2 119 Lexical functions: F$UNIQUE, F$USER, and F$VERIFY 120 Lexical functions: F$MESSAGE 121 TUOS_File_Wrapper 122 OPEN, CLOSE, and READ system services UCL Commands 123 WRITE 124 Symbol assignment 125 The @ command 126 @ and EXIT 127 CRELNT system service 128 DELLNT system service 129 IF...THEN...ELSE 130 Comments, labels, and GOTO 131 GOSUB and RETURN 132 CALL, SUBROUTINE, and ENDSUBROUTINE 133 ON, SET {NO}ON, and error handling 134 INQUIRE 135 SYS_WRITE Service 136 OPEN 137 CLOSE 138 DELLNM system service 139 READ 140 Command Recall 141 RECALL 142 RUN 143 LIB_RUN 144 The Data Stream Interface 145 Preparing for execution 146 EOJ and LOGOUT 147 SYS_DELPROC and LIB_GET_FOREIGN CUSPs and utilities 148 The I/O Queue 149 Timers 150 Logging in, part one 151 Logging in, part 2 152 System configuration 153 SET NODE utility 154 UUI 155 SETTERM utility 156 SETTERM utility, part 2 157 SETTERM utility, part 3 158 AUTHORIZE utility 159 AUTHORIZE utility, UI 160 AUTHORIZE utility, Access Restrictions 161 AUTHORIZE utility, Part 4 162 AUTHORIZE utility, Reporting 163 AUTHORIZE utility, Part 6 164 Authentication 165 Hashlib 166 Authenticate, Part 7 167 Logging in, part 3 168 DAY_OF_WEEK, CVT_FROM_INTERNAL_TIME, and SPAWN 169 DAY_OF_WEEK and CVT_FROM_INTERNAL_TIME 170 LIB_SPAWN 171 CREPRC 172 CREPRC, Part 2 173 COPY 174 COPY, part 2 175 COPY, part 3 176 COPY, part 4 177 LIB_Get_Default_File_Protection and LIB_Substitute_Wildcards 178 CREATESTREAM, STREAMNAME, and Set_Contiguous 179 Help Files 180 LBR Services 181 LBR Services, Part 2 182 LIBRARY utility 183 LIBRARY utility, Part 2 184 FS Services 185 FS Services, Part 2 186 Implementing Help 187 HELP 188 HELP, Part 2 189 DMG_Get_Key and LIB_Put_Formatted_Output 190 LIBRARY utility, Part 3 191 Shutting Down UOS 192 SHUTDOWN 193 WAIT 194 SETIMR 195 WAITFR and Scheduling 196 REPLY, OPCOM, and Mailboxes 197 REPLY utility 198 Mailboxes 199 BRKTHRU 200 OPCOM 201 Mailbox Services 202 Mailboxes, Part 2 203 DEFINE 204 CRELNM 205 DISABLE 206 STOP 207 OPCCRASH and SHUTDOWN 208 APPEND Glossary/Index Downloads |
UOS Date and Time Formatting Before we can move on to the next lexical function, we must discuss UOS date and time formatting. We briefly addressed date/time in our discussion of the Init bootstrap back in article 8. UOS keeps time in the same manner - it is a 64-bit unsigned integer into which is packed the date and time (to the nanosecond). VMS deals with time as 128-bit values, but that provides no benefit over 64-bit values and, in fact, would take extra processing to deal with, so we will differ from VMS in this respect. Remember that a 64-bit integer covers a range of -8,000 BC to 8,000 AD, in one nanosecond increments. However, for reasons of encoding delta times (see below), UOS only deals with integer timestamps greater than 0. The user can specify UOS Dates in three forms: absolute, delta, and combination.
Absolute Date/Time Format
The fields are:
You can also specify an absolute time as one of the following special values.
You can abbreviate the date/time as follows.
Examples of abbreviated date/times
Delta Date/Time Format
The fields are:
You can abbreviate the delta date/time as follows.
Combination Date/Time Format the absolute and delta time/date specifications use the same fields and defaults as described above. The one exception is that the delta time/date can start with a minus sign instead of a plus and a minus as long as that is not ambiguous (it can always start with +-). Thus, in combination dates, a delta can be past or future. But you cannot mix plus and negative deltas (such as a negative day with a positive hour) - the entire delta portion of the combination date is either future or past. The following rules apply:
Examples of Combination date/times
Localization The ability of software to be customized to a particular country and/or language is called "Internationalization" (or "I18N" for short). Sometimes it is called "localization", as in "customizing to local conditions". I personally don't care for I18N, and "internationalization" is too long to keep typing, so herein I will use the term "localization". There are many different aspects of operating system localization. Here we will limit our discussion to that of date/time representation. In future articles we will address other areas of localization. The above discussion describes the default English date format. Why is that the default? Well, simply because that is the language in which I am most proficient. Further, English has become the lingua franca of the modern world - most educated people across all countries in the world speak some form of English. Thus, making English the default for UOS provides the widest possible appeal. But, UOS also provides a means of customizing the system's date/time formats. The first stage of date localization is to get the default language. The LNM$LANGUAGE symbol is used to define this. SYS$LANGUAGE defaults to "ENGLISH". This value is used for a symbol table name that will be used to determine date formats. Since symbols can be defined locally by a user to override the system symbol of the same name, this allows each user to define his own language rather than use the default defined by SYS$LANGUAGE.
The value of SYS$LANGUAGE is appended to "LNM$LANGUAGE_" to form the name of the symbol table to use
for obtaining date formatting information. By default, this means that the table
name is "LNM$LANGUAGE_ENGLISH". The values of the symbols in this table are delimited by the
first character that occurs in the value. The character must also terminate the values.
For instance:
Note that the output format consists of two delimited items: the first is the date format and the second is the time format. During output, these are both used to display the date/time. LIB$DT_FORMAT and LIB$DT_INPUT_FORMAT use special codes that indicate how to format date output (in the former) and the order/type of items during input (the latter). The codes start with an exclamation point (!) and must be one of the following values. Note also that non-space characters that are not part of a code are considered delimiters between the different fields.
To make things more user-friendly, the language tables are pre-defined for UOS. As long as the proper language is set during system installation, most people won't have to worry about the gory details specified above. To further aid the UOS system manager, certain symbol names have been predefined for output date and time formats (this occurs in the system startup command file), as follows:
In the next article, we will look at code to parse and manipulate date/time formats.
Copyright © 2020 by Alan Conroy. This article may be copied in whole or in part as long as this copyright is included. |