PROGRAMMER DELETED SOURCE FILES

pts.
Tags:
AS/400 Library
AS/400 Source Files
PF
QCLSRC
QRPGSRC
Recently I asked an AS400 RPG programmer who has worked here over 9 years to delete PF's in their test library. This person also deleted their test source files (QRPGSRC, QCLSRC, ECT) Does anyone have thoughts on this? I really appreciate this.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Restore from backup?

Discuss This Question: 15  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • I'm really curious what kind of programmer deletes the source files? On a regular basis we do "cleanup". I think this employee is showing passive/aggressive behavior. But I wanted other's opinions before I move forward. Thanks
    0 pointsBadges:
    report
  • Gilly400
    Hi, It's not a mistake I'd expect from anyone with reasonable experience. Taking copies of data files to use for testing is common practice, but these files are often forgotten and left to occupy (read waste) disk space. Removing obsolete test data files should also become common practice. Deleting source files is something that shouldn't. Does your programmer also keep compile listings on the system - maybe you could get him to rebuild his sources from his latest compile listings - might be a valuable lesson for him. Regards, Martin Gilbert.
    23,730 pointsBadges:
    report
  • Gilly400
    Hi, Just an extra thought - nobody's perfect, we all make mistakes... I remember back in the days accidentally formatting the C: drive on my PC in work. Regards, Martin Gilbert.
    23,730 pointsBadges:
    report
  • Aloniks
    before asking to delete the PF one should say DO NOT DELETE source physical file or allyws a good process to folLow before any deltion is one should take the backup you can restore the source file (QRPGSRC, QCLSRC, ECT) from any save file or from tape drive or from your backup server (if it exist) else there is no way to revert back. Better to start coding of all source programs ... cheers!!! Sandeep K Aloni
    30 pointsBadges:
    report
  • philpl1jb
    I do one really boneheaded thing a year. Phil
    49,600 pointsBadges:
    report
  • mcl
    I do one really boneheaded thing a year. Can we quote you on that? :) Seriously though - programmers sometimes get a bit "touchy" about stuff in thier own lib.. We do cleanup on a regular basis and have one programmer who makes up backup copies of files and literally keeps the copies for months. The fact that they get backed up to tape on a nightly basis doesn't matter. When asked to delete files that have not been used in months this person has gotten really upset. In the case of your programmer deleting the PF-DTA and the PF-SRC - did he care? Was he upset? Was it a bad day? Regards Mike
    2,740 pointsBadges:
    report
  • Yorkshireman
    It looks as if you're asking if the employee has reached 'time to move on' I know the difference between source and data, but yet, if given a direct request to remove all files in library 'X' then the focus is on removing the files - a wrkobj *ALL *FILE and option 4 down the page comes to mind. oops! On the other hand, if you say 'remove all unnecessary files in library 'x' my brain comes into gear and I check what I'm doing. You know the person, you know the surrounding circumstances. If he/she and the day was calm, it could be deliberate mischief. If events were such as to suggest he/she made a mistake, well... OTOH if this source was important, I could argue that it's your job these days not just to lay down a paper procedure 'that must be followed' but put in place systems which keep important source safe - check out/in, production versions secured, access only via homegrown commands to copy to work libraries, daily backups. Systems Directors job to ensure no more than a day's work wasted - always have backup available. .
    5,580 pointsBadges:
    report
  • BigKat
    I have had it happen to me a couple of times (due to typing ahead of the screen -- WRKSPLF-ENTER-4-ENTER-ENTER) that I meant to delete the compile listing, but had actually hit ENTER twice after the WRKSPLF (which returned me to WRKMBRPDM) and deleted my source. If the program is ILE and you compiled with DBGVIEW(*SOURCE), you can recover the source by doing a STRDBG on the program, paging down, and copying each screen to a text editor. Then do a little cleanup and transfer it into a new source member.
    7,935 pointsBadges:
    report
  • Koohiisan
    BigKat, that's a great tip! I've deleted source as well by keying ahead of the screen. (I suppose I could blame it on our old, overworked system training us to rely on the keyboard buffer...but...I have to take the blame.) Anyway, I never thought about using the debug source. I'll remember that if it happens again! Thanks! ^_^
    5,020 pointsBadges:
    report
  • philpl1jb
    So now we get to analyze BUSY? I would rather not work for him/her. Phil
    49,600 pointsBadges:
    report
  • mcl
    Busy asked.. We're just tossing ideas.. Regards Mike
    2,740 pointsBadges:
    report
  • Cwc
    Regarding recovering the source from via STRDBG: I don't think that would work if the program was compiled with DBGVIEW(*SOURCE), because the source member still must exist in order to get the source view when debugging, and is not a part of the object. To have the source as part of the object, a program would need to be compiled with the *LIST or *ALL option in the DBGVIEW keyword for an ILE program, or *LSTDBG in the OPTION keyword of an OPM program.
    4,290 pointsBadges:
    report
  • Thanks everyone for your QUICK, HONEST, Responses. I really appreciate it. Originally I wanted to get "unbiased" opinions from outside professionals. I didn't give you any background on this employee. We have had many issues with this employee for about 1 year. (1 year ago this employee's friend and co-worker happily , joyfully and voluntarily retired). Also this employee never "shared" that he/she deleted the source files- after I noticed they were going this employee just smiled and said "You said to remove your test files". (We are installing a new machine on 2/21/09 so I like to remove "test garbage".) Just for everyone's piece of mind. I"m going to ignore this behavior and continue on. Thanks again!!!
    0 pointsBadges:
    report
  • BigKat
    oops - I thought we had changed the default to DBGVIEW(*SOURCE) , but CWC is right our system is set to default to DBGVIEW(*ALL)
    7,935 pointsBadges:
    report
  • Ashnirody
    He was a good soldier. He did exactly what you asked him to do. However not something I would expect with his experience. Something else is definitely going on here. Next time I give this person any instructions, I would double check those instructions.
    100 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following