| DESCRIPTION OF ENHANCEMENTS |
This patch makes a few minor bug fixes and contains some enhancements to
Format: NUMYEAR4(datexp)
Where: datexp is an expression with a date/time value
Use: This function returns the 4 digit year in datexp as a
number.
Example: NUMYEAR4(DATE OF BIRTH)==> 1949
Routine Summary:
DIDT (%DT) Two minor bugs were corrected.
================
Routine Name Before Patch After Patch Patch List
============ ============ =========== ==========
DDMP2 9285380 9295425 30,44
DIDT (%DT) 6367783 6481242 18,24,37,44
DIDTC (%DTC) 7334026 7099203 18,44
DIEH1 1151210 1201975 44
DIENV (env.check) 129370 129370 44
DILIBF 6348908 6194115 44
One is that before, if %DT input variable contained "X", and if user
DINVMSM 8405664 8320664 44
DIP12 4793451 4793661 2,9,16,44
DIQGU 4937798 4828002 8,44
To test if the transport has been corrupted, you can use the "Verify
Package Integrity" option. This option is under Utilities under the KIDS
menu. It will compare the checksums in the build with the current
checksums and list any that differ.
entered a date like MMDDYY where the year was "00", the date was
Installation Instructions:
==========================
NOTE the instructions that are different for your M implementation.
1. NOTE: Users ARE NOT allowed to be on the system during the
installation.
--- Pre Installation steps ---
rejected.
2. Use the 'INSTALL/CHECK MESSAGE' option on the PackMan menu.
This option will load the KIDS package onto your system. The environment
check routine DIENV will run automatically.
DIENV is sent to prevent the inadvertent queuing of the installation
of this patch.
3. The patch has now been loaded into a Transport global on your
system. You now need to use KIDS to install the Transport global.
The other is that one of the algorithms was incorrectly treating the
4. On the KIDS menu, under the 'Installation' menu, use the
following options:
Verify Checksums in Transport Global
Print Transport Global
Compare Transport Global to Current System
Backup a Transport Global
--- Actual Installation ---
year 2100 as a leap year.
5. Users ARE NOT allowed to be on the system during the
installation. Inhibit users from login into the system. %DT, %DTC, DILIBF
and DIP12 in particular are used heavily in VISTA applications. The
consequences of installing this patch while users are on the system are
that users may get a 'source routine edited' error.
6. DO place TaskMan in a WAIT state.
7. DSM Sites: The routines %DT, %DTC and DILIBF are usually mapped
on systems that allow mapping, so you will need to disable mapping for
these routines.
8. On the KIDS menu, under the 'Installation' menu, use the
following option:
Install Package(s)
INSTALL NAME: DI*21.0*44
==========
Answer 'NO' to 'Want to DISABLE Scheduled Options, Menu Options,
In addition, an enhancement was made that will change the current
and Protocols?'
9. DSM and MSM sites: After installing this patch, you need to move
the routines DIDT and DIDTC from your production account into your manager
account. Then, in the manager account, rename:
DIDT to %DT
DIDTC to %DTC
Example: ZL DIDT ZS %DT
behavior. Currently, as documented, if a user enters only 2 digits of
10. Open M sites: Rename:
DIDT to %DT
DIDTC to %DTC
Example: ZL DIDT ZS %DT
11. DSM Sites: Rebuild your mapped set if necessary.
ensure compliance with year 2000 issues. The changes are as follows:
the year and if %DT is not set up by the developer to contain either
12. DO remove TaskMan from a WAIT state.
13. Enable users' login.
an "F" (future) or "P" (past), then FileMan assumes the current
century. Thus in 1997, if a user enters 01/01/00, FileMan assumes
01/01/1900.
NEW BEHAVIOR for DIDT (%DT):
note that this new behavior only applies when the user enters
a 2-digit year, causing FileMan to guess the century. Note
also that the "F" and "P" flags will behave as they always have--this
new behavior is only used when neither of those flags is set.
If using the current century causes the date to be more than 80 years
in the past, then FileMan will assume the next century. Thus in 1997
if a user enters a year of 0 through 16, FileMan will assume the
years 2000 through 2016, because 1900 through 1916 are more than 80
years in the past.
If using the current century causes the date to be more than 20 years
in the future, then FileMan will assume the previous century. Thus
in the year 2000, if the user enters 21 through 99, FileMan will
assume the years 1921 through 1999, because 2021 through 2099 are
more than 20 years in the future.
DIDTC (%DTC) Although all of the code properly handled dates up to 2100,
the code was treating 2100 as a leap year. This has been corrected.
Also, online help for dates (HELP^%DTC) was changed to reflect the
change in functionality described in ^%DT above.
DIEH1 Online help for dates used by the DataBase Server calls (DT^DIEH1)
was changed to reflect the change in functionality described in
^%DT above. In support of this routine change is a change to entry
#9110 in the DIALOG file.
DILIBF Old algorithms were treating the year 2100 as a leap year. This
has been corrected.
DDMP2 Changed to call internal FileMan date formatting routines (DILIBF)
DINVMSM This routine contains operating system-specific code and is used
by stand-alone FileMan sites only. Routine SET was setting DT using
an MSM-specific call that would not have worked properly in the year
2000. This has been corrected.
DIP12 In the PRINT option, if the user chose to print the sort criteria
in the header of the report, and if any of the sort fields were
dates, the date was previously printed with a 2-digit year. That is
changed so that the date is now printed with a 4-digit year for
rather than Kernel date formatting routines (XLFDT) to take
clarity.
DIQGU Old algorithms were treating the year 2100 as a leap year. This
has been corrected.
CHANGE TO ENTRY IN DIALOG FILE: In support of new online help for dates
to reflect the new behavior of ^%DT, entry number 9110 has been
advantage of changes made to DILIBF (described below).
changed. This entry is called from routine DIEH1.
NEW FILEMAN FUNCTIONS: NUMDATE4 and NUMYEAR4
The new FileMan Functions NUMDATE4 and NUMYEAR4 have been added to
the list of FileMan Functions that are available for use within
FileMan. They behave as follows:
NUMDATE4
Format: NUMDATE4(datexp)
Where: datexp is an expression with a date/time value
Use: This function returns the date in datexp, in MM/DD/YYYY
format.
Example: NUMDATE4(DATE OF BIRTH)==> 03/07/1949
NUMYEAR4
|
