Embedded Files
Subscribe to keep this site alive! Under new management but as always, still 100% FREE. Anyone with the IBM i is a friend of ours.
The Challenge: The Data Privacy Act requires the purging of the personal data as soon as the grace period has passed. The Internal Trading Partner ID can be a starting point to locate where in the data base are these parties.
The Challenge: The Data Privacy Act requires the purging of the personal data as soon as the grace period has passed. The Internal Trading Partner ID can be a starting point to locate where in the data base are these parties.
The Solution: The Trading Partner Relationship (TPR) contains the Internal Trading Partner ID along with the translation formats which can be derived from the PRTFMTTPR API. Each translation format has a related User File Definition (UFD) and a UFD has related underlying record formats (files). Working back, the PRTUFDRCD API reports the related translation formats given a UFD. And the PRTUSRFIL API reports the related UFDs given a filename.
The Solution: The Trading Partner Relationship (TPR) contains the Internal Trading Partner ID along with the translation formats which can be derived from the PRTFMTTPR API. Each translation format has a related User File Definition (UFD) and a UFD has related underlying record formats (files). Working back, the PRTUFDRCD API reports the related translation formats given a UFD. And the PRTUSRFIL API reports the related UFDs given a filename.
The solution requires a list of file names to be fed to the PRTUSRFIL-API. This API produces the PED290USR report which can be report-scraped using @@XTRCTUFD-RPGLE to produce a list of the UFD name with the corresponding file from the file seed. The list of UFD names will be fed to the PRTUFDRCD-API producing the PED290RCD report giving list of the related translation formats and the corresponding UFD. The matrix of Files-UFDs-translation formats can be joined to the matrix of translation formats-TPRs and be able to relate the Internal Trading Partner ID to the file. Then it will be up to your DBA to further relate these file to the rest of your system/database.
The solution requires a list of file names to be fed to the PRTUSRFIL-API. This API produces the PED290USR report which can be report-scraped using @@XTRCTUFD-RPGLE to produce a list of the UFD name with the corresponding file from the file seed. The list of UFD names will be fed to the PRTUFDRCD-API producing the PED290RCD report giving list of the related translation formats and the corresponding UFD. The matrix of Files-UFDs-translation formats can be joined to the matrix of translation formats-TPRs and be able to relate the Internal Trading Partner ID to the file. Then it will be up to your DBA to further relate these file to the rest of your system/database.
Thinking of a new CHALLENGE? Let us know HERE.
Page updated
Google Sites
Report abuse