ITN5363-4ADD4.Pdf

FLORIDA STATE UNIVERSITY PURCHASING DEPARTMENT A1400 UNIVERSITY CENTER TALLAHASSEE FL 32306-2370 ADDENDUM ACKNOWLEDGMENT FORM DATE: December 16, 2009 ADDENDUM NO. 4 Competitive Solicitation Number ITN 5363-4 TITLE: NWRDC Mainframe Software Products INSTRUCTIONS TO RESPONDERS: Attached is additional information pertaining to the Competitive Solicitation. Please read this information carefully and incorporate it into the terms, conditions and specifications submitted with the original solicitation and any prior addendum’s. This cover sheet must be signed by the individual signing the solicitation and returned with this solicitation. CERTIFICATION: This is to certify that I did receive the referenced addendum and have incorporated the terms, conditions, and specifications listed therein into the attached Competitive Solicitation. ___________________________ SIGNED ___________________________ TITLE OF ABOVE 1) Life Cycle: How many stages do they have in their life cycle? The final stage should be PRODuction or something like that. What is the name for each stage and what is the relationship to the predecessor/successor stage? Is an Emergency stage defined and what is its relationship to any standard stage? NWRDC does not utilize ‘life cycle’s’ 2) Components: What is the full list of all the component types i.e. Cobol Source, Assembler Load, CICS Maps, Copybooks, JCL Procedures etc., to be managed in LCM. NWRDC does not know how many programs its customers manage. NWRDC customers do utilize maps, cobol, copybooks and jcl Are any of the component types sub-divided in more than 1 (e.g. Batch Cobol vs CICS Cobol) location this is important because we need to consider these as separate component types. How many of each component type exist? NWRDC does not utilize ‘life cycle’s’ 3) External libraries: What are the full set of external libraries (PDSs) for each component type at each stage of the development life cycle. These will be the target libraries for activities such as export (for change) and build (compilation). NWRDC does not utilize ‘life cycle’s’ 4) Systems: Have the components been divided by system or application or some other definition? NWRDC does not manage customer programs 5) Export/Import: For each source type we need to know the line columns to import. For Cobol we normally only import columns 7 – 72. We do not recommend importing columns 1 – 6 because they only contain a sequence number that has no relevance. If we do import these lines a simple renumbering exercise would have the effect of indicating to LCM that many lines have changed when in fact no actual Cobol code may have been actually changed. Question???? 6) Processors: For each stage in the development life cycle, for each component type, we need to know what to do and what the target is, i.e. the compilation rules. For example, are programs recompiled at each stage of the life cycle or just at the first stage and then the executable is migrated? What component types are linked together i.e. DB2 LOAD and DBRM? NWRDC does not utilize ‘life cycle’s’ Development libraries: With LCM changes are made in libraries (PDSs) that are external to the LCM database. This type of library is outside the control of LCM. We need to know where developers will export code to. Do they work on a standard set of libraries or can they define and select their own? Will they import code back into LCM from the same library that they exported to? Will there be different libraries (at developer level) for each source type? Do we have to control this to enforce a discipline or standard? NWRDC does not utilize ‘life cycle’s’ 7) Packages: Components can only be imported into Packages. A package is the unit of work in LCM and may contain 1 component or more than 1 component and are not limited by component type. The naming of packages is important so that they can be matched to other change mechanisms. That may exist. For example if they have a problem logging system, they may wish to use the number of the problem in the problem logging system as the package name in LCM so the two events can be tied together. What (if any) are the requirements for package names? NWRDC does not utilize ‘life cycle’s’ 8) Approvals: What authority controls and approvals do Qantas require? This controls who is permitted to perform an action at any particular stage of the life cycle. Approvals may be implemented at any stage of the life cycle when defined to LCM. NWRDC does not utilize ‘life cycle’s’ 9) Endevor customization: What (if any) other customization has been implemented around Endevor? NWRDC nor NWRDC Customer use Endevor 10) Versioning: By default, LCM keeps all versions of each component at each stage of the life cycle. For each component type at each stage we need to know how many versions should be kept before a version merge is performed. NWRDC does not utilize ‘life cycle’s’ 11) Backouts: LCM has the capability to reverse changes i.e. perform a backout of a change that has been implemented. Is this action to be performed only by selected users? NWRDC does not utilize ‘life cycle’s’ 12) Concurrent Development: Is concurrent development to be permitted? NWRDC does not utilize ‘life cycle’s’ 13) Existing Modification History: We understand that a significant amount of change history exists in the Endevor system. It is not recommended in LCM to keep all versions of a component because every time the component is accessed LCM must go through all the versions to create the current image of the component. This does depend on how many versions have created over time. What is the highest number of versions of an existing component in the existing system and approximately what is the average number of versions? NWRDC does not utilize ‘life cycle’s’ 14. How many LPAR’s are being used? NWRDC uses four LPAR’s 15. Is the software listed in the RFP run in more than 1 LPAR? NWRDC has not issued and software RFP’s 16. If so, what products are used in each LPAR? NWRDC utilizes all of the licensed software in all LPAR’s a. What is the operating system version level and release level z/OS v1.9 17. What is the version/release level for each of the ISV software products that are in production? All NWRDC software is compatible with current mainframe hardware platform 18. Are any of the software products using Sub Capacity Software pricing? ISV no, IBM yes a. If so, which products All eligible for WLC 19. What is the current CPU model number? 2096-s07-u04 20. Are there any customer coded exits being used for any ISV software products? yes 21. If so, which products? LRS, CA1 22. How many tapes are defined within CA‐1? Approximately 66,000 23. How many vaults are being used? none 24. Is the tape pulling listing reports used? no 25. Is tape encryption being used? no 26. If so, what method is used? n/a 28 How many userid’s are defined within ACF2? Approximately 20-30 thousand 29. is data set security being used for application files? yes 30. Are tape data sets protected? yes 31. Are security exits invoked within the application programs? no 32. Is HSM currently used? yes 33. How many archive tape volumes are there in ABR? none 34. Roughly how much disk space under ABR control? n/a 35. Is ABR being used to process Open Systems disk space? mainframe software does not manage open systems storage 36. SAS—we have a product that will replace SAS— are you open to pursue? vendor responses are defined in ITN document 37. Do you have any immediate plans to move to a Z10? ITN is for current hardware platform Technical Questions for NWRDC General Questions: 38. Will NWRDC be looking for Service engagements from new vendor to migrate to new products? If service engagements are required to accomplish NWRDC goals 39. What type of service engagement will be required? Turnkey? Heavy Assist (NWRDC 25% ‐ Vendor 75%) Medium Assist (NWRDC 50% ‐ Vendor 50%) Light Assist (NWRDC 75% ‐ Vendor 25%) Whatever is required to accomplish NWRDC goals 40. Will remote access be given for the migration service work? yes 41. Do the services need to be completed prior to old vendor contract expiring? NWRDC expects vendors to work with the needs of NWDRC as to service completion dates and contract expiration dates 42. When do all of your vendor licenses expire? Month/Year for each Indentified in the ITN document 43. If awarded, when could the migration services start? When do you expect the new contract to be signed? As soon as possible After PO process is completed Control‐M Usage Questions: Answers to questions 44‐58 NWRDC has eleven separate Control‐M environments managed totally by our customers NWRDC has no input as to how NWRDC Customers use the product 44. List your current Control M scheduling environments (e.g., prod, test) 45. Number of tables per Control M DB environment 46. Number of Jobs defined per DB? 47. Number of Jobs scheduled per DB per (Day/Week/Month) – select one 48. Number of adhoc (on demand) Jobs per DB per (Day/Week/Month) – select one 49. Number of Jobs using scheduler JCL variables 50. Number of Jobs using scheduler specific directives 51. Number of JCL libraries defined to Control M 52. Number of distributed servers being scheduled in the MF Scheduler 53. Number of distributed Jobs (scripts) being scheduled by your MF Scheduler 54. Do Application Programmers access Control M? (Browse or Modify) 55.

Load more