About the ITAOP/savePDF Method - Usa-federal-forms.com
About the ITAOP/savePDF Method - Usa-federal-forms.com
About the ITAOP/savePDF Method - Usa-federal-forms.com
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
E3.1. CARTRIDGE SUBMISSION<br />
E3. ENCLOSURE 3<br />
SUBMISSION INSTRUCTIONS<br />
DODI 1336.5, May 2, 2001<br />
The submitting Military Service shall use IBM 3480 or 3490 magnetic tape cartridges.<br />
Each file shall be written with standard IBM internal labels using <strong>the</strong> file naming<br />
convention outlined in section E3.4., below, and coded using <strong>the</strong> EBCDIC character set.<br />
DMDC can accept <strong>com</strong>pressed data files.<br />
E3.2. ELECTRONIC SUBMISSION<br />
The submitting Military Service shall contact <strong>the</strong> DMDC Active Duty Personnel File<br />
Manager, who will establish a UNIX account number and password exclusively for <strong>the</strong>se<br />
reports and provide additional system specifications, including security protocols<br />
appropriate to protect <strong>the</strong> data from <strong>com</strong>promise and consistent with standards<br />
established by <strong>the</strong> National Institute of Standards and Technology (NIST). DMDC<br />
supports standard FTP software and can accept <strong>com</strong>pressed (zipped) data files. The file<br />
names shall be consistent with <strong>the</strong> naming convention outlined in section E3.4., below.<br />
(Note that <strong>the</strong> UNIX environment at DMDC requires <strong>the</strong> exclusive use of lower case<br />
for all file names.) The Military Service is responsible for <strong>the</strong> accuracy and<br />
<strong>com</strong>pleteness of each electronic data transfer.<br />
E3.3. DATA SPECIFICATIONS<br />
Order each file in ascending order by Person Social Security Number Identifier (Field 5<br />
of enclosure 4, or Field 1 of attachment 1 to enclosure 5) and Transaction Effective<br />
Calendar Date (Field 86 of enclosure 4, or Member Personnel Tempo Event Begin<br />
Calendar Date (Field 8 of attachment 1 to enclosure 5). Multiple transaction records<br />
with <strong>the</strong> same date shall be submitted in <strong>the</strong> order <strong>the</strong>y are to be processed.<br />
9 ENCLOSURE 3