RE: Memory Allocation Question

>>>  * Use the Social Security Number as the customer number if SSN is
valid.                    

I would rethink this idea of using the SSN as the customer number. I don't
like the use of the SSN as a identifier. It's a privacy/identity theft
issue. In fact, the prescription plan at work just issued new ID cards,
changing the account number from the SSN to another number. 
I'd be concerned about liability if a customer's identity was comprised
because of the use of the SSN as the account number.

Steve Morrison
Beacon Insurance
940-720-4672 

-----Original Message-----
From: Francis Lapeyre [mailto:flapeyre@xxxxxxxxxxx] 
Sent: Tuesday, November 09, 2004 9:39 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Memory Allocation Question

I have a routine to kinda/sorta validate Social Security numbers. There are
some obvious bad combinations. Here it is:

      * Social Security Number broken down into parts        
     D                 DS                  Inz               
     D  Key_Ssn                       9  0 
     D   Area                         3  0 Overlay(Key_Ssn)  
     D   Group                        2  0 Overlay(Key_Ssn:*NEXT)
     D   Serial                       4  0 Overlay(Key_Ssn:*NEXT)

     D   SSN_Ok                        N   Inz(*OFF)
                                                             
      * Determine if SSN is valid.

      * Use the Social Security Number as the customer number if SSN is
valid.