Professional Web Applications Themes

[DB2 UDB for OS/390 V7.1] Need package-versioning strategy - IBM DB2

We're implementing packages to handle Java/Websphere/CICS(Generic Transaction) program calls. I'm pretty sure we're going to need multiple versions to handle this. I've got a handle on basic package naming, but we're still mostly a plan-based shop here (wakefern.com). I'd appreciate anyone's suggestions on how to name the versions of packages. Sequential assignment? Timestamp? Is there something better out there? I'd also appreciate any help finding a good, intense discussion of Java, CICS, WLM, Stored Procedure, Package implementation. It wasn't this complex in the Good Old Days, y'know? I'm confronting my own limited education on these issues, here, and it isn't ...

  1. #1

    Default [DB2 UDB for OS/390 V7.1] Need package-versioning strategy

    We're implementing packages to handle Java/Websphere/CICS(Generic
    Transaction) program calls. I'm pretty sure we're going to need
    multiple versions to handle this.

    I've got a handle on basic package naming, but we're still mostly a
    plan-based shop here (wakefern.com). I'd appreciate anyone's
    suggestions on how to name the versions of packages. Sequential
    assignment? Timestamp? Is there something better out there?

    I'd also appreciate any help finding a good, intense discussion of
    Java, CICS, WLM, Stored Procedure, Package implementation. It wasn't
    this complex in the Good Old Days, y'know? I'm confronting my own
    limited education on these issues, here, and it isn't pretty.

    --Phil Sevetson
    [email]phil.sevetsonwakefern.com[/email]
    Badger Guest

  2. #2

    Default Re: [DB2 UDB for OS/390 V7.1] Need package-versioning strategy

    The default versioning scheme works better than all of the complex manual
    procedures, causes the least work and is the most reliable. This was also
    true in the "good old days" of DB2 V3, when package versioning was first
    implemented.

    "Badger" <psevetsonnetscape.net> wrote in message
    news:1a838009.0309151030.36419339posting.google.c om...
    > We're implementing packages to handle Java/Websphere/CICS(Generic
    > Transaction) program calls. I'm pretty sure we're going to need
    > multiple versions to handle this.
    >
    > I've got a handle on basic package naming, but we're still mostly a
    > plan-based shop here (wakefern.com). I'd appreciate anyone's
    > suggestions on how to name the versions of packages. Sequential
    > assignment? Timestamp? Is there something better out there?
    >
    > I'd also appreciate any help finding a good, intense discussion of
    > Java, CICS, WLM, Stored Procedure, Package implementation. It wasn't
    > this complex in the Good Old Days, y'know? I'm confronting my own
    > limited education on these issues, here, and it isn't pretty.
    >
    > --Phil Sevetson
    > [email]phil.sevetsonwakefern.com[/email]

    Mark Yudkin Guest

Similar Threads

  1. Web Service Versioning
    By Brett in forum ASP.NET Web Services
    Replies: 2
    Last Post: June 23rd, 08:24 AM
  2. Replies: 0
    Last Post: November 14th, 05:21 PM
  3. Versioning Best Practices?
    By S. Justin Gengo in forum ASP.NET General
    Replies: 6
    Last Post: August 12th, 04:48 PM
  4. versioning of assemblies
    By MeDhanush in forum ASP.NET General
    Replies: 2
    Last Post: June 30th, 06:18 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139