Procedure for Submission of non-IBM-Written Software or Documents to the VM Download Library

We might make revisions to this procedure, especially early on as we are working out the kinks in it. Please check this page right before you submit to make sure you are following the current instructions.

Instructions for All Submitters

1. Read the submission agreement for non-IBM-written content. By making a submission you are stating that you agree to the terms therein.

2. Make a soft copy of our skeleton agreement file. Clip out the Affirmation and Certificate of Originality sections, and depending on who owns the copyrights to your submission, clip out the appropriate confirmation form.

3. Fill out the Affirmation and Certificate of Originality sections.

4. E-mail your completed Affirmation and Certificate of Originality to your manager or advisor along with the empty confirmation form you saved. Ask your manager or advisor to fill out the confirmation form and return all three items to you via e-mail.

5. When your manager or advisor responds to you, save all three of the completed items as plain text in a single CMS file whose filename is the name of your package and whose filetype is IAGREE.

6. Draw up a one line abstract of your package -- just a single line of text. Save your abstract in a file whose filename is the name of your package and whose filetype is ABSTRACT.

7. Write a more complete description for your package. Your description should be written using simple HTML markup. Please follow the instructions for writing such descriptions. Save your description in a file whose filename is the name of your package and whose filetype is DESCRIPT.

8. If your submission includes files intended for consumption on CMS, build a single VMARC archive file containing those files. This is the VMARC archive file that others will download when they retrieve the CMS component of your submission from our server. (If you do not have VMARC, you can get it from our download page.) Make the filename of your VMARC archive the name of your package. The filetype of your VMARC archive should be VMARC.

9. If your submission includes files intended for consumption on a PC, build a single ZIP archive file containing those files. This is the ZIP archive file that others will download when they retrieve the PC component of your submission from our server. Upload the ZIP file in binary to your CMS system. Make the filename of your ZIP archive the name of your package. The filetype of your ZIP archive should be ZIP.

10. If your submission includes files intended for consumption on a UNIX system, build a single TAR archive file containing those files. This is the TAR archive file that others will download when they retrieve the UNIX component of your submission from our server. Upload the TAR file in binary to your CMS system. Make the filename of your TAR archive the name of your package. The filetype of your TAR archive should be TAR.

11. Make a VMARC archive containing these things:
    1. Your IAGREE file.
    2. Your ABSTRACT file.
    3. Your DESCRIPT file.
    4. Your VMARC file, if you have one.
    5. Your ZIP file, if you have one.
    6. Your TAR file, if you have one.

    Give this archive file a filename matching the name of your package and a filetype of DOWNLOAD. Let's call this file your submission file.

To E-Mail Us Your Submission

1. Get the INHEX file encoding package from our download library.

2. Use INHEX to build an encoded version of your DOWNLOAD file. It will build a file whose filename matches the name of your package and whose filetype is INHEX.

3. Send a note to submit@www.vm.ibm.com, using XEDIT GET or equivalent to include your package's INHEX file as part of the note body.

This submission procedure should work if your DOWNLOAD file contains fewer than about 26200 80-byte records.

We'll send you e-mail when we're done handling your submission.